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.2If you still face errors then please provide me with a trace: >grm -r -1 -m -1 -p <pool index in config file 1..n> |
|
|
|
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. |
|
|
|
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/APII 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 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 ;-) |
|
|
|
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: 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/Yp3Ff2beWhen running normally, it is also entering this empty data into the db: > 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/8If the output is an html the please upload the html file not just the text output. |
|
|
|
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 |
|
|
|
|
Ok. Please post a trace so I can look at the json and check how it’s being processed
|
|
|
|
Hey man, thanks for a quick reply, Here is the info you asked for: https://supportxmr.com/api/miner/<wallet>/stats {"hash":25028,"identifier":"global","lastHash":1526141126,"totalHashes":28872699609,"validShares":956038,"invalidShares":100,"expiry":1526141158601,"amtPaid":2237540754924,"amtDue":169040694230,"txnCount":0}
<wallet>/identifiers ["MineRig2","MineRig1","proxy"]
<wallet>/stats/<rig name> {"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
<wallet>/payments [{"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}]
{"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. |
|
|
|
config looks ok. You might want to disable dynu DNS if you are not using it 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? 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 {"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 <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 starts at 1 not 0 |
|
|
|
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' |
|
|
|
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: 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 starts at 1 not 0 |
|
|
|
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 |
|
|
|
config looks ok. You might want to disable dynu DNS if you are not using it 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? 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 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
Anyone else has any suggestions?
|
|
|
|
|
Show Posts
