Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Clique : Discarded bad propagated block#1 when syncing #14945
Geth Version: 1.6.7-stable
Sync block#1 successfully
Steps to reproduce the behaviour
Not sure if this occurs with POW.
I am having a similar issue with my multi-node PoA setup. I only have a single miner, mining interval set to 1 second, and the "bitchin tricks" mining hack is in place (only mine when there is a tx in the pool).
I send a transaction from a non-mining node, it propagates, and a block is subsequently mined with the transaction in it. Everything actually works great except for the two WARN messages I am seeing in the console:
Even though it says Synchronisation fails, it actually didnt. The block propagated successfully and the transaction was processed.
i am having same issue, with 3 signer/mining nodes and one node without mining that gives transactions, one of the mining nodes when a transaction is mined gives a "bad block unknown ancestor" and stops mining, whole network stucks after that
version 1.7.0 on commit (#14631)
From my understanding:
When the PM is being created, the
Note that the calling operation is:
That is, if the
referenced this issue
Jan 9, 2018
Any updates on this?
Reason: Some peers appeared when running
We also ran into many issues; we changed many things along the way, maybe something might solve your issue: