Closed borzaka closed 3 years ago
Same exact problem.
Thanks for the report, we are working on a solution. This should be fixed with the upcoming NiceHash Miner release. Currently the best way to avoid this is to prevent the excavator from crashing.
@borzaka This is nhm2 bug we should have this fixed in the next upcoming release. Please keep this issue open and close it if the next upcoming release solves the problem.
This bug is also present on the Linux version of the excavator_1.5.5a (cryptonightv7 algorithm).
@khusnullin Does this happen after a share hasn't been found for quite some time (due too the high difficulty on cryptonightv7)? If that's the case, then it's not a bug. Stratum server will drop inactive connection after share hasn't been sent for x minutes, excavator will reconnect if everything is alright and continue mining.
@dropky
This happens when the miner is initialized. After ~5 minutes of downtime, usually the mining starts working.
In Windows excavator starts working immediately (with the same configuration file).
json:
[ {"time":0,"commands":[ {"id":1,"method":"subscribe","params":["nhmp.jp.nicehash.com:3200","hidden_wallet"]} ]}, {"time":2,"commands":[ {"id":1,"method":"algorithm.add","params":["cryptonightV7","hidden_wallet"]} ]}, {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["cryptonightV7","0"]}, {"id":1,"method":"worker.add","params":["cryptonightV7","1"]}, {"id":1,"method":"worker.add","params":["cryptonightV7","2"]}, {"id":1,"method":"worker.add","params":["cryptonightV7","3"]}, {"id":1,"method":"worker.add","params":["cryptonightV7","4"]}, {"id":1,"method":"worker.add","params":["cryptonightV7","5"]} ]}, {"time":10,"loop":10,"commands":[ {"id":1,"method":"worker.print.speed","params":["0"]}, {"id":1,"method":"algorithm.print.speeds","params":["0"]} ]} ]
@khusnullin Can you run excavator with -f 0 parameter and post here the log file? What version of driver are you using?
@dropky I looked at the logs... Sorry guys. Instead of json, the excavator reads garbage. The problem with the file system, not with the miner. Thanks for the support.
Sorry,it's my fault.i didn't see a typo in my config.
@S74nk0 hi when will solve the bug with NHM2?
Got same problem today.
This happens when connection with server is lost. Not a bug. Closing.
Basic information:
Problems I see:
End of file (2)
warning at the beginningThoughts:
Logs: log.txt