Show Posts
Hello mikaelh, i have checked debug.log on all servers, no errors. They are not using the same wallet.dat file. Haveged package is installed on all instances to ensure entropy/no duplicate work. They are all synced with the network. If sieve options are not causing the issue the only thing i have not done is recreate peers.dat file to get a fresh list of nodes on every server. Would it be better to point all mining servers to one under my control, with a -connect= flag in the config or leave node selection default ?
I have switched them all to mining litecoin since my last post but will soon switch them back. Let me know If there is anything else you'd like me to test.
I have switched them all to mining litecoin since my last post but will soon switch them back. Let me know If there is anything else you'd like me to test.
If every miner is using a separate wallet, then you shouldn't have issues with running out of pre-generated keys. If your wallets are encrypted, then you may run out of keys because the wallet needs to be unlocked before new keys can be generated.
Connectivity is also important because mining will stop if the wallet loses all connections. Using the -connect parameter is probably a bad idea because it introduces a single point of failure. If your central node crashes, then all the slave nodes lose connectivity. You should use -addnode if you want to have a central node.
I looked at the code a bit and I spotted a potential issue with shared wallet mining. The issue is that N mining threads are probably using the first N keys available in the wallet. If multiple machines are using the same wallet, they may be trying to solve the same block if the timestamp and the extra nonce are the same. I can write a fix for that but it's unlikely to help you since you're using separate wallets.
That's all the ideas I have currently.
We use separate wallets + they were all generated using -keypool=5000 , so each can hold up to 5000 transactions. Now the important part :
Just before i switched back to XMP mining i came accross a post about haveged!: https://bitcointalk.org/index.php?topic=255782.msg2899987#msg2899987
I killed it on all servers, started mining, and in less than one hour 1 block found. Now how does that explain found blocks before 22. Dec - well i do recall killing haveged manually on all servers on several occasions so
it most probably was not running on all servers. What i do know for sure is that all servers were rebooted on 22. Dec and several times after, chkconfig shows haveged as on so it started automatically.
I will post an update tomorrow.
Regarding conectivity, if wallet loses all connections, wouldnt it be trying to reconnect indefinitely, using peers.dat file ? I've had machines lose conectivity for hours and reconnect just fine.
