lolMiner-releases
lolMiner-releases copied to clipboard
Lolliedieb
lolminer does not properly reconnect after loss of communication with the pool.
Hi. lolminer does not properly reconnect after loss of communication with the pool. The log writes that the connection is established, but neither the host name nor the address is displayed. Only a full restart of the lolminer helps. This happens on both hiveos and raveos. Other miners (nbminer, t-rex, gminer) work without any problems. But I like lolminer.
Statistics (13:51:09); Uptime: 42h 11m 1s The api is active on port 44444 Mining: Ethash Connected to: eu1.ethermine.org:4444 (34ms latency)
GPU 1: Found a share of difficulty 126.12G GPU 3: Found a share of difficulty 8.60G GPU 5: Found a share of difficulty 17.53G Average speed (10s): 30.63 Mh/s | 31.00 Mh/s | 30.64 Mh/s | 30.64 Mh/s | 31.00 Mh/s | 31.01 Mh/s Total: 184.93 Mh/s Average speed (10s): 30.63 Mh/s | 31.00 Mh/s | 30.65 Mh/s | 30.65 Mh/s | 31.01 Mh/s | 31.00 Mh/s Total: 184.93 Mh/s Pool not reacting to submitted shares for too long. Reconnecting. Lost connection to stratum server eu1.ethermine.org:4444 or server not reachable. Trying to connect in 5 second(s) Average speed (10s): 20.97 Mh/s | 18.79 Mh/s | 9.38 Mh/s | 10.76 Mh/s | 15.82 Mh/s | 24.38 Mh/s Total: 100.10 Mh/s
Statistics (13:52:09); Uptime: 42h 12m 1s The api is active on port 44444 Mining: Ethash Connected to: (34ms latency)
Name Speed Pool Shares Best Eff. Power CCLK MCLK Core Junc Fan
Mh/s Mh/s A/S/Hw Share Mh/s/W W MHz MHz Temp Temp Pct
GPU 0 GTX 1660 Ti 26.47 31.10 1100/0/0 31.1T 0.689 38.4 1050 6801 47 58 60 GPU 1 GTX 1660 Ti 26.38 30.28 1070/1/0 41.6T 0.676 39.0 1050 6801 41 53 60 GPU 2 GTX 1660 Ti 27.10 29.03 1027/0/0 2.3T 0.756 35.8 1050 6801 48 60 60 GPU 3 GTX 1660 Ti 27.33 30.11 1065/0/0 3.5T 0.623 43.8 1050 6801 45 56 59 GPU 4 GTX 1660 Ti 25.89 31.30 1107/0/0 1.5P 0.566 45.7 1050 6801 43 55 60 GPU 5 GTX 1660 Ti 27.32 30.62 1083/0/0 3.9T 0.688 39.7 1050 6801 44 55 60
Total 160.48 182.44 6452/1/0 1451.2T 0.662 242.5
Average speed (10s): 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s Total: 0.00 Mh/s
Hi.
lolminer does not properly reconnect after loss of communication with the pool. The log writes that the connection is established, but neither the host name nor the address is displayed. Only a full restart of the lolminer helps. This happens on both hiveos and raveos. Other miners (nbminer, t-rex, gminer) work without any problems. But I like lolminer. Statistics (13:51:09); Uptime: 42h 11m 1s The api is active on port 44444 Mining: Ethash Connected to: eu1.ethermine.org:4444 (34ms latency)
GPU 1: Found a share of difficulty 126.12G
GPU 3: Found a share of difficulty 8.60G GPU 5: Found a share of difficulty 17.53G Average speed (10s): 30.63 Mh/s | 31.00 Mh/s | 30.64 Mh/s | 30.64 Mh/s | 31.00 Mh/s | 31.01 Mh/s Total: 184.93 Mh/s Average speed (10s): 30.63 Mh/s | 31.00 Mh/s | 30.65 Mh/s | 30.65 Mh/s | 31.01 Mh/s | 31.00 Mh/s Total: 184.93 Mh/s Pool not reacting to submitted shares for too long. Reconnecting. Lost connection to stratum server eu1.ethermine.org:4444 or server not reachable. Trying to connect in 5 second(s) Average speed (10s): 20.97 Mh/s | 18.79 Mh/s | 9.38 Mh/s | 10.76 Mh/s | 15.82 Mh/s | 24.38 Mh/s Total: 100.10 Mh/s Statistics (13:52:09); Uptime: 42h 12m 1s The api is active on port 44444 Mining: Ethash Connected to: (34ms latency)
Name Speed Pool Shares Best Eff. Power CCLK MCLK Core Junc Fan Mh/s Mh/s A/S/Hw Share Mh/s/W W MHz MHz Temp Temp PctGPU 0 GTX 1660 Ti 26.47 31.10 1100/0/0 31.1T 0.689 38.4 1050 6801 47 58 60
GPU 1 GTX 1660 Ti 26.38 30.28 1070/1/0 41.6T 0.676 39.0 1050 6801 41 53 60 GPU 2 GTX 1660 Ti 27.10 29.03 1027/0/0 2.3T 0.756 35.8 1050 6801 48 60 60 GPU 3 GTX 1660 Ti 27.33 30.11 1065/0/0 3.5T 0.623 43.8 1050 6801 45 56 59 GPU 4 GTX 1660 Ti 25.89 31.30 1107/0/0 1.5P 0.566 45.7 1050 6801 43 55 60 GPU 5 GTX 1660 Ti 27.32 30.62 1083/0/0 3.9T 0.688 39.7 1050 6801 44 55 60
Total 160.48 182.44 6452/1/0 1451.2T 0.662 242.5
Average speed (10s): 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s | 0.00 Mh/s Total: 0.00 Mh/s
We have found other people with that... it seems needs and improvement, in some cases doesn't work propoerly, did you have failsafe pool?.
No, I don't have a failsafe pool.
You could try to add also eu1.ethermine.org:14444
I have the same problem. All my 5 rigs stop mining in ubuntu.
Ethash: Average speed (15s): 43.32 Mh/s SHA256-TON: Average speed (15s): 1303.41 Mh/s No working connection for 300 seconds (Authorization or Work missing). Reconnecting.
I have the same problem. All my 5 rigs stop mining in ubuntu.
Ethash: Average speed (15s): 43.32 Mh/s SHA256-TON: Average speed (15s): 1303.41 Mh/s No working connection for 300 seconds (Authorization or Work missing). Reconnecting.
That is a pool problem... no work during 300s...
@jgonzis I keep having the same problem. It disconnects and never connects again. I have 3 separate rigs in the same location/connection and randomly one will lose connection to the pool and never get it back (while it continues mining ETH since I'm dual mining). Can you please try to replicate it and test it for yourselves?
Even if it's the pool's fault for the initial disconnection, it's lolminer's fault for never connecting again while we KNOW the pool status is not down.
Edit: sometimes even if I manually restart lolminer and it connects to the pool, it will not start mining TON and I have to restart another 1-2 times till it starts. I hope this gives you some hints for the potential bug. And I repeat: the pool is up and running, I am getting jobs and hashing on the rigs next to the one that stopped hashing TON.
@jgonzis I keep having the same problem. It disconnects and never connects again. I have 3 separate rigs in the same location/connection and randomly one will lose connection to the pool and never get it back (while it continues mining ETH since I'm dual mining). Can you please try to replicate it and test it for yourselves?
Even if it's the pool's fault for the initial disconnection, it's lolminer's fault for never connecting again while we KNOW the pool status is not down.
Edit: sometimes even if I manually restart lolminer and it connects to the pool, it will not start mining TON and I have to restart another 1-2 times till it starts. I hope this gives you some hints for the potential bug. And I repeat: the pool is up and running, I am getting jobs and hashing on the rigs next to the one that stopped hashing TON.
Hi, also with the new 1.49?
Could you share which pool are you using. It has been an Improvement in the last version
@jgonzis It doesn't have to do with pool. The issue persists in 1.51 and it affects more nvidia cards than amd apparently.
The only extra parameter I have on my dual mining .bat file is --silence 1
This issue happens with latest drivers of nvidia too, on other rigs that have nvidia only GPUs. I just wanted to show you that even on the same instance, AMD cards start mining TON along with ETH, but nvidia ones just ETH. So something else is at play here.
The only extra detail is that I'm mixing LHR/non-LHR cards in all rigs at the moment and maybe LHR ones cause the whole instance of lolminer to not start dual mining TON?
Hope this info helps you resolve this issue.
EDIT: With version 1.51, I added the --dualfactor parameter on those nvidia GPUs (for example 34.2,34,25,25) and now the dual mining starts correctly. So I guess the auto-tuning has an issue starting or finishing.
@jgonzis It doesn't have to do with pool. The issue persists in 1.51 and it affects more nvidia cards than amd apparently.
The only extra parameter I have on my dual mining .bat file is --silence 1
This issue happens with latest drivers of nvidia too, on other rigs that have nvidia only GPUs. I just wanted to show you that even on the same instance, AMD cards start mining TON along with ETH, but nvidia ones just ETH. So something else is at play here.
The only extra detail is that I'm mixing LHR/non-LHR cards in all rigs at the moment and maybe LHR ones cause the whole instance of lolminer to not start dual mining TON?
Hope this info helps you resolve this issue.
EDIT: With version 1.51, I added the --dualfactor parameter on those nvidia GPUs (for example 34.2,34,25,25) and now the dual mining starts correctly. So I guess the auto-tuning has an issue starting or finishing.
Yes one of the reason of --dualfactor is solve that problem on Windows users... the tunning is very sensitive and depending the Computers has been a nightmare... a really nightmare... I hope that factor helps on that.
I thought with the advent of new versions, the problem went away. But nothing has changed. If you cannot find the reason, please add an option, such as in nbminer, if no share has been received in a certain period, then restart miner. In general, it is not clear why this problem cannot be solved. lolminer, when he made an incorrect connection, shows that he connected to nowhere. Empty string. (In the log: "Connected to: (34ms latency)"). On this basis, you can understand that something went wrong.