Hello, I have this interesting setup: some computers on a LAN running minerd connected to a litecoind on one "server" and this litecoind is connected to a socks4 proxy running on a machine on different network. It looks like working and miners use 100%CPU. I have litecoind started with -printtoconsole so I see the messages. So it goes like this, but sometimes a strange problem occurs - like it cannot find any nodes to connect to or they all refuse connection or whatever.
3/16/2012 23:05 RandAddSeed() 204724 bytes
askfor block be6df48583638a9906cc 0
sending getdata: block be6df48583638a9906cc
askfor block be6df48583638a9906cc 1331939158000000
askfor block be6df48583638a9906cc 1331939278000000
askfor block be6df48583638a9906cc 1331939398000000
askfor block be6df48583638a9906cc 1331939518000000
askfor block be6df48583638a9906cc 1331939638000000
askfor block be6df48583638a9906cc 1331939758000000
received block be6df48583638a9906cc
Got new block at height 101269: be6df48583638a9906ccece66842a552b1bea62288c4905d
3992242f7a686df5
SetBestChain: new best=be6df48583638a9906cc height=101269 work=342909385960814
ProcessBlock: ACCEPTED
3/16/2012 23:06:01 Flushing wallet.dat
Flushed wallet.dat 62ms
askfor block b8d63b01d9525c94e8ca 0
sending getdata: block b8d63b01d9525c94e8ca
askfor block b8d63b01d9525c94e8ca 1331939168000000
received block b8d63b01d9525c94e8ca
Got new block at height 101270: b8d63b01d9525c94e8ca2b900ac8ad7ea53d11feedfe07d4
85e0870a0ac0cb63
SetBestChain: new best=b8d63b01d9525c94e8ca height=101270 work=342915682517571
ProcessBlock: ACCEPTED
3/16/2012 23:06:11 Flushing wallet.dat
Flushed wallet.dat 47ms
ResendWalletTransactions()
AddAddress(142.177.232.41:9333)
askfor tx c25a1dfb6ebd6d639426 0
sending getdata: tx c25a1dfb6ebd6d639426
askfor tx c25a1dfb6ebd6d639426 1331939345000000
AcceptToMemoryPool(): accepted c25a1dfb6e
askfor tx fb23dc6e2ff4460836b5 0
sending getdata: tx fb23dc6e2ff4460836b5
AcceptToMemoryPool(): accepted fb23dc6e2f
received getdata for: tx fb23dc6e2ff4460836b5
and here something goes wrong and continues like this
socket recv error 10054
disconnecting node 94.76.233.147:9333
socket recv error 10054
disconnecting node 130.160.47.113:9333
socket recv error 10054
disconnecting node 173.11.125.162:9335
trying connection 142.177.232.41:9333 lastseen=-2.1hrs lasttry=-369983.2hrs
proxy connecting 142.177.232.41:9333
socket recv error 10054
disconnecting node 87.106.180.211:9335
proxy connected 142.177.232.41:9333
connected 142.177.232.41:9333
socket recv error 10054
disconnecting node 178.254.3.19:9333
socket recv error 10054
disconnecting node 209.217.250.10:9333
socket closed
disconnecting node 142.177.232.41:9333
socket recv error 10054
disconnecting node 169.237.101.193:10333
trying connection 93.141.50.37:9333 lastseen=-6.5hrs lasttry=-369983.2hrs
proxy connecting 93.141.50.37:9333
socket recv error 10054
disconnecting node 178.33.28.54:10333
trying connection 184.72.90.135:9333 lastseen=-11.6hrs lasttry=-369983.3hrs
proxy connecting 184.72.90.135:9333
when these errors start appearing all miners connections are being refused and they stop working. litecoind getinfo shows connections:0. When it worked it was connections:8. Strangely it seems like restart of litecoind always helps, but this is useless if it randomly stops working like this and needs to be restarted
When there is this problem I can still start minerd and connect to a pool, so I don't know. The problem was happening even when I tested it without proxy, so it used different network. Is litecoin network unstable or what?
Now when it happened it was connections:0 for about 3minutes and then suddendly it went to connections:1 and miners started to work again...but only for about a minute before it broke again. Any ideas? I don't think there is a problem with local firewall, because disabling it does not help...
Or is there some list of stable nodes so I could configure it to connect to them to avoid problems finding some available nodes?
