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

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: zeef on May 12, 2018, 09:26:51 PM

Any ideia to develop it in cast xmrstack?

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

zeef

newbie

Activity: 296

Merit: 0

Any ideia to develop it in cast xmrstack?

Thanks

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 12, 2018, 02:41:37 PM

Quote from: iLLNiSS on May 12, 2018, 02:14:48 PM

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

FYI:
-p -1 disables the pool monitoring
-m -1 disables market data monitoring
-r 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

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 12, 2018, 05:37:24 PM

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

Here ya go:

Code:

devel@devel-vm:[~/WORK/RigMonitor]: ./grm-2.0.b1 -p -1 -m -1 -r 1 -t
INFO: 2018/05/12 21:41:11 main.go:33: Starting rig-monitor...
INFO: 2018/05/12 21:41:11 main.go:46: Tracing is enabled!
INFO: 2018/05/12 21:41:11 main.go:50: Commmand line arguments: -config
INFO: 2018/05/12 21:41:11 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/12 21:41:11 config.go:86: Reading configuration file...
TRACE: 2018/05/12 21:41:11 config.go:103: 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,xmr-stak,label_supportXMR,,http://192.168.232.31:16000,10,4250,,,,650,75"}}}
INFO: 2018/05/12 21:41:11 main.go:70: Commmand line arguments: -p -1
INFO: 2018/05/12 21:41:11 main.go:82: Commmand line arguments: -r 1
INFO: 2018/05/12 21:41:11 main.go:105: Commmand line arguments: -m -1
TRACE: 2018/05/12 21:41:11 main.go:117: List of rigs: []string{"MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75"}
TRACE: 2018/05/12 21:41:11 main.go:118: List of pools: []string{}
INFO: 2018/05/12 21:41:11 main.go:122: Connection to influxDB at http://localhost:8086 ...
INFO: 2018/05/12 21:41:11 influxdb.go:18: Starting DBDaemon routine...
INFO: 2018/05/12 21:41:12 main.go:146: Launching pool monitor worker: 0
INFO: 2018/05/12 21:41:12 main.go:146: Launching pool monitor worker: 1
INFO: 2018/05/12 21:41:12 main.go:146: Launching pool monitor worker: 2
INFO: 2018/05/12 21:41:12 main.go:152: Launching rig monitor worker: 0
INFO: 2018/05/12 21:41:12 main.go:152: Launching rig monitor worker: 1
INFO: 2018/05/12 21:41:12 main.go:152: Launching rig monitor worker: 2
INFO: 2018/05/12 21:41:12 main.go:158: Launching power monitor worker: 0
INFO: 2018/05/12 21:41:12 main.go:158: Launching power monitor worker: 1
INFO: 2018/05/12 21:41:12 main.go:158: Launching power monitor worker: 2
INFO: 2018/05/12 21:41:12 main.go:163: Launching market monitor worker: 0
INFO: 2018/05/12 21:41:12 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/12 21:41:12 env.go:46: New environment monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
TRACE: 2018/05/12 21:41:12 env.go:48: New environment monitor job received: &lib.RigConfig{RigName:"MineRig1", Miner:"", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"", InstalledGpus:0, TargetHashRate:0, TargetHashRate2:0, SmartPlugType:"", SmartPlugIP:"", PSUMaxPower:650, TargetTemperature:0}
TRACE: 2018/05/12 21:41:12 rig-monitor.go:42: New rig monitor job received: &lib.RigConfig{RigName:"MineRig1", Miner:"XMR-STAK", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"http://192.168.232.30:16000", InstalledGpus:16, TargetHashRate:4850, TargetHashRate2:0, SmartPlugType:"", SmartPlugIP:"", PSUMaxPower:0, TargetTemperature:75}
INFO: 2018/05/12 21:41:12 rig-monitor.go:68: Connection to rig MineRig1 OK.
TRACE: 2018/05/12 21:41:12 xmr-stak.go:64: Miner(xmr-stak) response from MineRig1: {
"version": "xmr-stak/2.4.3/26a5d65f/unknown/win/amd-cpu/aeon-cryptonight-monero/0",
"hashrate": {
"threads": [
[
229.1,
229.1,
229.1
],
[
229,
229.1,
229.1
],
[
452.7,
452.7,
452.7
],
[
444.9,
444.7,
444.7
],
[
469.4,
469.4,
469.4
],
[
461.2,
461.1,
461.2
],
[
463.2,
463.5,
463.6
],
[
455.7,
455.5,
455.4
],
[
454.9,
454.8,
454.8
],
[
447,
446.9,
446.8
],
[
238.9,
238.8,
238.8
],
[
238.8,
238.8,
238.8
],
[
70.4,
70.4,
70.4
],
[
72.4,
72.5,
72.3
],
[
72.2,
72.4,
72.3
],
[
71,
71,
71
]
],
"total": [
4870.8,
4870.6,
4870.4
],
"highest": 4873.7
},
"results": {
"diff_current": 141272,
"shares_good": 3137,
"shares_total": 3172,
"avg_time": 29.4,
"hashes_total": 167559063,
"best": [
727401336,
697808744,
216834535,
154470710,
135829103,
110481742,
70728425,
52480418,
49959351,
49316225
],
"error_log": [
{
"count": 1,
"last_seen": 1526069933,
"text": "[NETWORK ERROR]"
},
{
"count": 34,
"last_seen": 1526161221,
"text": "AMD Invalid Result GPU ID 1"
}
]
},
"connection": {
"pool": "pool.supportxmr.com:9000",
"uptime": 35564,
"ping": 114,
"error_log": [
{
"last_seen": 1526161255,
"text": "[pool.supportxmr.com:9000] RECEIVE error: socket closed"
}
]
}
}
TRACE: 2018/05/12 21:41:12 influxdb.go:51: New record received by DBDaemon: miner_system map[label:label_supportXMR miner:XMR-STAK rig_id:MineRig1] map[avg_result_time:29.4 current_difficulty:141272 invalid_shares:35 target_hr:4850 total_shares:3172 valid_shares:3137 avg_hr_10s:4870.8 avg_hr_60s:4870.6 configured_threads:16 error_count:2 total_hashes:167559063 active_threads:3 avg_hr_15m:4870.4] 2018-05-12 21:41:12.097998908 +0000 UTC m=+1.047779093
TRACE: 2018/05/12 21:41:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[gpu_id:0 miner:XMR-STAK rig_id:MineRig1] map[avg_hr_10s:229.1 avg_hr_15m:229.1 avg_hr_60s:229.1] 2018-05-12 21:41:12.098035279 +0000 UTC m=+1.047815449
TRACE: 2018/05/12 21:41:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[gpu_id:1 miner:XMR-STAK rig_id:MineRig1] map[avg_hr_10s:229 avg_hr_15m:229.1 avg_hr_60s:229.1] 2018-05-12 21:41:12.098041814 +0000 UTC m=+1.047821981
TRACE: 2018/05/12 21:41:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[gpu_id:2 miner:XMR-STAK rig_id:MineRig1] map[avg_hr_10s:452.7 avg_hr_15m:452.7 avg_hr_60s:452.7] 2018-05-12 21:41:12.098045882 +0000 UTC m=+1.047826056
INFO: 2018/05/12 21:41:26 influxdb.go:45: DBDaemon ticker expired (15s). Data points (4) saved to influxDB
INFO: 2018/05/12 21:41:41 influxdb.go:45: DBDaemon ticker expired (15s). Data points (0) saved to influxDB
INFO: 2018/05/12 21:41:56 influxdb.go:45: DBDaemon ticker expired (15s). Data points (0) saved to influxDB
INFO: 2018/05/12 21:42:11 influxdb.go:45: DBDaemon ticker expired (15s). Data points (0) saved to influxDB
INFO: 2018/05/12 21:42:12 env.go:46: New environment monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
TRACE: 2018/05/12 21:42:12 env.go:48: New environment monitor job received: &lib.RigConfig{RigName:"MineRig1", Miner:"", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"", InstalledGpus:0, TargetHashRate:0, TargetHashRate2:0, SmartPlugType:"", SmartPlugIP:"", PSUMaxPower:650, TargetTemperature:0}
INFO: 2018/05/12 21:42:12 rig-monitor.go:40: New rig monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
TRACE: 2018/05/12 21:42:12 rig-monitor.go:42: New rig monitor job received: &lib.RigConfig{RigName:"MineRig1", Miner:"XMR-STAK", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"http://192.168.232.30:16000", InstalledGpus:16, TargetHashRate:4850, TargetHashRate2:0, SmartPlugType:"", SmartPlugIP:"", PSUMaxPower:0, TargetTemperature:75}
INFO: 2018/05/12 21:42:12 rig-monitor.go:68: Connection to rig MineRig1 OK.
TRACE: 2018/05/12 21:42:12 xmr-stak.go:64: Miner(xmr-stak) response from MineRig1: {
"version": "xmr-stak/2.4.3/26a5d65f/unknown/win/amd-cpu/aeon-cryptonight-monero/0",
"hashrate": {
"threads": [
[
229,
229,
229.1
],
[
229,
229.1,
229.1
],
[
452.7,
452.7,
452.7
],
[
444.7,
444.7,
444.7
],
[
469.7,
469.4,
469.4
],
[
460.8,
461.1,
461.2
],
[
463.5,
463.6,
463.6
],
[
455.4,
455.4,
455.4
],
[
454.8,
454.8,
454.8
],
[
446.9,
446.9,
446.8
],
[
238.8,
238.8,
238.8
],
[
238.8,
238.8,
238.8
],
[
70.5,
70.7,
70.4
],
[
72.2,
72.4,
72.3
],
[
72.1,
72.6,
72.3
],
[
71,
71.3,
71
]
],
"total": [
4869.9,
4871.4,
4870.4
],
"highest": 4873.7
},
"results": {
"diff_current": 141272,
"shares_good": 3137,
"shares_total": 3172,
"avg_time": 29.5,
"hashes_total": 167559063,
"best": [
727401336,
697808744,
216834535,
154470710,
135829103,
110481742,
70728425,
52480418,
49959351,
49316225
],
"error_log": [
{
"count": 1,
"last_seen": 1526069933,
"text": "[NETWORK ERROR]"
},
{
"count": 34,
"last_seen": 1526161221,
"text": "AMD Invalid Result GPU ID 1"
}
]
},
"connection": {
"pool": "pool.supportxmr.com:9000",
"uptime": 35624,
"ping": 114,
"error_log": [
{
"last_seen": 1526161255,
"text": "[pool.supportxmr.com:9000] RECEIVE error: socket closed"
}
]
}
}
TRACE: 2018/05/12 21:42:12 influxdb.go:51: New record received by DBDaemon: miner_system map[label:label_supportXMR miner:XMR-STAK rig_id:MineRig1] map[error_count:2 target_hr:4850 total_hashes:167559063 active_threads:3 avg_hr_10s:4869.9 avg_hr_60s:4871.4 current_difficulty:141272 invalid_shares:35 total_shares:3172 valid_shares:3137 avg_hr_15m:4870.4 avg_result_time:29.5 configured_threads:16] 2018-05-12 21:42:12.06029473 +0000 UTC m=+61.010074910
TRACE: 2018/05/12 21:42:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[gpu_id:0 miner:XMR-STAK rig_id:MineRig1] map[avg_hr_10s:229 avg_hr_15m:229.1 avg_hr_60s:229] 2018-05-12 21:42:12.060343136 +0000 UTC m=+61.010123316
TRACE: 2018/05/12 21:42:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[gpu_id:1 miner:XMR-STAK rig_id:MineRig1] map[avg_hr_15m:229.1 avg_hr_60s:229.1 avg_hr_10s:229] 2018-05-12 21:42:12.060349697 +0000 UTC m=+61.010129884
TRACE: 2018/05/12 21:42:12 influxdb.go:51: New record received by DBDaemon: miner_gpu map[miner:XMR-STAK rig_id:MineRig1 gpu_id:2] map[avg_hr_10s:452.7 avg_hr_15m:452.7 avg_hr_60s:452.7] 2018-05-12 21:42:12.06036155 +0000 UTC m=+61.010141736
^C
devel@devel-vm:[~/WORK/RigMonitor]:

rodney2250

jr. member

Activity: 177

Merit: 2

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

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 12, 2018, 04:30:10 PM

Quote from: syncro2017 on May 12, 2018, 12:28:03 PM

Quote from: rodney2250 on May 12, 2018, 02:07:58 AM

config looks ok. You might want to disable dynu DNS if you are not using it

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Also, forgot to add,
For some reason the number of GPUs online is being shown as 6, as well as hashrate per thread, there should be 26 threads in total, 16 from one rig and 10 from another but only 6 are being shown

which version of rig-monitor are you using, 2.0.b1 or 2.0.a.x?
Can you send me one of your rigs' json so I can run it through my rig-monitor test environment?

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Another issues i noticed is when you import the dashboad.csv through sqlite3, it gives error "Wrong datatype". I had this issue both on linux and windows

Found and fixed the issue in the current development branch. The sqlite headers were included in the export, thus the datatype error. That error doesn't block the rest of the import so you should be OK.

I'm using version 2.0.b1 right now, as i thought its the latest

Here is the JSON from MineRig1, also Im using the latest xmr-stak 2.4.3

Code:

{"version":"xmr-stak/2.4.3/26a5d65f/unknown/win/amd-cpu/aeon-cryptonight-monero/0","hashrate":{"threads":[[229.0,229.2,229.1],[229.4,229.2,229.1],[452.8,452.7,452.7],[444.9,444.7,444.7],[469.7,469.4,469.4],[461.1,461.2,461.2],[463.4,463.6,463.6],[455.6,455.5,455.5],[455.1,454.9,454.8],[446.9,446.9,446.8],[238.9,238.8,238.8],[238.8,238.8,238.8],[68.5,70.3,70.4],[70.5,72.2,72.3],[70.2,72.2,72.3],[68.6,70.6,70.9]],"total":[4863.5,4870.3,4870.4],"highest":4873.7},"results":{"diff_current":134820,"shares_good":2464,"shares_total":2484,"avg_time":31.1,"hashes_total":74650083,"best":[697808744,154470710,135829103,70728425,52480418,49316225,45764116,44632776,42631037,40983093],"error_log":[{"count":1,"last_seen":1526069933,"text":"[NETWORK ERROR]"},{"count":19,"last_seen":1526138753,"text":"AMD Invalid Result GPU ID 1"}]},"connection":{"pool": "pool.supportxmr.com:9000","uptime":16652,"ping":111,"error_log":[{"last_seen":1526142266,"text":"[pool.supportxmr.com:9000] RECEIVE error: socket closed"}]}}

The 2.4.2. and 2.4.3 json format is exactly the same. Let's check a couple of things:

1) Check if data is being stored in influxDB. Run grm. Open another terminal an d login to influx client: #influx
>use rigdata
> select * from miner_system where miner='XMR-STAK' order by time asc
> select * from miner_gpu where miner='XMR-STAK' order by time asc

2) If data is not in influxDB then send me a trace:
>grm -p -1 -m -1 -r -t

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

Looks like the data is in the influx, however not for all threads, here are the logs:

miner_system table:

Code:

> select * from miner_system where miner='XMR-STAK' order by time asc
name: miner_system
time active_threads avg_hr_10s avg_hr_15m avg_hr_60s avg_result_time configured_threads current_difficulty error_count invalid_shares label miner rig_id target_hr total_hashes total_shares valid_shares
---- -------------- ---------- ---------- ---------- --------------- ------------------ ------------------ ----------- -------------- ----- ----- ------ --------- ------------ ------------ ------------
1526075368000000000 3 4868.2 4866.6 4867.4 26.3 16 142680 1 1 label_supportXMR XMR-STAK MineRig1 4850 25993555 208 207
1526075368000000000 3 4249.2 4253.3 4250.9 28.5 10 122492 0 0 label_supportXMR XMR-STAK MineRig2 4250 46791096 403 403
1526075424000000000 3 4863.6 4866.6 4866.7 26 16 143462 1 1 label_supportXMR XMR-STAK MineRig1 4850 26566621 212 211
1526075424000000000 3 4251.2 4253.4 4253 28.2 10 123121 0 0 label_supportXMR XMR-STAK MineRig2 4250 47404185 408 408
1526075484000000000 3 4867.5 4866.6 4866.9 26.1 16 145021 1 1 label_supportXMR XMR-STAK MineRig1 4850 26855104 214 213
1526075484000000000 3 4254.9 4253.5 4253.3 28 10 123752 0 0 label_supportXMR XMR-STAK MineRig2 4250 48021052 413 413
1526075544000000000 3 4872.2 4866.6 4868.6 26 16 145804 1 1 label_supportXMR XMR-STAK MineRig1 4850 27290950 217 216
1526075544000000000 3 4252.5 4253.5 4254 28.1 10 124053 0 0 label_supportXMR XMR-STAK MineRig2 4250 48144804 414 414
1526075604000000000 3 4870.8 4867 4870.7 26.3 16 145021 1 1 label_supportXMR XMR-STAK MineRig1 4850 27290950 217 216
1526075604000000000 3 4253 4253.4 4253.6 28.1 10 124053 0 0 label_supportXMR XMR-STAK MineRig2 4250 48392910 416 416
1526075664000000000 3 4871 4867.1 4867.4 26.1 16 146550 1 1 label_supportXMR XMR-STAK MineRig1 4850 27871034 221 220
1526075664000000000 3 4253.6 4253.3 4252.5 28 10 124712 0 0 label_supportXMR XMR-STAK MineRig2 4250 48889122 420 420
1526075724000000000 3 4869.4 4867.5 4870 25.9 16 146550 1 1
....
....
More similar rows
....

miner_gpu table:

Code:

> select * from miner_gpu where miner='XMR-STAK' order by time asc

name: miner_gpu
time avg_hr_10s avg_hr_15m avg_hr_60s gpu_id miner rig_id
---- ---------- ---------- ---------- ------ ----- ------
1526075368000000000 229.1 229.1 229.3 0 XMR-ST AK MineRig1
1526075368000000000 236.3 239.5 237.5 2 XMR-ST AK MineRig2
1526075368000000000 490.4 490.3 490.2 0 XMR-ST AK MineRig2
1526075368000000000 455.5 455.2 455.4 1 XMR-ST AK MineRig2
1526075368000000000 452.6 452.7 452.7 2 XMR-ST AK MineRig1
1526075368000000000 229.1 229.1 229.2 1 XMR-ST AK MineRig1
1526075424000000000 450.7 452.7 452.7 2 XMR-ST AK MineRig1
1526075424000000000 229.1 229.1 229 1 XMR-ST AK MineRig1
1526075424000000000 490.3 490.3 490.2 0 XMR-ST AK MineRig2
1526075424000000000 228.8 229.1 229.1 0 XMR-ST AK MineRig1
1526075424000000000 235.9 239.6 238.9 2 XMR-ST AK MineRig2
1526075424000000000 455.7 455.2 455.3 1 XMR-ST AK MineRig2
1526075484000000000 247.8 239.7 240 2 XMR-ST AK MineRig2
1526075484000000000 455.7 455.2 455.1 1 XMR-ST AK MineRig2
1526075484000000000 490 490.3 490.3 0 XMR-ST AK MineRig2
1526075484000000000 452.9 452.7 452.7 2 XMR-ST AK MineRig1
1526075484000000000 229.1 229.1 229.1 1 XMR-ST AK MineRig1
1526075484000000000 229.4 229.1 229.2 0 XMR-ST AK MineRig1
1526075544000000000 229.2 229.1 229.1 1 XMR-ST AK MineRig1
1526075544000000000 229.3 229.1 229.1 0 XMR-ST AK MineRig1
1526075544000000000 490.6 490.3 490.3 0 XMR-ST AK MineRig2
1526075544000000000 238.7 239.5 239.5 2 XMR-ST AK MineRig2
1526075544000000000 455.4 455.3 455.3 1 XMR-ST AK MineRig2
1526075544000000000 452.6 452.7 452.6 2 XMR-ST AK MineRig1
1526075604000000000 455.6 455.2 455.2 1 XMR-ST AK MineRig2
1526075604000000000 452.5 452.7 452.7 2 XMR-ST AK MineRig1
1526075604000000000 489.9 490.3 490.3 0 XMR-ST AK MineRig2
1526075604000000000 229.1 229.1 229.1 1 XMR-ST AK MineRig1
1526075604000000000 228.9 229.1 229 0 XMR-ST AK MineRig1
1526075604000000000 244.6 239.6 240.1 2 XMR-ST AK MineRig2
1526075664000000000 229 229.1 229.1 0 XMR-ST AK MineRig1
1526075664000000000 237 239.4 238.3 2 XMR-ST AK MineRig2
1526075664000000000 490.8 490.3 490.4 0 XMR-ST AK MineRig2
1526075664000000000 455.1 455.2 455.3 1 XMR-ST AK MineRig2
1526075664000000000 452.8 452.7 452.7 2 XMR-ST AK MineRig1
1526075664000000000 229 229.1 229.1 1 XMR-ST AK MineRig1
1526075724000000000 452.7 452.7 452.5 2 XMR-ST AK MineRig1
1526075724000000000 229 229.1 229.1 1 XMR-ST AK MineRig1
1526075724000000000 489.4 490.3 490.2 0 XMR-ST AK MineRig2
1526075724000000000 229.1 229.1 229.1 0 XMR-ST AK MineRig1
1526075724000000000 238.6 239.5 239.9 2 XMR-ST AK MineRig2
1526075724000000000 455.4 455.2 455.2 1 XMR-ST AK MineRig2
1526075784000000000 240.3 239.5 239.9 2 XMR-ST AK MineRig2
1526075784000000000 455.4 455.3 455.3 1 XMR-ST AK MineRig2
1526075784000000000 489.7 490.3 490.2 0 XMR-ST AK MineRig2
1526075784000000000 452.6 452.7 452.9 2 XMR-ST AK MineRig1
1526075784000000000 229 229.1 229.1 1 XMR-ST AK MineRig1
1526075784000000000 229.1 229.1 229 0 XMR-ST AK MineRig1
1526075844000000000 229.1 229.1 229.1 1 XMR-ST AK MineRig1
1526075844000000000 228.9 229.1 229.1 0 XMR-ST AK MineRig1
1526075844000000000 490.2 490.3 490.3 0 XMR-ST AK MineRig2
1526075844000000000 239.4 239.4 239.1 2 XMR-ST AK MineRig2
1526075844000000000 455.4 455.2 455.1 1 XMR-ST AK MineRig2
1526075844000000000 452.8 452.7 452.5 2 XMR-ST

notice the gpu_id being logged are only 0-2, but in the config i have 16 for one rig and 10 for another

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: syncro2017 on May 12, 2018, 12:11:19 PM

Quote from: rodney2250 on May 12, 2018, 02:02:00 AM

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

1. Im mining XMR on https://supportxmr.com and for some reason i get errors from the monitor saying JSON parsing failed when it tried to get stats for my miners, even though it did correctly identified them. Maybe the issue is that one of the miners on the pool is not xmr-stak

could you run the following API calls and send me the output? I don't use that pool and I am away from my test rig this week.
https://supportxmr.com/api/miner//stats
https://supportxmr.com/api/miner//identifiers
https://supportxmr.com/api/miner//stats/
https://supportxmr.com/api/miner//payments
https://supportxmr.com/api/network/stats

At least the network/stats API is working so there must be something funny going on

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

Added to the feature request list.

Hey man, thanks for a quick reply, Here is the info you asked for:

https://supportxmr.com/api/miner//stats

Code:

{"hash":25028,"identifier":"global","lastHash":1526141126,"totalHashes":28872699609,"validShares":956038,"invalidShares":100,"expiry":1526141158601,"amtPaid":2237540754924,"amtDue":169040694230,"txnCount":0}

https://supportxmr.com/api/miner//identifiers

Code:

["MineRig2","MineRig1","proxy"]

https://supportxmr.com/api/miner//stats/

Code:

{"lts":1526141258,"identifer":"MineRig2","hash":"5665","totalHash":"1515959755","validShares":17442,"invalidShares":null}

{"lts":1526141317,"identifer":"MineRig1","hash":"3645","totalHash":"3146252635","validShares":28285,"invalidShares":1}

{"lts":1526141373,"identifer":"proxy","hash":"15675","totalHash":"18884345146","validShares":679034,"invalidShares":82} - This one is not added to the monitor rigs, its on the VPS

https://supportxmr.com/api/miner//payments

Code:

[{"pt":"pplns","ts":1525351766,"amount":419975101283,"txnHash":"3a0ded8c578d43cd88954c3a63d820f3e7a12df05eb040e869d836a9e628f95b","mixin":6},{"pt":"pplns","ts":1525075256,"amount":307777442308,"txnHash":"0fc8a06be52f7c001a37461f22c9770de74887c00b2dcf796c9d22c6303bcaa5","mixin":6},{"pt":"pplns","ts":1524877698,"amount":305838960257,"txnHash":"fe5adb71693c5e207bb68790b1a75aebbb3e1c9c3da7d99d424f149e1bbb26b1","mixin":6},{"pt":"pplns","ts":1524677785,"amount":308320137180,"txnHash":"4465f4c50ca589f0668e4f8ac6aa6a9ae26c1224fcd91bfa307dc7df4e66f348","mixin":6},{"pt":"pplns","ts":1524471720,"amount":299518867949,"txnHash":"a92754baffb0cf73e7f4f53e9b45a478cbe080e8c9c06b74c213d795e3d9d9da","mixin":6},{"pt":"pplns","ts":1515029546,"amount":295072097298,"txnHash":"fc09c79022adc0fbce61dbae2fcc0398a20817b9ed794f595b7a9b918d054b60","mixin":4},{"pt":"pplns","ts":1514165344,"amount":301038148649,"txnHash":"b34fe8bb5919a2eaa4a936fd41603b1d158a76d01870fedc306b151aedf122e6","mixin":4}]

https://supportxmr.com/api/network/stats

Code:

{"difficulty":51629140831,"hash":"4906a8451ecc347d67dbf4b41d70307dc061870e34026084bdce83cd08ca7951","height":1571233,"value":4654142109567,"ts":1526141404,"expiry":1526141461169}

Thanks. It seems supportxmr.com is using a modified version of the API. They have added an "Expiry" field to both miner and network stats. I need a few days to come up with a solution that is compatible with both the standard cryptonote-pool-api and this modified version.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: syncro2017 on May 12, 2018, 12:28:03 PM

Quote from: rodney2250 on May 12, 2018, 02:07:58 AM

config looks ok. You might want to disable dynu DNS if you are not using it

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Also, forgot to add,
For some reason the number of GPUs online is being shown as 6, as well as hashrate per thread, there should be 26 threads in total, 16 from one rig and 10 from another but only 6 are being shown

which version of rig-monitor are you using, 2.0.b1 or 2.0.a.x?
Can you send me one of your rigs' json so I can run it through my rig-monitor test environment?

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Another issues i noticed is when you import the dashboad.csv through sqlite3, it gives error "Wrong datatype". I had this issue both on linux and windows

Found and fixed the issue in the current development branch. The sqlite headers were included in the export, thus the datatype error. That error doesn't block the rest of the import so you should be OK.

I'm using version 2.0.b1 right now, as i thought its the latest

Here is the JSON from MineRig1, also Im using the latest xmr-stak 2.4.3

Code:

{"version":"xmr-stak/2.4.3/26a5d65f/unknown/win/amd-cpu/aeon-cryptonight-monero/0","hashrate":{"threads":[[229.0,229.2,229.1],[229.4,229.2,229.1],[452.8,452.7,452.7],[444.9,444.7,444.7],[469.7,469.4,469.4],[461.1,461.2,461.2],[463.4,463.6,463.6],[455.6,455.5,455.5],[455.1,454.9,454.8],[446.9,446.9,446.8],[238.9,238.8,238.8],[238.8,238.8,238.8],[68.5,70.3,70.4],[70.5,72.2,72.3],[70.2,72.2,72.3],[68.6,70.6,70.9]],"total":[4863.5,4870.3,4870.4],"highest":4873.7},"results":{"diff_current":134820,"shares_good":2464,"shares_total":2484,"avg_time":31.1,"hashes_total":74650083,"best":[697808744,154470710,135829103,70728425,52480418,49316225,45764116,44632776,42631037,40983093],"error_log":[{"count":1,"last_seen":1526069933,"text":"[NETWORK ERROR]"},{"count":19,"last_seen":1526138753,"text":"AMD Invalid Result GPU ID 1"}]},"connection":{"pool": "pool.supportxmr.com:9000","uptime":16652,"ping":111,"error_log":[{"last_seen":1526142266,"text":"[pool.supportxmr.com:9000] RECEIVE error: socket closed"}]}}

The 2.4.2. and 2.4.3 json format is exactly the same. Let's check a couple of things:

1) Check if data is being stored in influxDB. Run grm. Open another terminal an d login to influx client: #influx
>use rigdata
> select * from miner_system where miner='XMR-STAK' order by time asc
> select * from miner_gpu where miner='XMR-STAK' order by time asc

2) If data is not in influxDB then send me a trace:
>grm -p -1 -m -1 -r -t

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

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 12, 2018, 02:46:31 PM

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

thanks

Check out the development version I just published. It includes support for SRBMiner. I only got an example file from the miner developer.
If you run into issues then please create an issue on GitHub and attach a Json from one of you miners.

I haven't had the time to create the dashboard yet, but you can check the field/tag names by logging into influxBD

#influx

>use rigdata
> select * from miner_system where miner='SRBMINER'
> select * from miner_gpu where miner='SRBMINER'

Thanks, I will give it a try, but I’m currently mining with xmr-stack 2.4.3 and have issues with statistics for number of threads in a rig, see my previous comment and example Json output from one of my rigs

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

thanks

Check out the development version I just published. It includes support for SRBMiner. I only got an example file from the miner developer.
If you run into issues then please create an issue on GitHub and attach a Json from one of you miners.

I haven't had the time to create the dashboard yet, but you can check the field/tag names by logging into influxBD

#influx

>use rigdata
> select * from miner_system where miner='SRBMINER'
> select * from miner_gpu where miner='SRBMINER'

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 12, 2018, 02:14:48 PM

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

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

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 12, 2018, 02:11:02 AM

Quote from: iLLNiSS on May 11, 2018, 08:58:01 PM

Perhaps some basic GPIO abilities on the RPI. You could use them to reset/power rigs without the need of a smart plug if end users tie into the power switch or reset line on their mobos.

Do you have a link where I can read about it? Those seem to be 2 slightly different use cases which I would need to implement:
1) switch PSU off-on on rig "failure"
GPIO voltage = 3.3v -> PSU on
GPIO voltage = 0v -> PSU off
GPIO voltage = 3.3v -> PSU on
2) reset PSU on rig "failure"
GPIO burst 0v->3.3v->0

I can't seem to locate much info, but it would need a level converter (theoretically) as the ATX pins are 5V. I just figured it'd be nice to have a watchdog running since some might be using a Pi already for this.

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.

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 12, 2018, 02:07:58 AM

config looks ok. You might want to disable dynu DNS if you are not using it

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Also, forgot to add,
For some reason the number of GPUs online is being shown as 6, as well as hashrate per thread, there should be 26 threads in total, 16 from one rig and 10 from another but only 6 are being shown

which version of rig-monitor are you using, 2.0.b1 or 2.0.a.x?
Can you send me one of your rigs' json so I can run it through my rig-monitor test environment?

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Another issues i noticed is when you import the dashboad.csv through sqlite3, it gives error "Wrong datatype". I had this issue both on linux and windows

Found and fixed the issue in the current development branch. The sqlite headers were included in the export, thus the datatype error. That error doesn't block the rest of the import so you should be OK.

I'm using version 2.0.b1 right now, as i thought its the latest

Here is the JSON from MineRig1, also Im using the latest xmr-stak 2.4.3

Code:

{"version":"xmr-stak/2.4.3/26a5d65f/unknown/win/amd-cpu/aeon-cryptonight-monero/0","hashrate":{"threads":[[229.0,229.2,229.1],[229.4,229.2,229.1],[452.8,452.7,452.7],[444.9,444.7,444.7],[469.7,469.4,469.4],[461.1,461.2,461.2],[463.4,463.6,463.6],[455.6,455.5,455.5],[455.1,454.9,454.8],[446.9,446.9,446.8],[238.9,238.8,238.8],[238.8,238.8,238.8],[68.5,70.3,70.4],[70.5,72.2,72.3],[70.2,72.2,72.3],[68.6,70.6,70.9]],"total":[4863.5,4870.3,4870.4],"highest":4873.7},"results":{"diff_current":134820,"shares_good":2464,"shares_total":2484,"avg_time":31.1,"hashes_total":74650083,"best":[697808744,154470710,135829103,70728425,52480418,49316225,45764116,44632776,42631037,40983093],"error_log":[{"count":1,"last_seen":1526069933,"text":"[NETWORK ERROR]"},{"count":19,"last_seen":1526138753,"text":"AMD Invalid Result GPU ID 1"}]},"connection":{"pool": "pool.supportxmr.com:9000","uptime":16652,"ping":111,"error_log":[{"last_seen":1526142266,"text":"[pool.supportxmr.com:9000] RECEIVE error: socket closed"}]}}

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 12, 2018, 02:02:00 AM

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

1. Im mining XMR on https://supportxmr.com and for some reason i get errors from the monitor saying JSON parsing failed when it tried to get stats for my miners, even though it did correctly identified them. Maybe the issue is that one of the miners on the pool is not xmr-stak

could you run the following API calls and send me the output? I don't use that pool and I am away from my test rig this week.
https://supportxmr.com/api/miner//stats
https://supportxmr.com/api/miner//identifiers
https://supportxmr.com/api/miner//stats/
https://supportxmr.com/api/miner//payments
https://supportxmr.com/api/network/stats

At least the network/stats API is working so there must be something funny going on

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

Added to the feature request list.

Hey man, thanks for a quick reply, Here is the info you asked for:

https://supportxmr.com/api/miner//stats

Code:

{"hash":25028,"identifier":"global","lastHash":1526141126,"totalHashes":28872699609,"validShares":956038,"invalidShares":100,"expiry":1526141158601,"amtPaid":2237540754924,"amtDue":169040694230,"txnCount":0}

https://supportxmr.com/api/miner//identifiers

Code:

["MineRig2","MineRig1","proxy"]

https://supportxmr.com/api/miner//stats/

Code:

{"lts":1526141258,"identifer":"MineRig2","hash":"5665","totalHash":"1515959755","validShares":17442,"invalidShares":null}

{"lts":1526141317,"identifer":"MineRig1","hash":"3645","totalHash":"3146252635","validShares":28285,"invalidShares":1}

{"lts":1526141373,"identifer":"proxy","hash":"15675","totalHash":"18884345146","validShares":679034,"invalidShares":82} - This one is not added to the monitor rigs, its on the VPS

https://supportxmr.com/api/miner//payments

Code:

[{"pt":"pplns","ts":1525351766,"amount":419975101283,"txnHash":"3a0ded8c578d43cd88954c3a63d820f3e7a12df05eb040e869d836a9e628f95b","mixin":6},{"pt":"pplns","ts":1525075256,"amount":307777442308,"txnHash":"0fc8a06be52f7c001a37461f22c9770de74887c00b2dcf796c9d22c6303bcaa5","mixin":6},{"pt":"pplns","ts":1524877698,"amount":305838960257,"txnHash":"fe5adb71693c5e207bb68790b1a75aebbb3e1c9c3da7d99d424f149e1bbb26b1","mixin":6},{"pt":"pplns","ts":1524677785,"amount":308320137180,"txnHash":"4465f4c50ca589f0668e4f8ac6aa6a9ae26c1224fcd91bfa307dc7df4e66f348","mixin":6},{"pt":"pplns","ts":1524471720,"amount":299518867949,"txnHash":"a92754baffb0cf73e7f4f53e9b45a478cbe080e8c9c06b74c213d795e3d9d9da","mixin":6},{"pt":"pplns","ts":1515029546,"amount":295072097298,"txnHash":"fc09c79022adc0fbce61dbae2fcc0398a20817b9ed794f595b7a9b918d054b60","mixin":4},{"pt":"pplns","ts":1514165344,"amount":301038148649,"txnHash":"b34fe8bb5919a2eaa4a936fd41603b1d158a76d01870fedc306b151aedf122e6","mixin":4}]

https://supportxmr.com/api/network/stats

Code:

{"difficulty":51629140831,"hash":"4906a8451ecc347d67dbf4b41d70307dc061870e34026084bdce83cd08ca7951","height":1571233,"value":4654142109567,"ts":1526141404,"expiry":1526141461169}

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: iLLNiSS on May 11, 2018, 08:58:01 PM

Perhaps some basic GPIO abilities on the RPI. You could use them to reset/power rigs without the need of a smart plug if end users tie into the power switch or reset line on their mobos.

Do you have a link where I can read about it? Those seem to be 2 slightly different use cases which I would need to implement:
1) switch PSU off-on on rig "failure"
GPIO voltage = 3.3v -> PSU on
GPIO voltage = 0v -> PSU off
GPIO voltage = 3.3v -> PSU on
2) reset PSU on rig "failure"
GPIO burst 0v->3.3v->0

rodney2250

jr. member

Activity: 177

Merit: 2

config looks ok. You might want to disable dynu DNS if you are not using it

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Also, forgot to add,
For some reason the number of GPUs online is being shown as 6, as well as hashrate per thread, there should be 26 threads in total, 16 from one rig and 10 from another but only 6 are being shown

which version of rig-monitor are you using, 2.0.b1 or 2.0.a.x?
Can you send me one of your rigs' json so I can run it through my rig-monitor test environment?

Quote from: syncro2017 on May 11, 2018, 06:07:00 PM

Another issues i noticed is when you import the dashboad.csv through sqlite3, it gives error "Wrong datatype". I had this issue both on linux and windows

Found and fixed the issue in the current development branch. The sqlite headers were included in the export, thus the datatype error. That error doesn't block the rest of the import so you should be OK.

rodney2250

jr. member

Activity: 177

Merit: 2

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

1. Im mining XMR on https://supportxmr.com and for some reason i get errors from the monitor saying JSON parsing failed when it tried to get stats for my miners, even though it did correctly identified them. Maybe the issue is that one of the miners on the pool is not xmr-stak

could you run the following API calls and send me the output? I don't use that pool and I am away from my test rig this week.
https://supportxmr.com/api/miner//stats
https://supportxmr.com/api/miner//identifiers
https://supportxmr.com/api/miner//stats/
https://supportxmr.com/api/miner//payments
https://supportxmr.com/api/network/stats

At least the network/stats API is working so there must be something funny going on

Quote from: syncro2017 on May 11, 2018, 06:00:36 PM

2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

Added to the feature request list.

iLLNiSS

newbie

Activity: 30

Merit: 0

Quote from: rodney2250 on May 11, 2018, 02:18:52 PM

I am looking at the scope of the next version (2.1). Feature candidates are:
1) wemo smart plug support
2) ability to reset rigs via smart plugs based on configurable rules
3) profitability dashboard
4) docker container for windows with grafana+influxDB+sqlite+rig-monitor

Anything else has any suggestions?

Perhaps some basic GPIO abilities on the RPI. You could use them to reset/power rigs without the need of a smart plug if end users tie into the power switch or reset line on their mobos.

syncro2017

newbie

Activity: 81

Merit: 0

Also, forgot to add,
For some reason the number of GPUs online is being shown as 6, as well as hashrate per thread, there should be 26 threads in total, 16 from one rig and 10 from another but only 6 are being shown

Another issues i noticed is when you import the dashboad.csv through sqlite3, it gives error "Wrong datatype". I had this issue both on linux and windows

Here is my config just to make sure i didn't screw up anywhere:

Code:

# Grafana DB account
[grafana]
username = "grafana"
password = "grafana"

# infulux DB configuration
[influxDb]
hostname = "http://localhost:8086"
database = "rigdata"
username = "grafana"
password = "grafana"
writeInterval = 15
influxWriteBufferSize = 100

# dynu.com Dynamic Dns Config (Optional)
[dynu]
enabled = true
username = "dynu"
password = "dynu"
hostname = "host.dynu.com"
# in seconds
updateInterval = 1800

[profitability]
# Currency for crytpo conversion and profitability calculations.
# Supported currencies are:
# "AUD", "BRL", "CAD", "CHF", "CLP", "CNY", "CZK", "DKK", "EUR", "GBP", "HKD", "HUF", "IDR", "ILS", "INR", "JPY", "KRW", "MXN", "MYR", "NOK", "NZD", "PHP", "PKR", "PLN", "RUB", "SEK", "SGD", "THB", "TRY", "TWD", "USD","ZAR"
quoteCurrency = "USD"
# Electricity costs per kWh in quoteCurrency
powerCostkWh = 0.15
# Only applicable to dual miners e.g. claymore.
# This variable specifies the percent of the total power consumption "allocated" to the 2nd coin costs.
# Default is 0.3 (30%)
powerRatioDualMining = 0.3
# Polling interval for coin info data sources: coinmarketcap.com and whattomine.com
# I suggest to keep it as those sites only update their API every 10 mins or so
marketPollingInterval = 300
# Polling interval for smart plugs. This should match the rig polling interval for data record alignment in profitability calcutation.
EnvironmentPollingInterval = 60

[main]
# number of concurrent pool polling workers. Figure should be increased if you are mining to 10 or more different pools.
poolWorkers = 3
# Polling interval for pools.
# I suggest to keep it as most pools only update their APi data every 10 mins or so
poolPollingInterval = 600
# number of concurrent rig polling workers. Figure should be increased if you have more than 10 rigs.
rigWorkers = 3
# number of concurrent rig polling workers. Figure should be increased if you are mining with 10 or more rigs.
rigPollingInterval = 60

# Can be used to monitor multilpe pools and wallet addresses. Currently only ethermine, nanopool are MPOS-based pools are supported. If you are using an unsupported pool/currency combination different then create an issue on git hub and i'll add it
# LABEL - to differentiate between pools using same backend e.g. MPOS
# POOL_TYPE - pool backend. Currrently supported pool types: ETHERMINE, NANOPOOL, MPOS (for mpos-based mining pools like mininghubpool.com)
# CURRENCY - This filed is mandatory. Tested currencies: ETH,ETC,ZEC,LBRY,SC, MUSIC and XMR.
# API_URL - pool API url. Currenlty this is only used for MPOS-based pools.
# API_TOKEN - some pools, e.g. MPOS pools, use the API token instead of the wallet address to uniquely identify miners
# WALLET_ADDRESS - wallet address
poolList = [
"label_supportXMR,nodejs-pool,XMR,https://supportxmr.com,,MY_MONERO_ADDRESS"
#"label_hashvault,nodejs-pool,sumo,https://sumokoin.hashvault.pro,,Sumooqo6kqQXQ9paUwFYAQXdGnvZ3MUfddYBKBysUdD3yG66MFBG4HWhaF8rhC"
]

# Format:
# RIG_ID, MINER, PRIMARY_POOL_LABEL, SECONDARY_POOL_LABEL, RIG_URL/IP, INSTALLED_GPUS/THREADS,TARGET_HASHRATE,TARGET_HASHRATE_2nd_COIN,PLUG_TYPE,PLUG_IP,MAX_POWER,MAX_TEMP
#RIG_ID: RIG/WORKER NAME
#MINER: claymore, xmr-stak or sgminer
#PRIMARY_POOL_LABEL: This is required in order to estimate revenue from the "associated" pool and calculate profitability.
# For profitability calculation the revenue (based on pool payments) is deducted the power costs estimated from the rig power consumption.
#SECONDARY_POOL_LABEL: Same as above for dual miners like claymore
#RIG_IP: Rig IP address or hostname.
# For claymore and xmr-stak use "http://" format. See example below.
# For sgminer use "//" format. See example below.
#INSTALLED_GPUS/THREADS: Number of installed GPUs/Threads.
# For claymore and sgminer use number of GPUs. See example below.
# For xmr-stak use use number of threads. Don't forget to include the CPU threads. See example below.
#TARGET_HASHRATE: used as baseline hashrate. this can be used to generate alarms in case hashrate drops below target value.
#TARGET_HASHRATE_2nd_COIN: same as above for miners that support dual mining e.g. claymore
# PLUG_TYPE:
# tplink - TP-Link model HS110
# noplug - Qill use the value defined in max_power for cost calculation
#PLUG_IP_ADDRESS: smart plug ip address. Field should be empty if noplug is used.
#MAX_POWER: Psu maximum power. Can be used to generate alarms in case power consumption exceeds psu maximum power. if no smartplugs are used then this value can be used as average power consumption. In that case power costs will be calculated using MAX_POWER.
#MAX_TEMP: can be used to set alarms in case gpu temp exceeds MAX_TEMP
rigList = [
# cryptonight
"MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75",
# cryptonight
"MineRig2,xmr-stak,label_supportXMR,,http://192.168.232.31:16000,10,4250,,,,650,75",
]

syncro2017

newbie

Activity: 81

Merit: 0

Quote from: rodney2250 on May 11, 2018, 02:18:52 PM

I am looking at the scope of the next version (2.1). Feature candidates are:
1) wemo smart plug support
2) ability to reset rigs via smart plugs based on configurable rules
3) profitability dashboard
4) docker container for windows with grafana+influxDB+sqlite+rig-monitor

Anything else has any suggestions?

First of all great job on the software, i installed it both on linux and windows and it works great but i did have couple of issues:

1. Im mining XMR on https://supportxmr.com and for some reason i get errors from the monitor saying JSON parsing failed when it tried to get stats for my miners, even though it did correctly identified them. Maybe the issue is that one of the miners on the pool is not xmr-stak but a proxy on a VPS but i didn't include it in the config, only the 2 gpu rigs i have at home
2. If you are looking to add features, please add support for SRBMiner and CastXMR miner, that would be great

thanks

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