Go-ethereum: Synchronisation failed: no peers to keep download active - will this resolve?

[thebashfeed]

I read another, closed thread with a similar issue, but it did not solve my problem. Forgive me for my ignorance but I'm pretty new to how this works.

I'm trying to run the synchronisation program (geth --rpc) in the cmd console. It was working fine up until about #820919, at which point it gave me the following error message:

Synchronisation failed: no peers to keep download active

Will it resolve itself, or do I have to start the whole process over again? I've been running it all day so I'm hoping there's a simple fix for this issue...

[karalabe]

Yes, it will resolve itself.
You can also restart it, it will continue where it left off.
You could have used --fast option, which finishes in 20 minutes :P (only allowed on an empty database)

[MaxXor]

Same issue for me. After about 30-40mins syncing the blockchain the same error apppears and I'll need to restart geth.

[Bubleek]

Same issue for me too! I think this is a bug, but i don't know where this bug(in windows, in internet connection or in geth or somewhere). I'm put new issue in mist folder, but @frozeman close it and recomend put it issue here.
https://github.com/ethereum/mist/issues/171

[MaxXor]

I had to restart geth now over 100 times to finish the synchronization... now it's working flawlessly when a newly generated block is imported.

[thebashfeed]

Yes, it resolved after restarting a couple of times. Once it fully syncs it has zero issues. Now I just need to upgrade my GPU and I'll be good to go!

Thanks for the responses everyone.

[fjl]

This should be resolved as of geth 1.3.5.

[ycUygB1]

I have this problem with 1.3.5

[canadaduane]

I'm seeing this on 1.3.5 as well. Possibly related: the last time I tried to quit geth, it stalled for a long time (10 min?) and then ended with a "panic". I'm wondering if my db is corrupt as a result, and possibly related to this issue.

[canadaduane]

Turns out my clock was off by about 60 seconds.

[jamesmorgan]

I've just reset my clock (Mac OSX) and it kicking back into full speed, flying through now. 👍

[srw]

@jamesmorgan @canadaduane good catch! my clock was only off by ~20 seconds and the problem arised too.

[gorilla2112]

Im getting both 'no peers' error AND 'Synchronisation failed: leveldb/table: corruption on data-block (pos=0): checksum mismatch, want=0x8f40a97e got=0x792b89e6 [file=4762443.ldb]'

Cant get it to sync for anything. Thoughts?

[obscuren]

Table corruption occurs when there are partial writes due to sudden shutdowns. Could that be the case? Have you had a sudden shutdown prior to getting this message?

[lklancir]

I'm also getting this "no peers" error on the --fast mode. It imports like 3-5k transactions and then it snaps? Could it really be that the network is overloaded due to DAO hype?

--EDIT it must have been a problem with the ISP or the internal network for downloading the data. I have now switched to my mobile 4G and its going great. If you have similar problems try switching wireless/network somewhere else

[fluidvoice]

Happens constantly for me (in Brazil). Maybe a lack of peers nearby? It's annoying as hell. Even with --fast option I've been trying to sync for two days. It's completely unusable for me. I'm running the latest (Beta) geth as of now.

[holgerkpedersen]

There's a LOCK file in the chaindata that might be deleted to get the autosynch going again. But, I'm not sure what consequences it can have in other situations. But, I suspect it has something to do with timing of writing to the file and the progress of the import of blocks