Too Much Peer Conflict for Transaction Cycle #204912

[smooj]

Anyone else getting this?

Too Much Peer Conflict for Transaction Cycle #204912.
This cycle will remain empty until repaired with valid data.

Transaction history is backing up...

[PoisonWolf]

Same. Mine, however, starts at 204807. It's affecting all my servers. Seems like there's some really bad data floating around the network.

[tiker]

My good server is stuck on 204879.

If I have time this evening, I see if I can quickly put together a script to view the contents of the transaction blocks from the various nodes and see what's causing it.

[smooj]

Looks like it has sorted itself out now.

[PoisonWolf]

Looks like it has sorted itself out now.

Can confirm, history walks show no errors from 204000 and up. It's always awesome to see the network wrestle and weed out the problematic transactions.

[tiker]

My good server was happy after a few hours.

The questions are; what caused it, why did it take over 100 transaction cycles before the servers noticed there was a difference in transactions (fork) and what transaction changes were done to fix the conflict?

Might be an idea for a new plugin - a log of transaction history changes done to fix transaction history hash conflicts.