Blockchain doesn't catch up

slush0 commented 10 years ago

Hi,

after starting the server (leveldb, production), it connects to few nodes, download few thousands of blocks and then it stops syncing, no matter how log I wait.

2013-11-24 23:12:15,779 [DEBUG] CachedBlockStore Peer-thread-2 stored block 83288 000000000016ba320ad960dbd7aca7ebedd60e9cf8c8c8ae59760a6638a6d3cf 2013-11-24 23:12:15,779 [DEBUG] TxHandler Peer-thread-2 Removing 0 blocks 2013-11-24 23:12:15,779 [DEBUG] TxHandler Peer-thread-2 Pool size: 0 2013-11-24 23:12:15,779 [DEBUG] TxHandler Peer-thread-2 Adding 1 blocks 2013-11-24 23:12:15,779 [DEBUG] TxHandler Peer-thread-2 First seen in block: 819c95081d1e024df558211ea1680f7fded2c9614b7bf7428dbe5068bd67a966 2013-11-24 23:12:15,779 [DEBUG] TxHandler Peer-thread-2 Pool size: 0 2013-11-24 23:12:15,779 [DEBUG] ChainLoader Peer-thread-2 received block 000000000019d675d5b971a150c84a2dee43db5d8274e57d030e2875803fabcf from xxxxx/xxxxxxx:8333 2013-11-24 23:12:15,780 [DEBUG] CachedBlockStore Peer-thread-2 stored block 83289 000000000019d675d5b971a150c84a2dee43db5d8274e57d030e2875803fabcf 2013-11-24 23:12:32,400 [INFO] BitcoinPeer Peer-thread-7 Disconnected 'null' at xxxxx/xxxxxx:8333 2013-11-24 23:12:35,191 [INFO] BitcoinPeer Peer-thread-3 Disconnected '/Satoshi:0.8.3/' at xxxxxx/xxxxx:8333 2013-11-24 23:12:35,409 [INFO] BitcoinPeer Peer-thread-6 Disconnected 'null' at xxxxx/xxxxx:8333 2013-11-24 23:12:46,733 [INFO] BitcoinPeer Peer-thread-8 Disconnected 'null' at xxxxxxx/xxxxx:8333

That machine is on fiber optic so I don't expect local connection issues.
It does every time I stop and start server again
I see lot of disconnection messages, but there're still some open connections in netstat
I tried to raise open files limit to 40000, no difference

So far it looks like the node is misbehaving somehow, so it is banned by "new" ddos protection by other nodes. However I don't have any idea how to measure/debug that.

slush0 commented 10 years ago

I also raised the limit of "connections desired" = 50 to avoid connecting to some misbehaving nodes.

slush0 commented 10 years ago

I tried also older release (1.2), still no difference. First run freezed at block height 63000, second at 73000, third at ~78000 and so. Every run indexes less and less blocks.

bitsofproof commented 10 years ago

I use the node in slave more in production, that is behind a standard satoshi node. Try running with slave profile. That node never banned the BOP one so I do not think it misbehaves. It is not my priority at the moment to get it work naked on the network, but will follow up later.

bitsofproof / supernode

Blockchain doesn't catch up #49