Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not syncing with last 4-6 nodes gives timestamp greater error #58

Open
Ashutosh-Tosh opened this issue May 6, 2024 · 1 comment
Open

Comments

@Ashutosh-Tosh
Copy link

[2024-05-06] (15:24:42.009) WARN xelis_daemon::p2p > Error occured on chain sync with Peer[connection: Connection[state: Success, peer: 51.68.142.141:2125, read: 10.1 KiB, sent: 4.5 KiB, key rotation (in/out): (1/1), connected since: 57s, closed: false], id: 14610305161627733346, topoheight: 89282, top hash: 5dc1b85191e1450cc64b0dc333ef2d328f834437c0e2f7f1ee10f57dae2b6e9a, height: 84017, pruned: No, priority: true, tag: None, version: 1.10.0-45795c2, fail count: 0, out: true, peers: 0]: Timestamp 1714989282009 is greater than current time 1714989286823

image

already tried fast sync boost sync, running the latest version

@Ashutosh-Tosh
Copy link
Author

Update: Tried Changing my system time to UTC 0 it didnt work, however, reverting back to automatic(utc +5:30) started syncing node correctly and is up to date now since 15 mins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant