So this seems like a fairly significant problem. Have twice downloaded 600K+ blocks or so only to have to start anew after this message. Most recently it was after killing the process (kill -9). Is there development underway to shield the blockchain from this sort of unexpected failure? Or perhaps something that could repair the last block (or remove it from the chain)?
BTW, what is the appropriate way to stop a geth process running in the background?
0 ·
Comments
I0701 14:17:04.905767 3160 backend.go:301] Protocol Version: 60, Network Id: 0
I0701 14:17:04.905912 3160 backend.go:311] Blockchain DB Version: 3
I0701 14:17:04.908619 3160 chain_manager.go:269] LastBlock (c3236a945234f51f51e3d267b990fcb7e67b2098f25d27d335b4b338fb43385f) not found. Recovering...
F0701 14:17:04.908690 3160 chain_manager.go:273] Recover failed. Please report
Emphasizing motoadicts's post: It would be really nice to get some advice from the developers if there is a more elegant way to stop a node which is running in the background rather than simply kill -9 ...
kill -SIGINT PID
. Killing a node with -9 will cause some issues and earlier version were not able to recover as you are pointing out.Current develop has some better recovery code. Another thing you could do is
geth recover #number
orgeth recover block_hash