<p>My node stopped, bitcoin core does not start synchronizing. I opened the bitcoin log and found this error: Does anyone have a solution??</p>
<pre><code>i2pd_daemon_1  | 05:58:04@64/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1  | 05:58:16@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 05:58:21@64/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1  | 06:02:37@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:02:38@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:05:06@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:07:30@378/error - Tunnels: Can't select next hop for .....-...........-...........-...........-...........-...........-...........-......
i2pd_daemon_1  | 06:07:30@378/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1  | 06:08:17@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:15:36@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
</code></pre>

CC BY-SA 4.0
2023-07-09T13:31:11.090Z
That looks like logs from the I2P daemon, not Bitcoin Core
Pieter Wuille
CC BY-SA 4.0
2023-07-09T15:41:35.670Z
CANT handle ECIES is inside the bitcoin log
Texugo
CC BY-SA 4.0
2023-07-09T16:53:30.443Z
Bitcoin Core doesn't use ECIES in any way or form.
Pieter Wuille
CC BY-SA 4.0
2023-07-09T17:14:56.860Z
i do stop and start bitcoin, its ok
Texugo
<bitcoin-core><synchronization><daemon>
Bitcoin dont start sync
Texugo
# Bitcoin dont start sync

(Asked by: username_0 on 2023-07-09)

My node stopped, bitcoin core does not start synchronizing. I opened the bitcoin log and found this error: Does anyone have a solution??

```
i2pd_daemon_1  | 05:58:04@64/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1  | 05:58:16@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 05:58:21@64/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1  | 06:02:37@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:02:38@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:05:06@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:07:30@378/error - Tunnels: Can't select next hop for .....-...........-...........-...........-...........-...........-...........-......
i2pd_daemon_1  | 06:07:30@378/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1  | 06:08:17@549/error - Garlic: Can't handle .....-......-AEAD-Ratchet message
i2pd_daemon_1  | 06:15:36@67/error - Garlic: Can't handle .....-......-AEAD-Ratchet message

```

**Tags:** bitcoin-core, synchronization, daemon

> **Comments:**
> **username_1**: That looks like logs from the I2P daemon, not Bitcoin Core  
> **username_0**: CANT handle ECIES is inside the bitcoin log  
> **username_1**: Bitcoin Core doesn't use ECIES in any way or form.  
> **username_0**: i do stop and start bitcoin, its ok  

---

## 0 answers

