Closed gim913 closed 10 years ago
what was the command line us used?
iirc, mx2g and for sure: leveldb production BCSAPI activemq
logs indicate that similar issue happened later, between 4am and 9am:
2014-01-04 03:33:00,939 [DEBUG] TxHandler Peer-thread-6 Pool size: 0
2014-01-04 03:33:01,155 [DEBUG] ChainLoader Peer-thread-9 received block 00000000003991f5b74a110923b7ff8c1f3db76ef0d54b427ba5b87ab0b0a313 from dnsseed.bitcoin.dashjr.org/220.189.203.68:8333
2014-01-04 03:33:01,156 [DEBUG] CachedBlockStore Peer-thread-9 stored block 72338 00000000003991f5b74a110923b7ff8c1f3db76ef0d54b427ba5b87ab0b0a313
2014-01-04 03:49:56,199 [INFO] BitcoinPeer Peer-thread-4 Disconnected 'null' at seed.bitcoin.sipa.be/220.189.203.68:8333
2014-01-04 03:58:38,336 [INFO] BitcoinPeer Peer-thread-12 Disconnected 'null' at seed.bitcoin.sipa.be/98.118.96.18:8333
2014-01-04 04:06:02,670 [INFO] BitcoinPeer Peer-thread-6 Disconnected 'null' at dnsseed.bitcoin.dashjr.org/150.140.159.77:8333
2014-01-04 04:06:53,111 [INFO] BitcoinPeer Peer-thread-12 Disconnected 'null' at dnsseed.bluematt.me/222.184.35.23:8333
2014-01-04 04:07:23,770 [INFO] BitcoinPeer Peer-thread-6 Disconnected 'null' at dnsseed.bluematt.me/208.81.1.197:8333
I suggest running as a slave behind satoshi in production, that is command line leveldb slave production BCSAPI activemq
Can not reproduce. I am afraid, that the remedy will be coming with the headers-first download.
I was thinking about slave already, but I was hoping there'll be chance to get rid of bitcoind.
Thanks for answer!
it seems, that for some reason threads are not reconnecting, here's a piece from log:
I don't know if this is related to issue #41 or not
from 01:30-03:20 nothing happened, later I restarted server.