You were the canary in the coal mine.
Topic: New DDOS strategy being used? Repeated block count request? (Read 1937 times)
Heh - well - at least I now know what that DB error was ... I'm running 0.7.0
It was the 0.7 vs 0.8 hard fork
The hard fork occurred at block 225430 (after 225429)
It was the 0.7 vs 0.8 hard fork
The hard fork occurred at block 225430 (after 225429)
Firstly ... the IP address doing it was: 50.98.149.227
I'm running a modified bitcoind 0.7.0 (still)
I got this error a few times in the log:
)
I run multiple bitcoind, so I killed one off and restarted it.
Then I watched the log for a while ...
6 minutes after I restarted bitcoind, I kept seeing:
03/11/13 23:27:42 getblocks 217373 to 00000000000000000000 limit 500
03/11/13 23:27:42 getblocks stopping at limit 217872 00000000000004b61fe2
But the block start number would climb up to current then start again back around 210373
Then repeat this process over and over continuously.
My guess is that message is a request from a remote bitcoind?
(not a bug in 0.7.0 asking for blocks it already has?)
After a bit longer I got the above error I mentioned (when it tried to do a REORGANIZE)
Anyway for the time I was watching it - (12 minutes) - I got 794 of these block list requests from the same IP address I listed above.
I blocked the IP in my firewall and the requests all stopped immediately - so I obviously had the correct IP address.
I'm running a modified bitcoind 0.7.0 (still)
I got this error a few times in the log:
Code:
EXCEPTION: 11DbException
Db::put: Cannot allocate memory
bitcoin in ProcessMessages()
Which alerted me (p2pool actually was what alerted me Db::put: Cannot allocate memory
bitcoin in ProcessMessages()
)I run multiple bitcoind, so I killed one off and restarted it.
Then I watched the log for a while ...
6 minutes after I restarted bitcoind, I kept seeing:
03/11/13 23:27:42 getblocks 217373 to 00000000000000000000 limit 500
03/11/13 23:27:42 getblocks stopping at limit 217872 00000000000004b61fe2
But the block start number would climb up to current then start again back around 210373
Then repeat this process over and over continuously.
My guess is that message is a request from a remote bitcoind?
(not a bug in 0.7.0 asking for blocks it already has?)
After a bit longer I got the above error I mentioned (when it tried to do a REORGANIZE)
Anyway for the time I was watching it - (12 minutes) - I got 794 of these block list requests from the same IP address I listed above.
I blocked the IP in my firewall and the requests all stopped immediately - so I obviously had the correct IP address.
Jump to: