Bitcoin node keeps crashing after update v29.0.0

Bitcoin and Lightning
1

Hello,

Since the last Bitcoin Node update to v29.0.0, my node keeps crashing after a few hours syncing. Logs can be found below:

bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@369/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:06:10@441/error - Gzip: Deflate error 0
bitcoin_i2pd_daemon_1  | 13:06:13@441/error - Gzip: Deflate error 0
bitcoin_i2pd_daemon_1  | 13:06:13@441/error - Gzip: Deflate error 0
bitcoin_i2pd_daemon_1  | 13:06:14@441/error - Gzip: Deflate error 0
bitcoin_i2pd_daemon_1  | 13:06:15@369/error - Destination: Can't send LeaseSet request, no inbound tunnels found
bitcoin_i2pd_daemon_1  | 13:06:15@369/error - Destination: Can't send LeaseSet request, no outbound tunnels found
bitcoin_i2pd_daemon_1  | 13:06:15@369/error - Destination: Can't publish LeaseSet. Destination is not ready
bitcoin_i2pd_daemon_1  | ln: /home/i2pd/data/certificates/i2pd_certificates: File exists
bitcoin_i2pd_daemon_1  | 13:06:36@114/none - i2pd v2.44.0 (0.9.56) starting...
bitcoin_i2pd_daemon_1  | 13:06:46@731/error - Tunnels: Can't select next hop for ynEFtXafLW8zJ9nfbsjo7RYIat9~5FLWEq1nkvAzPbI=
bitcoin_i2pd_daemon_1  | 13:06:46@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:06:46@731/error - Tunnels: Can't select next hop for ynEFtXafLW8zJ9nfbsjo7RYIat9~5FLWEq1nkvAzPbI=
bitcoin_i2pd_daemon_1  | 13:06:46@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:06:47@731/error - Tunnels: Can't select next hop for ynEFtXafLW8zJ9nfbsjo7RYIat9~5FLWEq1nkvAzPbI=
bitcoin_i2pd_daemon_1  | 13:06:47@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:06:47@731/error - Tunnels: Can't select next hop for ynEFtXafLW8zJ9nfbsjo7RYIat9~5FLWEq1nkvAzPbI=
bitcoin_i2pd_daemon_1  | 13:06:47@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:07:01@731/error - Tunnels: Can't select next hop for 30wKElS3Sk41M~NSd2TOQ0d8nIXttZhmYCgVXvOyo4g=
bitcoin_i2pd_daemon_1  | 13:07:01@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:07:01@731/error - Tunnels: Can't select next hop for 1HEiCu0NjMba1QUZfRy8g6rbNWaCNlNerv2kPag2kQI=
bitcoin_i2pd_daemon_1  | 13:07:01@731/error - Tunnels: Can't create inbound tunnel, no peers available
bitcoin_i2pd_daemon_1  | 13:10:00@429/error - Streaming: No packets have been received yet
bitcoin_i2pd_daemon_1  | 13:10:02@903/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
bitcoin_i2pd_daemon_1  | 13:11:01@731/error - Tunnel: Tunnel with id 3646616091 already exists
bitcoin_i2pd_daemon_1  | 13:13:59@997/error - SSU2: RelayIntro unknown router to introduce
bitcoin_i2pd_daemon_1  | 13:21:00@731/error - Tunnel: Tunnel with id 1994717630 already exists

There are more error logs, but these ones are pretty much most of them.

Restarting “fixes” the problem temporarily. The node starts running and syncing again, but after a few hours it crashes again. After the restart, the lastest blocks need to be synced again.

Do you guys have any idea as of why this might happen and how to solve it…?

Thanks!

2

I’m also having this issue. I don’t have logs right now, but I’m seeing the same behaviour where my node goes back to 99.77% synchronised, even after blocks had been getting sync’d.

3

did you guys found a solution?

4

Uninstall Electrs and restart your node.

5

I didn’t actually delete Electrum, but I manually restarted the Bitcoin app while it was close to 100%, but not yet fully synchronised. That made it work. Why? No clue.

7

this is a bug umbrel is willingly ignoring, i am not sure why as this point