I am running Geth 1.8.1 on a Raspberry Pi 3 (yes I know people are saying that you cannot run a full Ethereum node on a Raspberry any more but I have not read any convincing arguments why it should not work to do a fast sync). I am having the exact same issue as cue0083. The wallet is telling me it doesn't know if it's synced or not? It's a bit strange, though, that I can see my address's state on etherscan, no outgoing transactions, but this is not shown in wallet: "If your balance doesn't seem updated, make sure that you are in sync with the network." Not what I expect as occasional end user. WARN Synchronisation failed, retrying err="header processing canceled (requested)"
INFO Imported new state entries count=384 elapsed=0s processed=11127 pending=10356 retry=384 duplicate=1 unexpected=165 INFO Imported new block headers count=0 elapsed=0s number=5111200 hash=da08e9…74d79d ignored=1 INFO Imported new block headers count=0 elapsed=0s number=5111199 hash=b3e461…d9db76 ignored=1 INFO Imported new block headers count=0 elapsed=0s number=5111198 hash=fa04b8…263d76 ignored=1 INFO Imported new state entries count=273 elapsed=0s processed=10743 pending=4369 retry=0 duplicate=1 unexpected=165 INFO Imported new block headers count=0 elapsed=0s number=5111197 hash=36486e…d94fc8 ignored=2 INFO Imported new block headers count=0 elapsed=0s number=5111195 hash=edc498…bb5428 ignored=1 INFO Imported new state entries count=444 elapsed=0s processed=10470 pending=21570 retry=0 duplicate=1 unexpected=165 Sample log dump indicates only the speed of block acquisition. Note: "Disk storage enabled for ethash DAGs" in console points to an inexistant path, while "Disk storage enabled for ethash caches" points to a correct custom path. Same result as above with -1024, with 4096 the OS starts swapping after a while, for some reason, even though all memory is not being used (memory leaks?). But it's not synced, at least that's what Mist thinks.Īfter several hours of running geth I tried using -cache=2048 and even 4096. Just does nothing at all, no messages in console, no cpu usage, batch job termination works, so it's not frozen. When I run Mist, geth seems to stop working after a while.
Seems to work a bit faster and causes less noise on HDD than geth 1.7.2, where it couldn't complete last n < 200 blocks. Geth catches up quickly, but never completes last n < 100 blocks. Now running with -cache=1048 -maxpeers=150. Used geth -fast -cache=1024 for initial sync. I run little or no apps on the machine, maybe some browser instances.ġ tb hdd, 64mb cache, used for eth blockchain only.ġ00 mbit eth -> optic internet connection