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.
Topic: [NEW] free rig-monitor 4.0 (alpha released) - page 9. (Read 14736 times)
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
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
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
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
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
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...
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] 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
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]
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
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
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.
Got it. Thanks
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
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
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
Any ideia to develop it in cast xmrstack?
Thanks
Thanks
Are you referring to this one? https://bitcointalksearch.org/topic/m.37051627
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.
Any ideia to develop it in cast xmrstack?
Thanks
Thanks
Are you referring to this one? https://bitcointalksearch.org/topic/m.37051627
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
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.
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
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?
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
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
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.
thanks bro but for me its useless i dont mine anymore i dont knwo how the hell they buy gpu for 500 $ to earn 1 $ perday (if its work 24h non stop )
that's 1.5 year ROI, still better than most businesses ;-)
thanks bro but for me its useless i dont mine anymore i dont knwo how the hell they buy gpu for 500 $ to earn 1 $ perday (if its work 24h non stop )
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
Jump to: