Quote from: MasterRuthless on October 22, 2013, 11:59:41 PM

Quote from: vasp on October 22, 2013, 11:08:04 PM

Also, there are some bug in network i think.
debug.log on pool wallet spammed with this messages:

getblocks 133263 to 00000000000000000000 limit 500
  getblocks stopping at limit 133762 000000005baeb4f22781
getblocks 138763 to 00000000000000000000 limit 500
  getblocks stopping at limit 139262 000000020c092152544f
ERROR: mempool transaction missing input
getblocks 136263 to 00000000000000000000 limit 500
  getblocks stopping at limit 136762 00000000157c4e7cdd98
getblocks 139263 to 00000000000000000000 limit 500
  getblocks stopping at limit 139762 000000017127b2ca603a
ERROR: mempool transaction missing input
getblocks 136763 to 00000000000000000000 limit 500
  getblocks stopping at limit 137262 00000001180089e6dd22
getblocks 139763 to 00000000000000000000 limit 500
  getblocks stopping at limit 140262 000000002f37c5abec8e
ERROR: mempool transaction missing input
getblocks 136263 to 00000000000000000000 limit 500
  getblocks stopping at limit 136762 00000000157c4e7cdd98

Its constantly repeated many times (5-10) every second for all last days!
What can be wrong?
Especially with this error "ERROR: mempool transaction missing input"
How to get this error out?

I can confirm this mine is filling up with these errors as well but at a far faster rate than 5-10 seconds.
My debug.log I just noticed entered the gigabyte size range.

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.