So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is: ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas? I had that problem before. Are you running it on a laptop? Check your power settings. |
|
|
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info Still 0s in grafana, but the grm message is slightly different: INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded! INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded! version 2.0 517792 OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build. |
|
|
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info |
|
|
|
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it. Here is the html output from phoenix: https://pastebin.com/m4WEtyrRHere is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config: https://pastebin.com/Y6UkYAkZThe only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay). Try version 2.1.d15 |
|
|
|
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it. Here is the html output from phoenix: https://pastebin.com/m4WEtyrRHere is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config: https://pastebin.com/Y6UkYAkZThe only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay). Got it. Now I am able to reproduce it. |
|
|
|
Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
[/quote] I PM'd you. The latest 2.1d14 version should fix the data insertion into influx [/quote] I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 [/quote] ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot this on a trial and error basis ... Which OS are you using? |
|
|
|
Now it runs endless and when I interrupt I got this: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
File "external/tplink.py", line 71, in <module>
sock_tcp.connect((ip, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $
I meant after creating the new version of tplink2.0, could you run it and send me the output? >python external/tplink2.0.py -t 192.168.0.4 -c "info" running with new tplink code gives me this error: INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76: Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!
Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv[/quote] Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
[/quote] I PM'd you. The latest 2.1d14 version should fix the data insertion into influx |
|
|
|
On my cell now so it’s hard to read the traces.
So is phoenixminer working properly now?
Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config?
It's working properly, but only with 3 rigs. Any more and it throws errors. I've tried with and without the "," after the last rig line and all others have a "," after them. Forgot to mention, I sent a link to my config via PM. Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3. Are you running the same version of PhoenixMiner on all miners? If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig. |
|
|
|
Check the config file. You probably have 2 "[" at the end.
should have only one. It was a typo on the release.
I removed the second ] before I was even getting any errors. There is no second ] at the end like in the original config on your release. Here is a trace without the index flag set: https://pastebin.com/srpaxU1XHere is a trace with the index set to 4 to match the 4 in the config: https://pastebin.com/xEkZHLurIt seems as though despite specifying the index to allow the program to run without error, it doesn't actually do anything after. As I was typing this and verifying all my ducks were in a row before submitting, I found the issue. The 'riglist = [ ]' section throws an error when I have 4 rigs added. Removing 1 and the app runs just fine. On my cell now so it’s hard to read the traces. So is phoenixminer working properly now? Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config? |
|
|
|
|
Check the config file. You probably have 2 "]" at the end.
should have only one. It was a typo on the release.
|
|
|
|
Now it runs endless and when I interrupt I got this: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
File "external/tplink.py", line 71, in <module>
sock_tcp.connect((ip, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $
I meant after creating the new version of tplink2.0, could you run it and send me the output? >python external/tplink2.0.py -t 192.168.0.4 -c "info" [/quote] running with new tplink code gives me this error: INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76: Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!
[/quote] Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv |
|
|
|
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.
I need to improve that error handling.
Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already. About hat error, there’s a double square bracket at the end. It’s a typo. If you delete one of them then it fixes it. |
|
|
|
|
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.
I need to improve that error handling.
|
|
|
|
Now it runs continuously with nohup! But I got issues with tplink:
INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF
do I have to set something or modify the firmware of HS110 ?
I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues. Could you run this from within the grm dir and send me the output? python external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}' You should get something like this: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}} [/quote] Thanks, but this is the output (( pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received:
the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999" Firmware version is 1.5.2 and hardware 2.0 Any ideas ? And this one "python external/tplink.py -t 192.168.1.99 -c "info" ? Which model exactly are you using? [/quote] Still void: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info" Sent: {"system":{"get_sysinfo":{}}} Received: I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs[/quote] Paste this https://pastebin.com/27avXMEa into a file called external/tplink2.0.py and run it e.g. python external/tplink2.0.py -t 192.168.0.4 -c "info" [/quote] Now it runs endless and when I interrupt I got this: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
File "external/tplink.py", line 71, in <module>
sock_tcp.connect((ip, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $
[/quote] I meant after creating the new version of tplink2.0, could you run it and send me the output? >python external/tplink2.0.py -t 192.168.0.4 -c "info" |
|
|
|
Now it runs continuously with nohup! But I got issues with tplink:
INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF
do I have to set something or modify the firmware of HS110 ?
I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues. Could you run this from within the grm dir and send me the output? python external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}' You should get something like this: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}} Thanks, but this is the output (( pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received:
the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999" Firmware version is 1.5.2 and hardware 2.0 Any ideas ? And this one "python external/tplink.py -t 192.168.1.99 -c "info" ? Which model exactly are you using? Still void: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info" Sent: {"system":{"get_sysinfo":{}}} Received: I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs[/quote] Paste this https://pastebin.com/27avXMEa into a file called external/tplink2.0.py and run it e.g. python external/tplink2.0.py -t 192.168.0.4 -c "info" |
|
|
|
Now it runs continuously with nohup! But I got issues with tplink:
INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF
do I have to set something or modify the firmware of HS110 ?
I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues. Could you run this from within the grm dir and send me the output? python external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}' You should get something like this: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}} Thanks, but this is the output (( pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received:
the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999" Firmware version is 1.5.2 and hardware 2.0 Any ideas ? And this one "python external/tplink.py -t 192.168.1.99 -c "info" ? Which model exactly are you using? Still void: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info" Sent: {"system":{"get_sysinfo":{}}} Received: I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs[/quote] I found the culprit. TP-Link 2.0 uses a slightly diff encryption. I'll need to adjust it. I'll have a fix tomorrow at latest. In the mean time I suggest you set it to "noplug" |
|
|
|
Now it runs continuously with nohup! But I got issues with tplink:
INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF
do I have to set something or modify the firmware of HS110 ?
I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues. Could you run this from within the grm dir and send me the output? python external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}' You should get something like this: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}} [/quote] Thanks, but this is the output (( pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received:
the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999" Firmware version is 1.5.2 and hardware 2.0 Any ideas ? [/quote] And this one "python external/tplink.py -t 192.168.1.99 -c "info" ? Which model exactly are you using? |
|
|
|
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxeyIt seems to be picking up the info, but still not parsing it correctly. Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that up. Could you also send me the html output? Please make sure it’s complete and with the html tags. This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JRI dumped you file in my simulator and is running fine. TRACE: 2018/05/19 17:53:25 phoenixminer.go:165: Miner(PhoneixMiner) response from rig07:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:169: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:170: Eth speed: 238.965 MH/s, shares: 9508/0/0, time: 114:54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:173: GPUs: 1: 30.173 MH/s (1203) 2: 30.180 MH/s (1218) 3: 29.105 MH/s (1182) 4: 30.175 MH/s (1217) 5: 29.105 MH/s (1132) 6: 30.034 MH/s (1226) 7: 30.176 MH/s (1187) 8: 30.016 MH/s (1143)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:174: Eth: Average speed (5 min): 239.036 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:175: Eth: Maximum difficulty of found share: 37.8 TH (!!!)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:176: Eth: Effective speed: 229.84 MH/s; at pool: 229.84 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 1
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[1] Model: Radeon RX 570 Series (pcie 1)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[1] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[1] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[1] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 2
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[2] Model: Radeon RX 570 Series (pcie 2)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[2] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[2] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[2] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 3
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[3] Model: Radeon RX 570 Series (pcie 3)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[3] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[3] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[3] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 4
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[4] Model: Radeon RX 570 Series (pcie 4)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[4] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[4] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[4] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 5
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[5] Model: Radeon RX 570 Series (pcie 5)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[5] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[5] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[5] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 6
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[6] Model: Radeon RX 570 Series (pcie 6)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[6] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[6] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[6] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 7
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[7] Model: Radeon RX 570 Series (pcie 8)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[7] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[7] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[7] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 8
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[8] Model: Radeon RX 570 Series (pcie 9)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[8] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[8] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[8] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:187: PhoenixMiner line to parse: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:317: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[0] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[0] fan: 44
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[1] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[1] fan: 47
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[2] temperature: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[2] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[3] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[3] fan: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[4] temperature: 58
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[4] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[5] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[5] fan: 55
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[6] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[6] fan: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[7] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[7] fan: 54
Which version are you running? try with the latest 2.1.d.12 |
|
|
|
Hi, I'm get some errors when rig-monitor tries to get data from nanopool. Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range
goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
/Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
/Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
/Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits when I'm running without pool data -p -1 it's OK Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ? I noticed the same in my test setup and have created an issue ( https://github.com/rodneymo/rig-monitorv2/issues/14) to handle these failures gracefully. I suggest you disable it in the meantime. I'll have a fix for it tomorrow. check version 2.1.d.9. It should be fixed now. Now it runs continuously with nohup! But I got issues with tplink: INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded! ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF do I have to set something or modify the firmware of HS110 ? I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues. Could you run this from within the grm dir and send me the output? python external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}' You should get something like this: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}} |
|
|
|
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.
Anyways, it's been fixed in 2.1.d10.
Let me know if you have any other problems.
Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxeyIt seems to be picking up the info, but still not parsing it correctly. Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that up. Could you also send me the html output? Please make sure it’s complete and with the html tags. |
|
|
|
|
Show Posts
