Geth version: 1.6.5-stable
OS & Version: Linux Ubuntu 16.04
I get this Error on my geth...
I0627 13:01:40.338572 p2p/discover/ntp.go:58] -------------------------------------------------------------------------------
I0627 13:01:40.338587 p2p/discover/ntp.go:59] System clock seems off by 22.347762561s, which can prevent network connectivity
I0627 13:01:40.338596 p2p/discover/ntp.go:60] Please enable network time synchronisation in system settings
I0627 13:01:40.338601 p2p/discover/ntp.go:61] -------------------------------------------------------------------------------
And spamming very much time... how can i fix it?
I find a tutorial for windows but not for Ubuntu with only terminal
You can use timedatectl set-ntp true to enable NTP on Ubuntu.
I tried timedatectl set-ntp true but there is doing nothing...
if i check timedatectlagain
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
If you open up the "Time and Date" settings app (just search for it from the start menu), there will be a radio button to set the time Automatically from the Internet. That should do it.
I have only Terminal Ubuntu Server.
In theory, the NTP synchronized: no should change to yes after a while. If that doesn't happen something is wrong with NTP on the machine.
I have the same issue. The node has been running for several months and stopped with the message several days ago. I had the same issue when I first ran the node but I didn't remember what was the solution.
sudo apt-get update
sudo apt-get install ntp
sudo service ntp start
seems to resolve the issue.
Sweet :) Closing then.
@karalabe I don't know if it fixes @Marow issue... Maybe it's not the same solution.
Aaah, didn't see that there are two different people with this issue :D
Ubuntu12 can't fix it
sudo apt-get update sudo apt-get install ntp sudo service ntp startI followed the above and it worked in few machines. The approach in the following link worked for all.
https://askubuntu.com/questions/929805/timedatectl-ntp-sync-cannot-set-to-yes
Seems to be solved, closing again
Most helpful comment
seems to resolve the issue.