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

[rodney2250]

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]

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]

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.

[Germini]

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

[rodney2250]

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.

[rodney2250]

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

[iLLNiSS]

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]

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.

[rodney2250]

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

[iLLNiSS]

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.

[sergey1301]

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.

[rodney2250]

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]

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!

[iLLNiSS]

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!

I use a script to simplify the influx and grafana install for raspberry pi (tested on raspbian stretch) if you're having any trouble installing them.

Code:

# Create InfluxDB and Grafana 4.4.3 (latest)
source /etc/os-release
OPSYS=${ID^^}
curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
test $VERSION_ID = "8" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
test $VERSION_ID = "9" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
curl https://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv6"* ]] && echo "deb https://dl.bintray.com/fg2it/deb-rpi-1b jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv7l"* ]] && echo "deb https://dl.bintray.com/fg2it/deb jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
sudo apt-get -y $AQUIET remove --purge grafana grafana-data
sudo apt-get -y $AQUIET autoremove
sudo apt-get -y update && sudo apt-get install -y apt-transport-https curl influxdb grafana
sudo systemctl daemon-reload
sudo systemctl enable influxdb
sudo systemctl start influxdb
sudo systemctl enable grafana-server
sudo systemctl start grafana-server

And if you're looking to set up rig monitor as a system service, here is a systemctl service file you can create (/lib/systemd/system/grm.service). Just make sure to set the execstart and workingdirectory to where your grm files are. If you do not set the workingdirectory grm will error out that it can't locate your config file even if you specify the location with -config.

Code:

[Unit]
Description=Rig Monitor
After=multi-user.target

[Service]
Type=idle
WorkingDirectory=/opt/grm
ExecStart=/opt/grm/grm

[Install]
WantedBy=multi-user.target

After creating the file do a daemon-reload, enable the service and start the service.

[rodney2250]

Would you mind if I add this to future release packages? Of course I'll add the necessary info and license about the author

[rodney2250]

For those of you using CastXMR, version 2.1.2 has been released.  It adds support for "mining_time" and updates the "Rig Overall status" panel on the respective dashboard template.

[iLLNiSS]

Would you mind if I add this to future release packages? Of course I'll add the necessary info and license about the author

I didn’t create the script, it was sourced from here:
https://tech.scargill.net/grafana-and-influxdb/

If that’s what you’re referring to.

[rodney2250]

Hi all,

I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.

If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2

[rodney2250]

I have just create a mining overview example dashboard that combines rig, pool and market data. See picture below. This example will be included in future releases, but in the meantime you can download it from here https://github.com/rodneymo/rig-monitorv2/issues/10

[rodney2250]

I just published a post on the blog explaining the power management feature. You can read about it here: https://www.rigmonitor.app/blog/using-rig-monitors-power-management-feature/