bitcoind rpc gets stuck in an infinite loop if incorrect password is provided

[rolznz]

This is logged continuously, and the whole LDK-node process seems to get stuck.

{"level":"error","line":512,"log_type":"LDK-node","module_path":"ldk_node::chain","msg":"Failed to synchronize chain listeners: BlockSourceError { kind: Persistent, error: Custom { kind: InvalidData, error: \"invalid response length: 0 bytes\" } }","time":"2025-06-25T12:23:59+07:00"}

[tnull]

Yeah, as mentioned elsewhere this will only happen on regtest, as on mainnet we'd abort early if we're unable to update fee rate estimates. We also have to keep retrying to make progress there, as it's part of initialization of the chain syncing task.
We could however consider to make the delay larger, and we should see whether we can provide a more conclusive error message (although I'm not sure whether bitcoind RPC provides an 'invalid password' return code that we could lean on here).

the whole LDK-node process seems to get stuck.

Could you expand on what 'seems to get stuck' means?

[tnull]

@tosynthegeek indicated interest in working on this.

[tosynthegeek]

@tosynthegeek indicated interest in working on this.

Yeah sure. Would love to pick this up

[rolznz]

Could you expand on what 'seems to get stuck' means?

It's somehow stopping me from being able to exit the process. I have to force-kill it. ctrl+c which normally works fine in our app, just does nothing.

[tosynthegeek]

@tnull please check #588