[NEW] free rig-monitor 4.0 (alpha released) - page 7.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 20, 2018, 01:00:07 PM

Quote from: rodney2250 on May 20, 2018, 12:44:39 PM

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.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 20, 2018, 12:44:39 PM

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.

rodney2250

jr. member

Activity: 177

Merit: 2

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.

iLLNiSS

newbie

Activity: 30

Merit: 0

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 20, 2018, 07:43:41 AM

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 ((

Code:

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:

Code:

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
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"

tradersblog

newbie

Activity: 12

Merit: 0

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 ?

[/quote]

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 ((

Code:

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:

Code:

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
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 $

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 19, 2018, 12:42:59 PM

Quote from: rodney2250 on May 19, 2018, 12:24:07 PM

Quote from: tradersblog on May 19, 2018, 12:21:07 PM

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 ((

Code:

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"

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 19, 2018, 12:42:59 PM

Quote from: rodney2250 on May 19, 2018, 12:24:07 PM

Quote from: tradersblog on May 19, 2018, 12:21:07 PM

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 ((

Code:

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"

tradersblog

newbie

Activity: 12

Merit: 0

Quote from: rodney2250 on May 19, 2018, 12:24:07 PM

Quote from: tradersblog on May 19, 2018, 12:21:07 PM

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 ((

Code:

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

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 19, 2018, 12:21:07 PM

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 ((

Code:

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?

tradersblog

newbie

Activity: 12

Merit: 0

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 ?

[/quote]

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 ((

Code:

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 ?

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 19, 2018, 10:35:24 AM

Quote from: rodney2250 on May 18, 2018, 05:50:23 PM

Quote from: iLLNiSS on May 18, 2018, 05:30:28 PM

Quote from: rodney2250 on May 18, 2018, 02:07:35 AM

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/T0XUbxey

It 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/qkjGq8JR

I dumped you file in my simulator and is running fine.

Code:

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

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 19, 2018, 09:45:41 AM

Quote from: rodney2250 on May 16, 2018, 03:43:20 PM

Quote from: rodney2250 on May 16, 2018, 12:38:10 PM

Quote from: tradersblog on May 16, 2018, 12:08:06 PM

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

Code:

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}}}

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 18, 2018, 05:50:23 PM

Quote from: iLLNiSS on May 18, 2018, 05:30:28 PM

Quote from: rodney2250 on May 18, 2018, 02:07:35 AM

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/T0XUbxey

It 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/qkjGq8JR

tradersblog

newbie

Activity: 12

Merit: 0

Quote from: rodney2250 on May 16, 2018, 03:43:20 PM

Quote from: rodney2250 on May 16, 2018, 12:38:10 PM

Quote from: tradersblog on May 16, 2018, 12:08:06 PM

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

Code:

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 ?

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 18, 2018, 05:30:28 PM

Quote from: rodney2250 on May 18, 2018, 02:07:35 AM

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/T0XUbxey

It 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.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 18, 2018, 02:07:35 AM

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/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.

rodney2250

jr. member

Activity: 177

Merit: 2

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.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 16, 2018, 10:05:06 PM

Quote from: iLLNiSS on May 16, 2018, 05:02:05 PM

Quote from: rodney2250 on May 15, 2018, 03:53:30 PM

Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.

Finally got around to testing (had a burst pipe in the basement). It seems as though it's not picking up all the details for all rigs. It shows the hashrates fine for all the rigs, but it is only reporting the gpu temp and fanspeed for one of the rigs.

Ok. Please send me a trace and I’ll take a look at it.

https://pastebin.com/6McV8M08

At a quick glance I notice an error with parsing the GPU info. It's listing all the temperatures for all GPUs (line 43, 104 & 256) in the first GPU1 line instead of the standard GPU name info. The next parse with the hashrate (GPUs) is correct so that would explain why hashrates are working.

rodney2250

jr. member

Activity: 177

Merit: 2

Anyone using cgminer? I need some real json outputs to add support to rig-monitor.

Thanks

Topic: [NEW] free rig-monitor 4.0 (alpha released) - page 7. (Read 14736 times)