When rebuilding the database...
addnode=70.79.24.157
was the only connection I got from YOUR list of nodes... This seems to be a rogue node.
Block-level is 53893 and rising... no other nodes in your list seem to have this height.
Time to look around and kill the rogue nodes, remove them from the many postings, and consider the following settings...
splash=0
server=1
gen=0
testnet=0
daemon=1
maxconnections=20
listen=1
Time to remove the addnodes... it is causing problems, because there is no way to enforce it, and the majority of large hashers seem to not be "listening" or "talking" to the network of your nodes. (Thus, they are building multiple solo chains, and not telling the outside world fast enough... or at all.)
Thus, many tall chains, from multi, from cryptsy, from anyone with three fast blocks or more, are creating branches that others see, only after the servers start talking to the outside world again. (After they have built stacks of private branches.)
If you don't add nodes, and LISTEN for more than the list of nodes you provide... (Obviously your nodes are not talking fast enough either... to each-other, or to the outside world.)... then you are aiding the issue. It only takes one person on both nodes to grab the longest one, and bring it back to the network, causing issues. Your nodes seem to ignore the fact that another chain is larger, and correct, forcing us to use the short ones they are attempting to "manage".
This issue goes back to the 27th... that is where the rogue node, listed above, stopped functioning. (Old code?)
Thank you for this. We have delayed the next release while we restructure a few things. Most of which you just mentioned. We are trying to get it out ASAP but want to make sure we have eliminated these issues as much as possible.
