ord 0.8.0 on Mac / error: JSON-RPC error: transport error: Couldn't connect to host: Broken pipe (os error 32)

[so7ow]

Ord 0.8.0 was working correctly for several days. Suddenly yesterday it started throwing this error for me:

error: JSON-RPC error: transport error: Couldn't connect to host: Broken pipe (os error 32)

...in response to ord wallet balance and ord wallet cardinals. ord index run still works. I haven't tried other commands. Anecdotally, I know of several other people on the official ord Discord reporting the same problem. The only solution we've found is to use this forked version of ord which apparently uses different logic to load inscriptions into RAM: https://github.com/gmart7t2/ord

My config:

Bitcoin Core 25.0 installed via HomeBrew

===bitcoin.conf===
txindex=1
server=1
blocksdir=/Volumes/BITCOIN/bitcoin
===============

===settings.json===
{
    "wallet": [
        "--redacted--",
        "ord",
        "--redacted--"
    ]
}
================

Ord commands and responses:

 % ~/ord/exec/0.8.0/ord --index ~/ord/index/no-sats/index.redb wallet balance
error: JSON-RPC error: transport error: Couldn't connect to host: Broken pipe (os error 32)

% ~/ord/exec/0.8.0/ord --index ~/ord/index/no-sats/index.redb wallet cardinals
error: JSON-RPC error: transport error: Couldn't connect to host: Broken pipe (os error 32)

% ~/ord/exec/0.8.0/ord --index ~/ord/index/no-sats/index.redb index run
███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████░ 798401/798402

System specs:

MacBook Pro 14-inch 2021
M1 Max / 32 GB RAM / 512 GB SSD
Running macOS 14 beta 3
Bitcoin blocksdir redirected to external SanDisk 2 TB USB-C SSD

[so7ow]

I just tried unloading my two non-ord wallets. No change.

[so7ow]

Tried using rpctimeout=100000 in bitcoin.conf -- no change.

Hmm...guess that's not a thing anymore.

2023-07-12T14:31:22Z Ignoring unknown configuration value rpctimeout

[so7ow]

Ah! Adding this entry:

rpcservertimeout=1000

...to bitcoin.conf has allowed the commands to complete successfully!

[so7ow]

I would submit that the ability to function correctly on a node with the default rpcservertimeout would be a good thing.