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

[rodney2250]

Ok. Please post a trace so I can look at the json and check how it’s being processed

Here ya go:

Thanks. Issue has been fixed on release 2.0.b.2. You can download it from GitHub

Thanks a lot man, now all the threads are showing up.
Let me know when you find a way to fix the supportxmr.com pool support.
I suppose one of the ways to do it could be just parsing the pool name and processing the json one way if its supportxmr or standard way if its not.

I'm trying to keep the binary file small. So I want to avoid duplication. I should have a solution by tomorrow.

[zeef]

Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi,

Hope dev can give you.

Thanks

[rodney2250]

Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi,

Hope dev can give you.

Thanks

I have asked the dev, but have not gotten any reply so far. If you can provide it then I can add it tomorrow.

[iLLNiSS]

Unrelated to the GPIO, I seem to be having issues getting 2.0 working.

When I view the claymore dashboard, it lists the rig_ids fine and shows how many gpus/etc are installed, but it's not populating any data to the dashboard. The rig-monitor app is running, and it does seem to be communcating with the miner:

Code:

INFO: 2018/05/12 18:08:19 rig-monitor.go:40: New rig monitor job received: miner01,claymore,nanopool,,http://192.168.10.81:3333,6,180,,noplug,,900,70
INFO: 2018/05/12 18:08:19 env.go:46: New environment monitor job received: miner01,claymore,nanopool,,http://192.168.10.81:3333,6,180,,noplug,,900,70

But I see no info on the dashboard.

Can you run a trace and send it back to me?
>grm -p -1 -m -1 -r <index of rig in config file> -t

FYI:
-p -1 disables the pool monitoring
-m -1 disables market data monitoring
-r <index> runs grm only for the specific rig. Index start at 1 not 0  

EDIT: I'm an idiot. I'm using PhoenixMiner and not Claymore. I assumed compatibility because they both use the same settings/remote monitoring software. I completely ignored that this thing is parsing the output of the console which is most certainly different between the two.

Ran a quick trace. It doesn't seem to be parsing the info correctly. https://pastebin.com/Yp3Ff2be

When running normally, it is also entering this empty data into the db:

Code:

> select * from miner_gpu where miner='CLAYMORE' order by time asc
name: miner_gpu
time                fan gpu_id hr hr2 invalid_shares invalid_shares2 max_temp miner    rig_id  temp valid_shares valid_shares2
----                --- ------ -- --- -------------- --------------- -------- -----    ------  ---- ------------ -------------
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   7      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   6      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169451000000000 0   0      0  0   0              0               70       CLAYMORE desktop 0    0            0
1526169451000000000 0   1      0  0   0              0               70       CLAYMORE desktop 0    0            0

No worries. I can add support for it in the coming version.
Could you upload to the monitoring output to the Github feature I have create here:https://github.com/rodneymo/rig-monitorv2/issues/8
If the output is an html the please upload the html file not just the text output.

Done.

[rodney2250]

Ok. Please post a trace so I can look at the json and check how it’s being processed

Here ya go:

Thanks. Issue has been fixed on release 2.0.b.2. You can download it from GitHub

Thanks a lot man, now all the threads are showing up.
Let me know when you find a way to fix the supportxmr.com pool support.
I suppose one of the ways to do it could be just parsing the pool name and processing the json one way if its supportxmr or standard way if its not.

I'm trying to keep the binary file small. So I want to avoid duplication. I should have a solution by tomorrow.

Please check 2.1_development_2 release on GitHub: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.2

If you still face errors then please provide me with a trace:
>grm -r -1 -m -1 -p <pool index in config file 1..n>

[syncro2017]

Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

Sure. I have created a new feature request on GitHub. Could you upload some json examples for both the "/" and "/workers.json" endpoints?

Thanks a lot man
I will post it tonight

[rodney2250]

Got it. Thanks

[rodney2250]

Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

Sure. I have created a new feature request on GitHub. Could you upload some json examples for both the "/" and "/workers.json" endpoints?

Thanks a lot man
I will post it tonight

Check development version 4 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.4). It includes support for XMRIG-PROXY and a dashboard template. Let me know if you have some issues.

[syncro2017]

Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

Sure. I have created a new feature request on GitHub. Could you upload some json examples for both the "/" and "/workers.json" endpoints?

Thanks a lot man
I will post it tonight

Check development version 4 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.4). It includes support for XMRIG-PROXY and a dashboard template. Let me know if you have some issues.

Thanks for the update man,
I just tried it and got the following errors with xmrig-proxy:

No Trace:

Code:

devel@devel-vm:[~/WORK/RigMon2.1]: ./grm-2.0.d4
INFO: 2018/05/14 14:21:58 main.go:33: Starting rig-monitor...
INFO: 2018/05/14 14:21:58 main.go:50: Commmand line arguments: -config
INFO: 2018/05/14 14:21:58 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/14 14:21:58 config.go:92: Reading configuration file...
INFO: 2018/05/14 14:21:58 main.go:70: Commmand line arguments: -p 0
INFO: 2018/05/14 14:21:58 main.go:82: Commmand line arguments: -r 0
INFO: 2018/05/14 14:21:58 main.go:105: Commmand line arguments: -m 0
INFO: 2018/05/14 14:21:58 main.go:122: Connection to influxDB at http://localhost:8086 ...
INFO: 2018/05/14 14:21:58 influxdb.go:18: Starting DBDaemon routine...
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:163: Launching market monitor worker: 0
INFO: 2018/05/14 14:21:59 pool-monitor.go:59: New pool monitor job received: label_supportXMR
INFO: 2018/05/14 14:21:59 nodejs-pool.go:62: Querying NODEJS-POOL minerStats.
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
INFO: 2018/05/14 14:21:59 market-monitor.go:58: New market monitor job received: XMR
INFO: 2018/05/14 14:21:59 rig-monitor.go:72:  Connection to rig MineRig2 OK.
INFO: 2018/05/14 14:21:59 rig-monitor.go:72:  Connection to rig proxy OK.
ERROR: 2018/05/14 14:21:59 xmrig-proxy.go:86: Could not decode response from proxy. Failed with json: cannot unmarshal number 0.0 into Go struct field XmrigProxyJson.donated of type int
INFO: 2018/05/14 14:22:00 market-monitor.go:174: Connection to https://api.coinmarketcap.com/v1/ticker?limit=0 OK.
INFO: 2018/05/14 14:22:00 rig-monitor.go:72:  Connection to rig MineRig1 OK.
INFO: 2018/05/14 14:22:00 market-monitor.go:174: Connection to https://whattomine.com/coins.json OK.
INFO: 2018/05/14 14:22:02 nodejs-pool.go:69: minerStats query succeeded!
INFO: 2018/05/14 14:22:02 nodejs-pool.go:74: Querying NODEJS-POOL workerIdentifiers.
INFO: 2018/05/14 14:22:02 nodejs-pool.go:81: workerIdentifiers query succeeded!
INFO: 2018/05/14 14:22:02 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(MineRig2).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(MineRig2) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(proxy).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(proxy) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(MineRig1).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(MineRig1) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:100: Querying NODEJS-POOL paymentStats.
INFO: 2018/05/14 14:22:03 nodejs-pool.go:107: paymentStats query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:112: Querying NODEJS-POOL networkStats.
INFO: 2018/05/14 14:22:03 nodejs-pool.go:119: networkStats query succeeded!
ERROR: 2018/05/14 14:22:03 functions.go:92: Could not parse 4783 string into float64. Exiting...

With Trace

Code:

devel@devel-vm:[~/WORK/RigMon2.1]: ./grm-2.0.d4 -p -1 -m -1 -r 3 -t
INFO: 2018/05/14 14:22:55 main.go:33: Starting rig-monitor...
INFO: 2018/05/14 14:22:55 main.go:46: Tracing is enabled!
INFO: 2018/05/14 14:22:55 main.go:50: Commmand line arguments: -config
INFO: 2018/05/14 14:22:55 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/14 14:22:55 config.go:92: Reading configuration file...
TRACE: 2018/05/14 14:22:55 config.go:109: Config file: &lib.Config{Grafana:lib.Grafana{Username:"grafana", Password:"grafana"}, Influxdb:lib.InfluxDb{Hostname:"http://localhost:8086", Database:"rigdata", Username:"grafana", Password:"grafana", WriteInterval:0xf, InfluxWriteBufferSize:0x64}, Dynu:lib.Dynu{Enabled:false, Username:"dynu", Password:"dynu", Hostname:"host.dynu.com", UpdateInterval:1800}, Profitability:lib.Profitability{QuoteCurrency:"USD", PowerCostKwh:0.15, PowerRatioDualMining:0.3, EnvPollingInterval:60, MarketPollingInterval:300}, Main:lib.Main{PoolWorkers:3, RigWorkers:3, PoolPollingInterval:600, RigPollingInterval:60, PoolConfig:[]string{"label_supportXMR,nodejs-pool,XMR,https://supportxmr.com,,45UCHuYkQfriTrWoCC2vhFYBSUHtrTsm4DJduNye42ssJagZPjG2tiFBmdgpvehAhSTCqBo2AfiS5Ukx8R1CVv1A2WiEoHk"}, RigConfig:[]string{"MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75", "MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75", "proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75"}}, PowerManagement:lib.PowerManagement{Enabled:false, Rules:[]string(nil)}}
INFO: 2018/05/14 14:22:55 main.go:70: Commmand line arguments: -p -1
INFO: 2018/05/14 14:22:55 main.go:82: Commmand line arguments: -r 3
INFO: 2018/05/14 14:22:55 main.go:105: Commmand line arguments: -m -1
TRACE: 2018/05/14 14:22:55 main.go:117: List of rigs: []string{"proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75"}
TRACE: 2018/05/14 14:22:55 main.go:118: List of pools: []string{}
INFO: 2018/05/14 14:22:55 main.go:122: Connection to influxDB at http://localhost:8086 ...
INFO: 2018/05/14 14:22:55 influxdb.go:18: Starting DBDaemon routine...
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:163: Launching market monitor worker: 0
INFO: 2018/05/14 14:22:56 rig-monitor.go:40: New rig monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
TRACE: 2018/05/14 14:22:56 rig-monitor.go:42: New rig monitor job received: &lib.RigConfig{RigName:"proxy", Miner:"XMRIG-PROXY", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"http://159.65.227.6:8088", InstalledGpus:19, TargetHashRate:16000, TargetHashRate2:0, SmartPlugType:"noplug", SmartPlugIP:"", PSUMaxPower:0, TargetTemperature:75}
INFO: 2018/05/14 14:22:56 env.go:43: New environment monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
TRACE: 2018/05/14 14:22:56 env.go:45: New environment monitor job received: &lib.RigConfig{RigName:"proxy", Miner:"", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"", InstalledGpus:0, TargetHashRate:0, TargetHashRate2:0, SmartPlugType:"NOPLUG", SmartPlugIP:"", PSUMaxPower:1200, TargetTemperature:0}
TRACE: 2018/05/14 14:22:56 influxdb.go:51: New record received by DBDaemon: env_data map[label:label_supportXMR plug_type:NOPLUG rig_id:proxy] map[max_power:1200 power_usage:1200] <nil> 2018-05-14 14:22:56.369355489 +0000 UTC m=+1.004418443
INFO: 2018/05/14 14:22:56 rig-monitor.go:72:  Connection to rig proxy OK.
ERROR: 2018/05/14 14:22:56 xmrig-proxy.go:86: Could not decode response from proxy. Failed with json: cannot unmarshal number 0.0 into Go struct field XmrigProxyJson.donated of type int

INFO: 2018/05/14 14:23:10 influxdb.go:45: DBDaemon ticker expired (15s). Data points (1) saved to influxDB
INFO: 2018/05/14 14:23:25 influxdb.go:45: DBDaemon ticker expired (15s). Data points (0) saved to influxDB
INFO: 2018/05/14 14:23:40 influxdb.go:45: DBDaemon ticker expired (15s). Data points (0) saved to influxDB

[rodney2250]

Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

Sure. I have created a new feature request on GitHub. Could you upload some json examples for both the "/" and "/workers.json" endpoints?

Thanks a lot man
I will post it tonight

Check development version 4 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.4). It includes support for XMRIG-PROXY and a dashboard template. Let me know if you have some issues.

Thanks for the update man,
I just tried it and got the following errors with xmrig-proxy:

It seems like a data type conflict, but I cannot troubleshoot it without the full trace. If you don't want to post it here then send it to me via telegram @rodneymo

[syncro2017]

Just wanted to say a huge thanks to the Author for fixing all the issues related to SupportXMR pool, SRB Miner and xmrig-proxy in the monitor software!
He spend more than 2 hours with me today and my monitor now works awesome.
I have 19 workers on xmrig-proxy + 2 mining rigs one with SRB miner and another one with xmr-stak.
Huge thanks to the developer for such dedication and fast response!
Cheers

[rodney2250]

Unrelated to the GPIO, I seem to be having issues getting 2.0 working.

When I view the claymore dashboard, it lists the rig_ids fine and shows how many gpus/etc are installed, but it's not populating any data to the dashboard. The rig-monitor app is running, and it does seem to be communcating with the miner:

Code:

INFO: 2018/05/12 18:08:19 rig-monitor.go:40: New rig monitor job received: miner01,claymore,nanopool,,http://192.168.10.81:3333,6,180,,noplug,,900,70
INFO: 2018/05/12 18:08:19 env.go:46: New environment monitor job received: miner01,claymore,nanopool,,http://192.168.10.81:3333,6,180,,noplug,,900,70

But I see no info on the dashboard.

Can you run a trace and send it back to me?
>grm -p -1 -m -1 -r <index of rig in config file> -t

FYI:
-p -1 disables the pool monitoring
-m -1 disables market data monitoring
-r <index> runs grm only for the specific rig. Index start at 1 not 0  

EDIT: I'm an idiot. I'm using PhoenixMiner and not Claymore. I assumed compatibility because they both use the same settings/remote monitoring software. I completely ignored that this thing is parsing the output of the console which is most certainly different between the two.

Ran a quick trace. It doesn't seem to be parsing the info correctly. https://pastebin.com/Yp3Ff2be

When running normally, it is also entering this empty data into the db:

Code:

> select * from miner_gpu where miner='CLAYMORE' order by time asc
name: miner_gpu
time                fan gpu_id hr hr2 invalid_shares invalid_shares2 max_temp miner    rig_id  temp valid_shares valid_shares2
----                --- ------ -- --- -------------- --------------- -------- -----    ------  ---- ------------ -------------
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   7      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   5      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   6      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   2      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   0      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   1      0  0   0              0               70       CLAYMORE miner02 0    0            0
1526169450000000000 0   3      0  0   0              0               70       CLAYMORE miner03 0    0            0
1526169450000000000 0   4      0  0   0              0               70       CLAYMORE miner01 0    0            0
1526169451000000000 0   0      0  0   0              0               70       CLAYMORE desktop 0    0            0
1526169451000000000 0   1      0  0   0              0               70       CLAYMORE desktop 0    0            0

No worries. I can add support for it in the coming version.
Could you upload to the monitoring output to the Github feature I have create here:https://github.com/rodneymo/rig-monitorv2/issues/8
If the output is an html the please upload the html file not just the text output.

Done.

I need a few more days. Unlike claymore the output from PhoenixMiner is not consistent e.g. most of the last paragraph does not include all the info. So I have to modified the regexs and logic.

[heavyarms1912]

Specific reason this is not open source?
any plans on making it open source?

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.

[Germini]

Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi! , thanks for your work, pretty awesome dashboard i'm running it using windows 10 in a miner without any problems

When castxmr v1.0.0 is executed using --remoteaccess you go to the miner http://127.0.0.1:7777 and you get this, no file extension:

Code:

{
	"total_hash_rate": 7381347,
	"total_hash_rate_avg": 7268710,
	"pool": {
		"server": "xmr-us-east1.nanopool.org:14444",
		"status": "connected",
		"online": 16,
		"offline": 0,
		"reconnects": 0,
		"time_connected": "2018-05-14 18:37:31",
		"time_disconnected": "2018-05-14 18:37:31"
	},
	"job": {
		"job_number": 1,
		"difficulty": 120001,
		"running": 15,
		"job_time_avg": 0.00
	},
	"shares": {
		"num_accepted": 0,
		"num_rejected": 0,
		"num_invalid": 0,
		"num_network_fail": 0,
		"num_outdated": 0,
		"search_time_avg": 0.00
	},
	"devices": [
	{
		"device": "GPU0",
		"device_id": 0,
		"hash_rate": 1844253,
		"hash_rate_avg": 1828105,
		"gpu_temperature": 39,
		"gpu_fan_rpm": 3657
	},
	{
		"device": "GPU1",
		"device_id": 1,
		"hash_rate": 1845520,
		"hash_rate_avg": 1764523,
		"gpu_temperature": 41,
		"gpu_fan_rpm": 3668
	},
	{
		"device": "GPU2",
		"device_id": 2,
		"hash_rate": 1962401,
		"hash_rate_avg": 1898305,
		"gpu_temperature": 45,
		"gpu_fan_rpm": 3749
	},
	{
		"device": "GPU3",
		"device_id": 3,
		"hash_rate": 1729173,
		"hash_rate_avg": 1777777,
		"gpu_temperature": 45,
		"gpu_fan_rpm": 3634
	}
	]
}

I will provide you with an URL so you can test it in a message

edit1: well, i can't send you messages because I am considered a newbie

[iLLNiSS]

I need a few more days. Unlike claymore the output from PhoenixMiner is not consistent e.g. most of the last paragraph does not include all the info. So I have to modified the regexs and logic.

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:

Code:

echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1","psw":"remote_monitor_password"}' | netcat MINERIP MINERPORT

If no password is used in the remote miner, you can remove the password and leave the psw in:

Code:

echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1","psw":""}' | netcat MINERIP MINERPORT

And the result from PhoenixMiner is:

Code:

{"id":0,"jsonrpc":"2.0","result":["PM 2.9e - ETH", "210", "61831;75;0", "31883;29948", "0;0;0", "off;off", "65;0;60;39", "eth-us-east1.nanopool.org:9999", "0;0;0;0"]}

A legend of what the data is:

Code:

"PM 2.9e - ETH" miner version.
""210" running time, in minutes.
"61831;75;0" total ETH hashrate in H/s, number of ETH shares, number of ETH rejected shares.
"31883;29948" detailed ETH hashrate for all GPUs. (there are 2 on this output)
"0;0;0" total DCR hashrate in H/s, number of DCR shares, number of DCR rejected shares.
"off;off" detailed DCR hashrate for all GPUs. 
"65;0;60;39" Temperature and Fan speed(%) pairs for all GPUs.
"eth-us-east1.nanopool.org:9999" current mining pool. For dual mode, there will be two pools here.
"0;0;0;0" number of ETH invalid shares, number of ETH pool switches, number of DCR invalid shares, number of DCR pool switches.

[rodney2250]

Specific reason this is not open source?
any plans on making it open source?

That was probably the thing I thought the most about when I decided to re-write it golang. This is not set in stone and I'll re-evaluate the decision as time goes by.
My experience with rig-monitor 1.x, which is scripted and inherently open source was not really good. Got a bunch of ppl forking it, but only
one guy sporadically contributing. But, like I said I might re-evaluate the decision later on.

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.

right, but that requires an "agent" to be installed on every rig. Right now I am looking at developing all 3 options below:
1) monitor hr and power usage KPIs and reset smart plug in case of failure (currently under development; will support both TPLINK and Wemo plugs)
2) use GPIO to trigger external relays (raspberry PI only)
3) develop "agent" that can be signaled to force rig reboot via syscall

[rodney2250]

Hi! , thanks for your work, pretty awesome dashboard i'm running it using windows 10 in a miner without any problems

When castxmr v1.0.0 is executed using --remoteaccess you go to the miner http://127.0.0.1:7777 and you get this, no file extension:


I will provide you with an URL so you can test it in a message

edit1: well, i can't send you messages because I am considered a newbie

Thank you. I really appreciate it. I'll get on it as soon as I finish support for PhoenixMiner. I'll send you a message, maybe you can reply to it.

[rodney2250]

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:

Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

[iLLNiSS]

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:

Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

I’m not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.

[heavyarms1912]

Specific reason this is not open source?
any plans on making it open source?

That was probably the thing I thought the most about when I decided to re-write it golang. This is not set in stone and I'll re-evaluate the decision as time goes by.
My experience with rig-monitor 1.x, which is scripted and inherently open source was not really good. Got a bunch of ppl forking it, but only
one guy sporadically contributing. But, like I said I might re-evaluate the decision later on.

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.

right, but that requires an "agent" to be installed on every rig. Right now I am looking at developing all 3 options below:
1) monitor hr and power usage KPIs and reset smart plug in case of failure (currently under development; will support both TPLINK and Wemo plugs)
2) use GPIO to trigger external relays (raspberry PI only)
3) develop "agent" that can be signaled to force rig reboot via syscall

i didn't get what you meant by an agent being installed.  
I am using TP-Link HS110 and monitoring power using a bash script and power-cycle whenever it falls below the threshold value using curl http GET/POST requests, remotely (doesn't even have to be on same network).
Pretty sure the same thing can be done with a WeMo.  Or with IFFT.