Open chfast opened 5 years ago
Is full logging enabled (-v4)?
Which network was that? Could be expected, if it keeps connecting to the single node from another network
Mainnet. I think the faulty header was already in the database.
I am starting to play with aleth. I set up two instances on different VMs, but otherwise followed the example of creating a local chain -- instead of localhost and a new port, I point at the IP address of the mining host, and use the same port on both.
I hit the error reported here and found this page via a search. I see a comment that it could happen if connecting to one node, but no explanation why that would be expected. I turned on -v4 and got things like the following. Any suggestions?
DEBUG 02-04 21:40:09 p2p blockhdr Expected trie root: 56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421
DEBUG 02-04 21:40:09 p2p blockhdr Expected uncle hash: 1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347
TRACE 02-04 21:40:09 p2p bq Block #a96c66b1? is 2 parent is #c37894c1?
TRACE 02-04 21:40:09 p2p bq OK - queued as unknown parent: #c37894c1?
DEBUG 02-04 21:40:09 p2p sync 0 imported OK, 0 with unknown parents, 0 with future timestamps, 0 already known received.
DEBUG 02-04 21:40:09 p2p sync Already known or future time & unknown parent or unknown parent, block #2. Resetting `sync.
Thanks.
I'll add that I think I've gotten around this by removing ~/.ethereum on the non-mining host and restarting aleth with no existing chain. It seems happier now.