pkreuzt
pkreuzt
But I'm using the official binary linux-x64 version downloaded from GitHub. And of course, the SHA256 sum is correct.
It seems to be related to the blockchain. If I backup it to another location and start from the beginning, it begins syncing correctly. Is it common to have connection...
Well, I downloaded it from this same place and checked the signed hash of the tar.bz2 file on https://web.getmonero.org/downloads/hashes.txt . Status command reports: `Height: 1991442/1991442 (100.0%) on mainnet, not mining,...
I have already tried that, no difference.
Here it is: [bitmonero.log](https://github.com/monero-project/monero/files/3979104/bitmonero.log)
I usually do, but not this time. I had to sync from an old backup at about 85% and doing it via tor was too slow.
News on this, I discarded blockchain and synced again from that old backup, but this time with: `$ monerod --db-sync-mode safe` Now it's working well so far. So definitely it...
Interestingly, the daemon seems to work only with an old p2pstate.bin file. If I delete it (which is recommended when using Tor) then I get those "connect failed" messages and...
I've been syncing from scratch again (with --db-sync-mode safe) and making some periodic tests, cleanly stopping monerod and erasing p2pstate.bin (after saving it apart) to verify it keeps syncing and...