Quote from: Tranz on October 23, 2013, 02:45:13 AM

Quote from: vasp on October 23, 2013, 01:47:13 AM

Quote from: Tranz on October 23, 2013, 12:38:22 AM

The getblocks message is normal an prints in everyone's debug. To be honest it should be under debug not general. I've made note of it.

The ERROR mempool message can be solved by shutting the daemon down and restarting. If that doesn't work, try it with a -rescan option. Let me know if neither of those helped.

Yes, sometimes its normal, but not in this case, see - there are same blocks requested by same clients, its repeated constantly, with very high speed.
And start blocks are 136263 and 136762 - they are in far past already.
In normal life i've never seen same requests with any other altcoins.

Yesterday already tryed restart pool wallet, doesnt helped with mempool error. Will try with rescan later.

There appears to be a bad client on the network. It is either on purpose or an old client. getblocks doesn't punish peers if they keep requesting the same blocks. I am pretty sure it is 70.98.114.237. I banned him via firewall and it stopped.

Blocking the IP did away with repeating getblocks messages for now.
The mempool messages are still rolling in after a wallet restart and a rescan.

MasterRuthless

Posts

Merits