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...
Too Much Peer Conflict for Transaction Cycle #204912
- PoisonWolf
- Posts: 186
- Joined: Fri Apr 12, 2013 10:39 am
Re: Too Much Peer Conflict for Transaction Cycle #204912
Same. Mine, however, starts at 204807. It's affecting all my servers. Seems like there's some really bad data floating around the network.
Re: Too Much Peer Conflict for Transaction Cycle #204912
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.
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.
Re: Too Much Peer Conflict for Transaction Cycle #204912
Looks like it has sorted itself out now.
- PoisonWolf
- Posts: 186
- Joined: Fri Apr 12, 2013 10:39 am
Re: Too Much Peer Conflict for Transaction Cycle #204912
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.smooj wrote:Looks like it has sorted itself out now.

Re: Too Much Peer Conflict for Transaction Cycle #204912
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.
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.