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

[badalf333]

Hi,

Are you woking with the forked version of Wishbone1138 ?
https://github.com/wishbone1138/rig-monitor

2 good ideas :
Using influxdb seems to be a better choice than SQL for this kind of things.
The miner scripts are not included in the code. So it's easier to modify. (for example, I need 3334 port, so I can add a new miner with this configuration).

I have played with it, but ihave some awk return errors. What a shame !
Your work is just awesome....

[kriskarthik]

Thanks for sharing. I did not use it yet but the dashboards snapshots are looking impressive. Just a suggestion to have a mobile app for the dashboard. Many of us do not prefer the mining dashboard on a web but instead looking to have it on a mobile app which can push notification alerts when the rig is down or when the temperature going higher than the limit pls do consider having them. But thanks again for sharing.

[vl_83]

Hello, and where you can specify a password for CLAYMORE.

[badalf333]

You don't need to specify a password for Claymore... Read only is enough.

[Arle]

hi rodney

ive been looking for a monitoring app like this. I'm currently using simple mining os but i pay a fee for each rig every month. want to move my miners over to Ubuntu
and avoid paying that fee if i can get a seperate monitor like yours to work. I'm trying to learn how to code in python at home but its a bit hard.

in my little mining farm theres about 50 GPU's. every rig has GPU;s on it that belongs to different people(my friends as i pay the least for electricity) and it all mines to one wallet... so its my responsibility to transfer everyone's crypto to them.

everyone in the team agrees that dividing up the profits according to shares is the best way. currently we are just doing it by taking the ratio of an individual's gpu's and dividing by total in the farm then multiplying by the profit to get each one's payout.

so for my question can you perhaps help with code that shows the accumulated shares of each gpu in a rig over a period of time?

[heavyarms1912]

hi rodney

ive been looking for a monitoring app like this. I'm currently using simple mining os but i pay a fee for each rig every month. want to move my miners over to Ubuntu
and avoid paying that fee if i can get a seperate monitor like yours to work. I'm trying to learn how to code in python at home but its a bit hard.

in my little mining farm theres about 50 GPU's. every rig has GPU;s on it that belongs to different people(my friends as i pay the least for electricity) and it all mines to one wallet... so its my responsibility to transfer everyone's crypto to them.

everyone in the team agrees that dividing up the profits according to shares is the best way. currently we are just doing it by taking the ratio of an individual's gpu's and dividing by total in the farm then multiplying by the profit to get each one's payout.

so for my question can you perhaps help with code that shows the accumulated shares of each gpu in a rig over a period of time?

if you're using nanopool or pools that have API to the number of shares submitted per worker then you can work on top of it.

[rodney2250]

hi rodney

ive been looking for a monitoring app like this. I'm currently using simple mining os but i pay a fee for each rig every month. want to move my miners over to Ubuntu
and avoid paying that fee if i can get a seperate monitor like yours to work. I'm trying to learn how to code in python at home but its a bit hard.

in my little mining farm theres about 50 GPU's. every rig has GPU;s on it that belongs to different people(my friends as i pay the least for electricity) and it all mines to one wallet... so its my responsibility to transfer everyone's crypto to them.

everyone in the team agrees that dividing up the profits according to shares is the best way. currently we are just doing it by taking the ratio of an individual's gpu's and dividing by total in the farm then multiplying by the profit to get each one's payout.

so for my question can you perhaps help with code that shows the accumulated shares of each gpu in a rig over a period of time?

which miner are you using?

[rodney2250]

Hi all,

I have started working on the new version of rig-monitor 3 days ago. I am re-writing it in Golang for performance, scalability and and cross-platform support. Expect to have that version in 2-3 weeks.

I'll publish the repo (and compiled binaries) on github in the coming days.

Keep you posted

[rodney2250]

Hi,

Are you woking with the forked version of Wishbone1138 ?
https://github.com/wishbone1138/rig-monitor

2 good ideas :
Using influxdb seems to be a better choice than SQL for this kind of things.
The miner scripts are not included in the code. So it's easier to modify. (for example, I need 3334 port, so I can add a new miner with this configuration).

I have played with it, but ihave some awk return errors. What a shame !
Your work is just awesome....

I was working  on it with wishbone. Check the dev_influxdb branch. It's an almost finalised version using influxDB. As I mentioned above, I am working on version 2.0 which is a re-write in Golang. This will really improve the scalability for larger farms and maintenance (shell scripting is a bitch)

[rodney2250]

Hi all,

version 2.0 alpha will be release in the next couple of days.

You can read more about it here: http://randomcryptostuff.blogspot.nl/2018/04/rig-monitor-re-write-in-golang.html#more

[rodney2250]

Download and installation instruction for 2.0 alpha release here:
http://randomcryptostuff.blogspot.nl/2018/04/new-version-20alpha1-released.html


If you have issues then reply to this message or create a github issue here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.0.a1

[rodney2250]

version 2.0 has been released. Details on 1st post

[rodney2250]

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?

[syncro2017]

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

[syncro2017]

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://<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",
]

[iLLNiSS]

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.

[rodney2250]

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/<wallet>/stats
https://supportxmr.com/api/miner/<wallet>/identifiers
https://supportxmr.com/api/miner/<wallet>/stats/<rig name>
https://supportxmr.com/api/miner/<wallet>/payments
https://supportxmr.com/api/network/stats

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

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.

[rodney2250]

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.

[rodney2250]

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

[syncro2017]

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/<wallet>/stats
https://supportxmr.com/api/miner/<wallet>/identifiers
https://supportxmr.com/api/miner/<wallet>/stats/<rig name>
https://supportxmr.com/api/miner/<wallet>/payments
https://supportxmr.com/api/network/stats

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

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/<wallet>/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/<wallet>/identifiers

Code:

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

https://supportxmr.com/api/miner/<wallet>/stats/<rig name>

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/<wallet>/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}