-
Notifications
You must be signed in to change notification settings - Fork 42
Stuck on finding peers -> hw clock needed syncing for geth to work #33
Comments
In Mist we currently use https://github.com/fjl/os-timesync to check for NTP sync and warn the user. |
I am having this same problem, my Win 7 computer is set to auto sync with network time.nist.gov and I've updated just to make sure. Have started and restarted, uninstalled and reinstalled several times. But "Synchronizing" "Finding peers" just sits. 14:17:16 info info info info info info info info info info info info |
Ok, I work on OSX 10.12.3 and have also the problem that it stucks in finding peers. "View details" Button shows a blank white page. |
Still the same behaviour with the 0.5.0 release! |
Okdoky, now with the version 0.5.2 my problem is solved! Thanks! |
Stuck on finding peers -> hw clock needed syncing for geth to work
I'm on archlinux 64bit
Got stuck on "finding peers", looking at the logs from within AKASHA there was nothing obvious.
I decided to install and run geth independently to see if there was any issues preventing it from syncing, this is what i got from stdout:
So, the issue was my hwclock was 30 seconds too slow to be able to connect with peers.
I synced my hwclock.
And now geth was able to sync
Then I terminated geth and started AKASHA back up and it managed to "find peers", and is now syncing correctly.
Probably worth adding to the FAQ and handling this scenario with an error message.
Edit: fully sync'd, no futher issues after hwclock sync, amazing dapp.
The text was updated successfully, but these errors were encountered: