Hi community!
I have the problem, that sometimes my Bitcoin node just stops synchronizing, so with other words the SSD is not in use anymore (no flashing light anymore from the wavlink). Then i close the Bitcoin app and try to do a troubleshooting again, but it can not generating the logs… it’s just freezing.
Then i need to reboot and even that is not working sometimes. No restart and no shutdown is working… Also no ssh…
So i did a troubleshooting and this is the error message in the report (this report comes while it is working):
App logs
bitcoin
Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_tor_1
i2pd_daemon_1 | 23:02:41@579/error - Tunnels: Can’t select next hop for tSC5WDnkwyLCVgjrYyHQ1m8ibSn9~FfIRRRDhsm442c=
i2pd_daemon_1 | 23:02:41@579/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 23:02:56@579/error - Tunnels: Can’t select next hop for d6gnw0zGlAlstFKwCDTOMAWiaT80-MCu3~lgbjIeIB4=
i2pd_daemon_1 | 23:02:56@579/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 23:03:02@767/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 23:03:13@767/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 23:03:16@767/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 23:03:18@767/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 23:03:26@579/error - Tunnels: Can’t select next hop for KXeh5ZWu~mNJsYoVeo5N5QCWCyVY5Ba6nRUrZiqm9JE=
i2pd_daemon_1 | 23:03:26@579/error - Tunnels: Can’t create inbound tunnel, no peers available
bitcoind_1 | 2024-03-30T23:04:08Z UpdateTip: new best=0000000000000000000355c29c6f245daf67b7e6cfbddd0181d892ef9bb90992 height=836289 version=0x20110000 log2_work=94.818746 tx=980444568 date=‘2024-03-25T22:22:37Z’ progress=0.997559 cache=14.1MiB(122916txo)
May anyone knowledgeable let me know, if that says something about the reason in regards to my problem?
Thank you in advance!!