search

JamesSmith2 / EthControlLinux

EthControl for mining rig monitoring remotely
8 stars 2 forks source link

API not responsive error #1

Open hhalim opened 6 years ago

hhalim commented 6 years ago

Getting this "API not responsive" error from EthControl regularly and lost monitoring completely. OS: Ubuntu 16.04 Miner: Claymore 10.2

2017/12/15 11:04:23 Getting config info from EthMonitoring.com
2017/12/15 11:04:23 EthMonitoring.com config api response error
2017/12/15 11:04:24 API not responsive..
2017/12/15 11:04:27 API not responsive..

This error seems to happen when the claymore miner sets to restarts itself every several hours, then the ethcontrol is unable to regain API monitoring. The claymore miner is fully working when the EthControl shows the error, it keeps on mining and using the command line to access port 3333 also works and return a result.

curl "http://127.0.0.1:3333"

The claymore configuration in use:

-epool eth-us-east1.nanopool.org:9999 -ewal [XXXXXXXX] -epsw x -r 360 -minspeed -10 -dbg 0 -gser 1 -wd 0 -tt 70 -tstop 85 -ttli 80 -mode 1 -ftime 10 -mport -3333

Maybe add a graceful recovery after a restart? Or should I not even use the restart option -r 360, which I'll try, but EthControl should be able to handle a restart from claymore.

JamesSmith2 commented 6 years ago

Hey, sorry for delay, didn't get any messages. Socket response also works? It can send out two different types.

hhalim commented 6 years ago

How do you check for socket response? I think it works fine, since I can SSH remotely into the server after it produced the error. Also switching to stand alone claymore miner without ethcontrol works fine without rebooting. Let me know if you want me to try specific test for the socket response. Thanks!