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

sergey1301

jr. member

Activity: 336

Merit: 1

Quote from: rodney2250 on May 27, 2018, 03:07:31 AM

Quote from: sergey1301 on May 27, 2018, 03:05:48 AM

I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

Hi Sergey,

you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/

Thank you!

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: sergey1301 on May 27, 2018, 03:05:48 AM

I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

Hi Sergey,

you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/

sergey1301

jr. member

Activity: 336

Merit: 1

I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 26, 2018, 02:31:06 AM

About the timeout, I think we need to rule out a grm issue as I have been running it on a raspberry PI 1 for almost days without issues.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?

I'll. take a look at the Nvidia output and provide you a fix.

With 2.1.0 it has stopped crashing on me and has now been running for 13 hours, so that's good

With 2.1.1 the fanspeed issue is resolved on my end. Good work. Your efforts are much appreciated.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 25, 2018, 11:58:32 PM

Quote from: rodney2250 on May 25, 2018, 10:11:03 AM

Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.

Fix in 2.1.1

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 25, 2018, 11:58:32 PM

Quote from: rodney2250 on May 25, 2018, 10:11:03 AM

Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.

About the timeout, I think we need to rule out a grm issue as I have been running it on a raspberry PI 1 for almost days without issues.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?

I'll. take a look at the Nvidia output and provide you a fix.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 25, 2018, 10:11:03 AM

Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.

rodney2250

jr. member

Activity: 177

Merit: 2

Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 23, 2018, 08:16:26 PM

Quote from: rodney2250 on May 23, 2018, 12:02:19 AM

Quote from: iLLNiSS on May 22, 2018, 06:08:47 PM

Quote from: rodney2250 on May 22, 2018, 12:26:45 AM

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.

New (stable) version 2.1 has been released. That issue should be permanently fixed in that version. I have it running for many hours now and both influxDB connection as well as memory usage are stable.

Germini

newbie

Activity: 20

Merit: 1

Hi, I've been trying to customize the panels available from claymore and castxmr but when copying overall rig status from claymore to other dashboard I see that Mining Time has incorrect values. How to fix this?

After some debugging I realized that the query from the original panel is different than the copied one. Is there any way to make it the same?. Where to specify $timeFilter in the copied one?

in the query of the original panel it says:

Code:

"SELECT installed_gpus,active_gpus/installed_gpus,last(hr)*1000000, target_hr*1000000,"mining_time" FROM "miner_system" WH ERE miner='CLAYMORE' and time >= now() - 24h group by "rig_id""

in the query of the copied panel it says:

Code:

"SELECT installed_gpus,active_gpus/installed_gpus,last(hr)*1000000, target_hr*1000000,"mining_time" FROM "miner_system" WH ERE miner='CLAYMORE' and time >= 1527129649148ms and time <= 1527151249150ms group by "rig_id""

I separated the word WHERE to avoid blocking from forum

EDIT: The time range in the top right was between an old time that is the $timeFilter so that's why the values are outdated. I leave the post for anyone with the same problem to fixit.

Thanks for your work rodney2250!! Cheesy

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 23, 2018, 08:16:26 PM

Quote from: rodney2250 on May 23, 2018, 12:02:19 AM

Quote from: iLLNiSS on May 22, 2018, 06:08:47 PM

Quote from: rodney2250 on May 22, 2018, 12:26:45 AM

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.

Found some memory leaks, which have been fixed in 2.1.d17.

I have tested it on my raspberry PI 1 and it's been running fine for almost 3 hours now.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 23, 2018, 12:02:19 AM

Quote from: iLLNiSS on May 22, 2018, 06:08:47 PM

Quote from: rodney2250 on May 22, 2018, 12:26:45 AM

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 22, 2018, 06:08:47 PM

Quote from: rodney2250 on May 22, 2018, 12:26:45 AM

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the influx log

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 22, 2018, 12:26:45 AM

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

Nah, on an RPI.

rodney2250

jr. member

Activity: 177

Merit: 2

Hi all,

I have created a telegram group for the rigmonitor community. Here's the link: https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q

rodneymo

tradersblog

newbie

Activity: 12

Merit: 0

Quote

OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.

Quote

Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)

[/quote]

Have you check the power detail template dashboard? Are the values showed there correct?
[/quote]

I've uploaded the txt file of the output of the influxdb query >> http://textuploader.com/dfy1e

can you create a grm developing channel in telegram ? it's more simple to communicate with frequent messages and attachements...

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: tradersblog on May 22, 2018, 09:51:46 AM

Quote from: rodney2250 on May 21, 2018, 05:11:02 PM

Quote from: tradersblog on May 21, 2018, 05:09:34 PM

Quote from: rodney2250 on May 21, 2018, 04:02:10 PM

Quote from: tradersblog on May 21, 2018, 03:14:46 PM

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?

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:

Code:

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:

Code:

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.

Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)

Have you check the power detail template dashboard? Are the values showed there correct?

tradersblog

newbie

Activity: 12

Merit: 0

Quote from: rodney2250 on May 21, 2018, 05:11:02 PM

Quote from: tradersblog on May 21, 2018, 05:09:34 PM

Quote from: rodney2250 on May 21, 2018, 04:02:10 PM

Quote from: tradersblog on May 21, 2018, 03:14:46 PM

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?

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:

Code:

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:

Code:

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.

Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 21, 2018, 07:52:15 PM

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:

Code:

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.

iLLNiSS

newbie

Activity: 30

Merit: 0

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:

Code:

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?

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