- changed status to resolved
Blacklisting seems not working
Issue #35
resolved
I recently see debug strings like these:
#!
...
[2014-02-11 13:10:56.388] DEBUG: Failed to accept block 1649430757733691096 at height 63731 received from nxt1.servebeer.com, blacklisting
[2014-02-11 13:10:56.388] DEBUG: Blacklisting nxt1.servebeer.com because of: Invalid timestamp: 6808384 current time is 6808256, previous block timestamp is 6808209
[2014-02-11 19:46:53.128] DEBUG: Failed to accept block 9496090578225855760 at height 63937 received from nxt1.servebeer.com, blacklisting
[2014-02-11 19:46:53.129] DEBUG: Blacklisting nxt1.servebeer.com because of: Invalid timestamp: 6832032 current time is 6832013, previous block timestamp is 6831942
[2014-02-11 19:46:54.758] DEBUG: Failed to accept block 9496090578225855760 at height 63937 received from 77.207.118.69, blacklisting
[2014-02-11 19:46:54.758] DEBUG: Blacklisting 77.207.118.69 because of: Invalid timestamp: 6832032 current time is 6832015, previous block timestamp is 6831942
, but these peers actually never disappear from "active peers" (and not appear in "blacklisted peers").
Comments (1)
-
repo owner - Log in to comment
Fixed in 0.7.5. It was a problem with updating the UI and deactivating only, the blacklisting was working as intended.