Show Posts
|
Pages: « 1 2 [3] 4 5 »
|
XMR-Stak is not fastest cryptonight miner. You must try SRB miner. It faster XMR-Stak or XMRig.
I take the previous comment back for a moment, just downloaded the latest SRB Miner 1.6.1, seems the hashrate is on part with JCE I updated my post, just to be clear, overclock/undervolt settings were the same between all test
|
|
|
XMR-Stak is not fastest cryptonight miner. You must try SRB miner. It faster XMR-Stak or XMRig.
I tried them all my friend, SRB for me does give a higher hashrate displayed on the rig, but on the pool the hashrate is lower, also SRB is higher about 1-3 % so not worth the hassle considering the fee
|
|
|
First of all, Thanks for the great work @JCE-Miner , i believe in a while this will be the fastest miner ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Now here are the results of my test on one of my rigs. Setup : 6 Cards Asus ROG Strix RX570 4GB Hynix - Index 0 Sapphire Pulse RX580 4GB Hynix - Index 3 Sapphire Pulse RX580 4GB Hynix - Index 4 MSI RX550 LP 2GB Elpida - Index 1 MSI RX550 LP 2GB Elpida - Index 2 Asus RX550 LP 2GB Hynix - Index 5 All flashed with custom bios Mining Monero (XMR) start.bat command line for miner: jce_cn_gpu_miner64.exe -c confgpu.txt --no-cpu --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
confgpu.txt: "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":432 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":432 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":432 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":432 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 3, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 3, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 4, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 4, "multi_hash":912 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 5, "multi_hash":432 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 5, "multi_hash":432 }, ] After playing with config values for about an hour , looks like these are the best i came up with. the issue is the a very long time it takes to restart the miner because of opencl payload compilation Result after 12 hours running: 08:19:36 | Accepted by the pool. 08:19:37 | Hashrate GPU Thread 0: 476.87 h/s 08:19:37 | Hashrate GPU Thread 1: 472.91 h/s 08:19:37 | Hashrate GPU Thread 2: 258.28 h/s 08:19:37 | Hashrate GPU Thread 3: 259.26 h/s 08:19:37 | Hashrate GPU Thread 4: 249.72 h/s 08:19:37 | Hashrate GPU Thread 5: 249.91 h/s 08:19:37 | Hashrate GPU Thread 6: 502.95 h/s 08:19:37 | Hashrate GPU Thread 7: 502.85 h/s 08:19:37 | Hashrate GPU Thread 8: 487.18 h/s 08:19:37 | Hashrate GPU Thread 9: 486.15 h/s 08:19:37 | Hashrate GPU Thread 10: 262.35 h/s 08:19:37 | Hashrate GPU Thread 11: 262.57 h/s 08:19:37 | Total: 4470.93 h/s - Max: 4479.91 h/s XMR Stak 2.4.5 config: // gpu: Ellesmere memory:3673 // compute units: 32 // Asus ROG Strix RX570 4GB Elpida { "index" : 0, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 0, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, // gpu: gfx804 memory:1646 // compute units: 8 // MSI RX550 2GB Elpida { "index" : 1, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 1, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, // gpu: gfx804 memory:1646 // compute units: 8 // MSI RX550 2GB Elpida { "index" : 2, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 2, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true },
// gpu: Ellesmere memory:3673 // compute units: 36 // Sapphire Pulse RX580 4GB Hynix { "index" : 3, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 8, "comp_mode" : true }, { "index" : 3, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 8, "comp_mode" : true }, // gpu: Ellesmere memory:3673 // compute units: 36 // Sapphire Pulse RX580 4GB Hynix { "index" : 4, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 8, "comp_mode" : true }, { "index" : 4, "intensity" : 880, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 8, "comp_mode" : true }, // gpu: gfx804 memory:1646 // compute units: 8 // MSI RX550 2GB Elpida { "index" : 5, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 5, "intensity" : 440, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : true },
XMR Stak 2.4.5 result: HASHRATE REPORT - AMD
| ID | 10s | 60s | 15m | ID | 10s | 60s | 15m | | 0 | 471.2 | 471.9 | (na) | 1 | 471.2 | 470.5 | (na) | | 2 | 248.9 | 248.0 | (na) | 3 | 251.1 | 247.7 | (na) | | 4 | 243.4 | 241.6 | (na) | 5 | 238.8 | 239.5 | (na) | | 6 | 493.0 | 493.8 | (na) | 7 | 493.3 | 492.5 | (na) | | 8 | 477.3 | 477.7 | (na) | 9 | 477.1 | 476.6 | (na) | | 10 | 255.4 | 255.7 | (na) | 11 | 251.9 | 254.3 | (na) | Totals (AMD): 4372.5 4369.8 0.0 H/s ----------------------------------------------------------------- Totals (ALL): 4372.5 4369.8 0.0 H/s Highest: 4376.5 H/s -----------------------------------------------------------------
SRB Miner 1.6.1 Config: "gpu_conf" : [ { "id" : 0, "intensity" : 20, "worksize" : 16, "threads" : 2}, { "id" : 1, "intensity" : 58, "worksize" : 8, "threads" : 2}, { "id" : 2, "intensity" : 58, "worksize" : 8, "threads" : 2}, { "id" : 3, "intensity" : 20, "worksize" : 16, "threads" : 2}, { "id" : 4, "intensity" : 58, "worksize" : 8, "threads" : 2}, { "id" : 5, "intensity" : 20, "worksize" : 16, "threads" : 2}, ] }
SRB Miner 1.6.1 Result: GPU0: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 16][T: 2][K: 1][BUS: 1] GPU1: Radeon RX 570 Series [Ellesmere] [4096 MB][Intensity 58.0][W: 8][T: 2][K: 1][BUS: 3] GPU2: Radeon RX 580 Series [Ellesmere] [4096 MB][Intensity 58.0][W: 8][T: 2][K: 1][BUS: 4] GPU3: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 16][T: 2][K: 1][BUS: 5] GPU4: Radeon RX 580 Series [Ellesmere] [4096 MB][Intensity 58.0][W: 8][T: 2][K: 1][BUS: 8] GPU5: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 16][T: 2][K: 1][BUS: 9]
[2018-06-27 10:32:27] GPU0 : 470 H/s [T: 61c, RPM: 3674, CC: 1250 MHz, MC: 2000 MHz][BUS:1] [2018-06-27 10:32:27] GPU1 : 967 H/s [T: 58c, RPM: 1081, CC: 1250 MHz, MC: 1950 MHz][BUS:3] [2018-06-27 10:32:27] GPU2 : 1022 H/s [T: 64c, RPM: 765, CC: 1250 MHz, MC: 2150 MHz][BUS:4] [2018-06-27 10:32:27] GPU3 : 484 H/s [T: 57c, RPM: 3221, CC: 1250 MHz, MC: 2000 MHz][BUS:5] [2018-06-27 10:32:27] GPU4 : 988 H/s [T: 57c, RPM: 901, CC: 1250 MHz, MC: 2100 MHz][BUS:8] [2018-06-27 10:32:27] GPU5 : 494 H/s [T: 55c, RPM: 0, CC: 1250 MHz, MC: 2000 MHz][BUS:9] [2018-06-27 10:32:27] Total: 4425 H/s
Rig was running very stable for over 12 hours. Very impressive RX550 performance, over 500h/s, great job on this one! Now couple of remarks: 1. Takes a long time to generate the opencl payload for the cards, i know that this is just the first beta but would be a really good idea to implement cache so need to generate only once and then just use the pre-compiled binary and load into the cards, like xmr-stak does. 2. When reporting the share value, its always the same and is equal to a static diff i set to mine at, here is the log: 08:19:45 | GPU Thread 1 Lane 14 finds a Share, value 27060 08:19:45 | Accepted by the pool. 08:19:47 | GPU Thread 6 Lane 138 finds a Share, value 27060 08:19:47 | Accepted by the pool. 08:19:55 | GPU Thread 2 Lane 69 finds a Share, value 27060 08:19:56 | Accepted by the pool. 08:19:56 | GPU Thread 11 Lane 380 finds a Share, value 27060 08:19:56 | GPU Thread 11 Lane 390 finds a Share, value 27060 08:19:56 | Accepted by the pool. 08:19:56 | Accepted by the pool. 08:19:56 | GPU Thread 10 Lane 254 finds a Share, value 27060 as you can see value is always 27060 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Otherwise, great job!!! hope there will be more optimizations and another release soon for even more hashrate ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Yes it works, i tested, but use --low on the cpu miner or it can annoy the gpu one. As a general rule, always use --low. it should have been the default value, but that's too late now i don't want to break interface.
to disable all cpu config and mining on the gpu version, parameter --no-cpu the reciprocal --no-gpu exists too, but in such case, better stay on the pure cpu release.
When do you plan to release the GPU version for testing?
|
|
|
i was testing an optim on cn-heavy than gave negligible perf increase. then i backtested on previous algos and gpu to look for regression.
and, and don't know why, but on Pitcairn the perf has skyrocketed. my 7870 now mine at 540 on v7, on par with my 7950, and far above any other miner, even Claymore 9.7 the gain on Tahiti is smaller, i jumped from 540 to 545
Great Job man, please post the GPU version for testing, i have a variety of RX550/570/580 2GB/4GB/8GB cards i would happily test with and provide comparison results with other miners
|
|
|
how much if i need only 1? how many GPUs can i fit, are they already modified for mining setup or they are just regular server cases?
|
|
|
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
|
|
|
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 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: 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 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
|
|
|
Hey guys, there a a few exchanges where users (not only team-members) can request a coin for listing. For example: https://m.poloniex.com/coinRequest
https://gate.io/listingWe would appreciate it really much if you could share a few minutes of your valuable time to apply Sumo for listing there. Thank you a lot! I just submitted as well, thanks for the links
|
|
|
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 a lot man I will post it tonight
|
|
|
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
|
|
|
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.
|
|
|
Ok. Please post a trace so I can look at the json and check how it’s being processed
Here ya go: 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] <nil> 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] <nil> 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] <nil> 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] <nil> 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] <nil> 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] <nil> 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] <nil> 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] <nil> 2018-05-12 21:42:12.06036155 +0000 UTC m=+61.010141736 ^C devel@devel-vm:[~/WORK/RigMonitor]:
|
|
|
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 Looks like the data is in the influx, however not for all threads, here are the logs: miner_system table: > 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: > 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
|
|
|
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
|
|
|
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"}]}}
|
|
|
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}
https://supportxmr.com/api/miner/<wallet>/identifiers ["MineRig2","MineRig1","proxy"]
https://supportxmr.com/api/miner/<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
https://supportxmr.com/api/miner/<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}]
https://supportxmr.com/api/network/stats{"difficulty":51629140831,"hash":"4906a8451ecc347d67dbf4b41d70307dc061870e34026084bdce83cd08ca7951","height":1571233,"value":4654142109567,"ts":1526141404,"expiry":1526141461169}
|
|
|
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: # 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://<ip or localhost:<port>" format. See example below. # For sgminer use "//<ip or localhost:<port>" 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", ]
|
|
|
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
|
|
|
Hi I started mining ETN at your pool, it’s been around 12 hours now but my balance is still at 0. Is this normal?? I’ve been mining sumo on fair pool with no issues at all My ETN address is etnjy845LSGVQnSKhEz7jLLVfDE2CU7PaNxyj6kr7FZcZySRomovQiZXvudPp7gm11KebAgm8u7463Z wKCbsvWBf1Fq1aCMpHK Any help would be appreciated. Also when I try to change the layout threshold on ETN, to any value, it doesn’t stick and gets reset to 0
We didn't find a block yet. Once we will find a block, the pool will split the reward among the active miners. Your personal payout threshold will be set to 10 ETN by default. Just wanted to thank you for such quick support both here and over email! keep it up bro, i really appreciate it
|
|
|
|