error: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)

[DerekYeung]

When I have hundreds of inscriptions in the memory pool, I will not be able to continue inscribe until they are confirmed.

it just throw me error: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)

I try to fix this in the fork and finally find that the problem occurs at https://github.com/casey/ord/blob/master/src/subcommand/wallet/inscribe.rs#L307, when I deleteInscribe::backup_recovery_key it works again @casey

[DerekYeung]

I don't know rust so I don't know what's going on here, but I'm wondering can I delete this? I assume here is a backup just in case something goes wrong and not actually needed

[zx0922]

P:\ord>ord --cookie-file .cookie --rpc-url 192.168.2.222 --data-dir P:\ord wallet balance error: JSON-RPC error: transport error: unexpected HTTP code: 403

.cookies file is like username:password

ord 0.5.1

Umbrel Version 0.5.3

[ghost]

There is a solution for this error?

[viralrich]

This is because bitcoind still running in background with some indexing process

[LightRider5]

Have suddenly the same error. Why should it be caused by bitcoind?

[viralrich]

You need to await few mins, probably process in background still active,

Wait like 10-15 mins and run "ord" command, if ordinals options are showed it's because process end

[LightRider5]

Didn't help. I also rebooted, restarted bitcoind and reinstalled the binary. Still the same error. Maybe I have to reindex again.

[viralrich]

To re-index you just can run command:

ord wallet balance and will resume the index process if not end yet,

Indexing are large process

El mar, 14 mar 2023 a las 16:16, LightRider @.***>) escribió:

Didn't help. I also rebooted, restarted bitcoind and reinstalled the binary. Still the same error. Maybe I have to reindex again.

— Reply to this email directly, view it on GitHub https://github.com/casey/ord/issues/1852#issuecomment-1468993186, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOVEO2X3SJAS7R66T3R3ITW4D33XANCNFSM6AAAAAAVJ7MOLI . You are receiving this because you commented.Message ID: @.***>

[LightRider5]

ord wallet balance updates the index to the current block count!

re-index means you build the complete index again from scratch. This are two completely different things!

The bug still consists. I could bypass it by changing the file i want to inscribe every time it occurs.

[piesrtasty]

I'm also experiencing this issue when inscribing > 100 files in a loop.

[RobertClarke]

+1

[pavillag]

• 1

Is there a solution to this?

[ylsGit]

if use https https://github.com/rust-bitcoin/rust-bitcoincore-rpc/issues/323 https://github.com/apoelstra/rust-jsonrpc/issues/106

[kvagajack]

+1

I am using ord 0.9.0 and getting the same error.

(Bitcoind is synced, and mempool is loaded)

[kvagajack]

Just upgraded ord to 0.14.1, and the same error :(

$ ord --cookie-file /var/lib/bitcoind/.cookie \
    --index /root/.local/share/ord/index.redb \
    wallet  inscribe  \
    --destination <address> \
    --postage 9999sats \
    --fee-rate 48 
    --file <file_path>

error: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)

[kvagajack]

Btw, this is an intermittent issue... Sometimes I am able to inscribe, but still the failure happens much more often...

Files i am inscribing are from 3K to 5K. And some may fail first, and then get through later. When I inscribe very small files (30B) I don't get the error.

[raphjaph]

This could be an issue with the initial client that talks to Bitcoin becoming stale if the connection is not used for a while. I've recently done a big wallet refactor where we now create new clients more often. This might solve this issue. Will probably make a release this week for that.