Closed domunus closed 7 months ago
You must sync your clock, XELIS has a limit of 2s above current clock time.
Use chrony on Windows or ntpdate on Linux.
Thanks, I followed the setup for Chrony for windows. Restarted daemon, now just waiting to see. So far so good though as I've seen a peer drop and a new peer join, no errors.
Issue is resolved. No further errors.
daemon version: 1.9.5-2115b52 Windows 11 port is default 2125
I started getting the below error yesterday morning and my peer count was dropping. I thought maybe it was the version I was on at the time, so i updated to the latest, boost synced and same issue. I only have 2 peers connected when prior to yesterday I had upwards of 30. Aside from the peering syncing, I appear to be syncing just fine. I also get a WARN message. Thought maybe windows firewall started blocking so disabled to test, but same problem.
[2024-04-29] (15:27:25.622) ERROR xelis_daemon::p2p > Error while adding new block from Peer[connection: Connection[state: Success, peer: 51.210.117.23:2125, read: 905.2 KiB, sent: 747.5 KiB, key rotation (in/out): (1/1), connected since: 6h 48m 27s, closed: false], id: 10098345888529429756, topoheight: 52407, top hash: ae299071ae3ea2d7632c340f74b0e385632d95587b8ac359485607e341e69dec, height: 49440, pruned: No, priority: true, tag: None, version: 1.9.5-02a51b7, fail count: 1, out: true, peers: 691]: Timestamp 1714429645622 is greater than current time 1714429655787
[2024-04-29] (15:27:28.930) WARN xelis_daemon::p2p > Error occured on chain sync with Peer[connection: Connection[state: Success, peer: 51.210.117.23:2125, read: 905.5 KiB, sent: 749.3 KiB, key rotation (in/out): (1/1), connected since: 6h 48m 30s, closed: false], id: 10098345888529429756, topoheight: 52407, top hash: ae299071ae3ea2d7632c340f74b0e385632d95587b8ac359485607e341e69dec, height: 49440, pruned: No, priority: true, tag: None, version: 1.9.5-02a51b7, fail count: 2, out: true, peers: 691]: Timestamp 1714429648930 is greater than current time 1714429655787