Quote from: Blaksmith on March 24, 2016, 02:53:42 PM

Quote from: krile on March 23, 2016, 03:10:35 PM

Can someone explain this, the debug log is getting spammed constantly with this. In the last few months it grew to over 4,5GB in size. This is funny, the blockchain size is only 40MB, but the debug.log is over a hundred times bigger Cheesy

Code:

2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 43442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 43941 ddf6a90be42e923bdf533f7ee32e5c9ebc17cd6ea706b462bd61d65cf6792580
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30 getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30 getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30 getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65

I am killing this node if this does not get fixed.

Unfortunately, that was the results of the last forking that happened. You should be able to stop your catcoind, and restart it. While it is stopped, you can delete your debug.log to free up your hdd space. You may also want to delete your peers.dat file too, because it is still hooking on to the old forks, and your peer.dat file has old non-updated nodes listed.

Thanks for the tip. Deleted the peers.dat, for now the debug log is giving normal output. But the last time I just restarted the daemon, and it was ok in the beginning, but after a day or two it started spamming again...

Wouldnt it be a good idea to make the nodes disconnect from the outdated ones?