Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: rodney2250 on August 27, 2017, 10:11:15 PM



Title: [NEW] free rig-monitor 4.0 (alpha released)
Post by: rodney2250 on August 27, 2017, 10:11:15 PM
https://www.rigmonitor.app/blog/wp-content/uploads/2018/05/final.jpg

rig-monitor is a free monitoring tool for rigs, pools, smart plugs and market data.

What's new in version 4.0 (alpha):

  • Updated market monitor module to use update coinmarketcap.com API
  • Refactored code base to make it simpler to extend/add new miners/pools/smartplugs

Complete feature list:
  • Single executable for monitoring pools, rigs, power and market data with support for logging, tracing
  • Single, consolidated mining dashboard with drop-down menu to select pool, including mining rig metrics, environment metrics (temperature, fan, power usage), market, revenue and profitably charts, etc…
  • Ability to pool thousands of rigs and dozens of pools simultaneously
  • miner support
    • claymore single/dual-mining (tested v12)
    • cgminer (not tested)
    • Xmr-stak (tested v2.4.2)
    • sgminer (not tested)
    • SRBMiner(tested v1.9.3)
    • XMRig-proxy (not tested)
    • XMRig
    • PhoenixMiner
    • CastXmr (not tested. Miner development stoped)
    • bminer
    • EWBF (not tested. Miner development stoped)
    • Ethminer
  • pool support
    • Nanopool (all coins)
    • Ethpool, Ethermine & Flypool (all coins)
    • Mpos based pools e.g. miningpoolhub.com (all coins)
    • Nodejs-pool based pools e.g. hashvaultpro.com (all coins)
    • Fairpool
    • Suprnova pools (not tested)
    • Cryptoknight pools
    • Yiimp pools (and pools using extended API e.g. Unimining)
  • power monitoring using smartplugs
    • TP-Link HS110 v1.0 and v2.0 hardware
    • Wemo Insight
  • power management rules enable users to trigger rig reset via smart plugs or external script in case a given KPI limit is crossed
    • TP-Link HS110 v1.0 and v2.0 hardware
    • Wemo Insight
    • Revive devices
    • User-defined scripts
  • Market data monitoring
    • Coinmarketcap.com
    • whattomine.com
  • Data storage using influxDB
  • Cross-platform support
    • linux/ARM
    • linux/ARM64
    • linux/x86-64
    • macOS/x86-64
    • windows/i386
    • windows/x86-64
  • Launch remote management applications like ssh or Team Viewer from Grafana
  • Custom config file replaced with toml-based config file
  • Automatic reload of rig, pool and power management rules in case of configuration file changes, during runtime
  • Notifications via Telegram

Download and instructions here: https://www.rigmonitor.app/blog/ (https://www.rigmonitor.app/blog/)

If you'd like other miners/pools/APIs to be supported then please submit a feature request on github.
For support please join the telegram group https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q (https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q)

Buy me a beer if you find this useful
BTC: 19zCtLQgUQPgZ24bPWw4CSC6N53BusXa6A
ETH: 0x0f2d4397CecB53883411cfe75882622c312c8340
MUSICOIN: 0x9a44a57041acd5f1511bf13a663d136ddbde1fb1


Title: Re: Monitoring claymore miners with a raspberry pi and grafana dashboards
Post by: jmigdlc99 on August 27, 2017, 11:50:23 PM
Wow thank you and great job putting all this together! Looks clean and does the job well.

Just a bit confused with what you said here:

Beware that, if you want to monitor power consumption you'll need the HS110s. The HS100 do not support power monitoring.

Do the smart plugs do the power monitoring or not?

Also, why use the raspberry pi as a server instead of just using the cpu on one of your rigs?


Title: Re: Monitoring claymore miners with a raspberry pi and grafana dashboards
Post by: rodney2250 on August 28, 2017, 06:00:26 AM
Wow thank you and great job putting all this together! Looks clean and does the job well.

Just a bit confused with what you said here:

Beware that, if you want to monitor power consumption you'll need the HS110s. The HS100 do not support power monitoring.

Do the smart plugs do the power monitoring or not?


Thanks.

Those are 2 different models: the HS100 supports remote power on/off, scheduling, etc... but not power consumption monitoring. For that you need the HS110, which are a bit more expensive.

Also, why use the raspberry pi as a server instead of just using the cpu on one of your rigs?

I decided to run in on a separate service for several reasons:
- I need to be able to keep monitoring the rest of the rigs during crashes and upgrades
- the raspberry will monitor rigs for "long" server freezes and reboot them automatically (this is in my TODO list)
- stability. those little things are very resilient. I have been running one for 3 years in a row without any issue

Or maybe all those reasons are bullshit and it's sys admin brain messing with me again


Title: Re: Monitoring claymore miners with a raspberry pi and grafana dashboards
Post by: jmigdlc99 on August 28, 2017, 08:32:33 AM
Wow thank you and great job putting all this together! Looks clean and does the job well.

Just a bit confused with what you said here:

Beware that, if you want to monitor power consumption you'll need the HS110s. The HS100 do not support power monitoring.

Do the smart plugs do the power monitoring or not?


Thanks.

Those are 2 different models: the HS100 supports remote power on/off, scheduling, etc... but not power consumption monitoring. For that you need the HS110, which are a bit more expensive.

Also, why use the raspberry pi as a server instead of just using the cpu on one of your rigs?

I decided to run in on a separate service for several reasons:
- I need to be able to keep monitoring the rest of the rigs during crashes and upgrades
- the raspberry will monitor rigs for "long" server freezes and reboot them automatically (this is in my TODO list)
- stability. those little things are very resilient. I have been running one for 3 years in a row without any issue

Or maybe all those reasons are bullshit and it's sys admin brain messing with me again

Awesome. That clears things up, i may have been sleepy when i wrote my post. Makes sense to have the RPI because all 3 rigs may go down at the same time. Again, great job! Thank you for the tutorial. I may do this when i get the time to do so.

 ;)


Title: Re: UPDATED: Monitoring claymore miners with grafana dashboards
Post by: rodney2250 on September 03, 2017, 11:02:13 AM
UPDATE:
Added support for Ethermine pool monitoring. Check version 1.1 https://github.com/rodneymo/rig-monitor
Current version supports currentStats and payouts APIs.
Upgrade instructions are here: http://randomcryptostuff.blogspot.nl/2017/09/update-ethermine-pool-monitoring-added.html (http://randomcryptostuff.blogspot.nl/2017/09/update-ethermine-pool-monitoring-added.html)

If you'd like other pools to be supported then please create issue


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on September 10, 2017, 09:25:33 AM
version v1.2 released.

SUPPORT FOR (CLAYMORE) DUAL MINING, COINMARKETCAP, ETHERMINE POOL, NANO POOL AND MPOS-BASED POOLS

The latest version (1.2) of rig-monitor adds the following features:
Support for claymore single and dual mining mode
Integration with ethermine pool (currentStats, payouts) API
Integration with MPOS-based pools (e.g. miningpoolhib) pool (getdashboarddata) API
Integration with nanopool API (generalinfo, payments). Supports all crypto pools (ETH, ETC, SIA, PASC, XMR and ZEC)
Integration with coinmarketcap API for monitoring crypo prices in different quote currencies, trading volume and market cap. Supports conversion to different quote currencies.
Revised template dashboards

If you'd like other pools to be supported then please create issue

Pool dashboard
https://4.bp.blogspot.com/-rBw8xqspzHU/WbUDczF3fEI/AAAAAAAAADs/EjtJhwsw1CQl2mwbaH74p8OgjY-7ykkVACLcBGAs/s1600/Screen%2BShot%2B2017-09-10%2Bat%2B11.10.11.png (https://4.bp.blogspot.com/-rBw8xqspzHU/WbUDczF3fEI/AAAAAAAAADs/EjtJhwsw1CQl2mwbaH74p8OgjY-7ykkVACLcBGAs/s1600/Screen%2BShot%2B2017-09-10%2Bat%2B11.10.11.png)

Mining overview dashboard
https://1.bp.blogspot.com/-pjUaJqXFVcs/WaHUQRYl4aI/AAAAAAAAACE/zFs4j0cclFs2qgjoRynBoqXlfsxd19SWwCLcBGAs/s1600/dashboard_1.png


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: wishbone on September 12, 2017, 02:30:18 AM
Great work!  I've been playing around with trying to do more of the data/graphing locally.  This really helps me get started.
 Here are some thoughts.

You might want to update your first post when you update this.  I was running off that for the latest instructions and they weren't up to date.  It's a convention thing to help "updates" not get lost in longer threads.

There are some issues with your walk through and user permissions.  Also I can see that you've edited out the create sql user in the create_db.sql, but your walk through does not indicate that you need to create the user.  It also does't setup permissions quite right for your script (grafana only needs SELECT but your script needs a lot more than that).  Not hard to fix, but just something to point out.  

I'm a bit confused by all the local storage of data in CSVs.  Aren't you using the database as well?

The rest of the bugs and issues I'll open on github, unless you'd prefer I put them here.

I use smartthings for HA and electricity monitoring.  I'll probably write something that either works with your script or just writes to the DB directly.  I believe I can get that data from their API.  ST is pretty popular here in the US so others might like to use that as well.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on September 12, 2017, 07:17:27 AM
Thanks for the feedback.
I am on vacation this week (and promised my gf to stay away from the laptop  :-[), so I'll have the fixes published later this week.

I'll also reply more in detail later today.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on September 13, 2017, 04:17:53 PM
Ok. Here's the proper reply:

Quote
You might want to update your first post when you update this.  I was running off that for the latest instructions and they weren't up to date.  It's a convention thing to help "updates" not get lost in longer threads.

Thanks for the tip. I will do so this wkd

Quote
There are some issues with your walk through and user permissions.  Also I can see that you've edited out the create sql user in the create_db.sql, but your walk through does not indicate that you need to create the user.  It also does't setup permissions quite right for your script (grafana only needs SELECT but your script needs a lot more than that).  Not hard to fix, but just something to point out. 

Fixed in dev branch

Quote
I'm a bit confused by all the local storage of data in CSVs.  Aren't you using the database as well?

I could insert them directly, but keeping the data in CSV allows me to recover it in case I have issues with DBs or upgrades. I think your point is valid but it's more a matter of convenience. Not using CSVs would make the scripts simpler. What's your advice?

Quote
I use smartthings for HA and electricity monitoring.  I'll probably write something that either works with your script or just writes to the DB directly.  I believe I can get that data from their API.  ST is pretty popular here in the US so others might like to use that as well.

Cool. If you do please push it to the repo


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: dantok on September 15, 2017, 03:25:09 AM
Hey Rodney,
I`m managed to get grafana and everything done. However that CSV file import to the dashboard does not work, how do i import it? Why don't we use the GUI to get it installed but it needs to be in JSON format?


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: wishbone on September 15, 2017, 03:37:48 AM
Hey Rodney,
I`m managed to get grafana and everything done. However that CSV file import to the dashboard does not work, how do i import it? Why don't we use the GUI to get it installed but it needs to be in JSON format?

You need to make sure you're following his instructions from his latest post.  It's the latest one on his blog.  The instructions have changed slightly for importing csv files.

Code:
Import dashboards

Import template dashbords via sqlite:

sudo sqlite3 /var/lib/grafana/grafana.db

sqlite> .separator ","
sqlite> .import dashboards.csv dashboard

sqlite> .quit


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on September 15, 2017, 10:29:22 AM
Thanks. I have renamed the title of the original post to installation instructions and updated it accordingly.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: kukem7 on November 12, 2017, 09:22:10 AM
I got stuck at "Create DB and rig-monitor metadata"
the comand "mysql -u root -p<mysql root password> < ./rig-monitor/sql/create_db.sql" error ???


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on November 13, 2017, 09:30:27 AM
Quote
I got stuck at "Create DB and rig-monitor metadata"
the comand "mysql -u root -p<mysql root password> < ./rig-monitor/sql/create_db.sql" error Huh

Don't you know your SQL root password? you need to enter it in order to create the database


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: kukem7 on November 13, 2017, 04:58:46 PM
it said: "bash: syntax error near unexpected token `<'" ???


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on November 13, 2017, 05:20:32 PM
 You need to replace <mysql root password> with the password


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: ejzok on January 21, 2018, 09:40:12 AM
Hi there, just a quick question, I planned to build a mining farm of around 150-200 gpus (total of around 20 rigs). In this case, do I need to link several Raspberry Pi together as a cluster computer? And if yes then how many RPis do I need, say if I want to keep database of around 2-3 days..?

Additionally, does it matter if some rigs are running Windows, some Linux, and some EthOS?

Thanks!
Ejzok


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: deepWebRun on January 22, 2018, 10:54:07 PM
Great tool and easy enough instructions.

Couple questions
1) any chance to add nanopool share & worker history? I can see ethermine has such options.
2) Currently only support Claymore, which is best for ETH. Any plans to add support for other miners, such as ZM Equihash miner? It has simple API.  https://bitcointalk.org/index.php?topic=2021765.0
3) Option to auto reboot rigs if freeze using those hs110 would be cool to have.

Again, thanks for sharing.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on January 23, 2018, 08:06:29 PM
Sorry for the late reply

Quote
1) any chance to add nanopool share & worker history? I can see ethermine has such options.
I'll take a look in a couple of weeks.

Quote
2) Currently only support Claymore, which is best for ETH. Any plans to add support for other miners, such as ZM Equihash miner? It has simple API.  https://bitcointalk.org/index.php?topic=2021765.0
Sure.

Quote
3) Option to auto reboot rigs if freeze using those hs110 would be cool to have.
I'll probably work on this first as I am facing similar issues.

Will keep you posted.
Thanks for the feedback


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: dougBTC on January 30, 2018, 09:58:42 PM
Still working on v2.0?   Planning on release any time soon?

Thank you


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: badalf333 on February 01, 2018, 01:37:21 PM
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....






Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: kriskarthik on February 01, 2018, 01:53:39 PM
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.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: vl_83 on February 07, 2018, 09:37:08 AM
Hello, and where you can specify a password for CLAYMORE.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: badalf333 on February 07, 2018, 01:36:38 PM
You don't need to specify a password for Claymore... Read only is enough.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: Arle on February 23, 2018, 06:18:43 PM
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?


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: heavyarms1912 on March 15, 2018, 07:18:37 PM
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.


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on April 13, 2018, 02:46:16 PM
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?



Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on April 13, 2018, 02:49:00 PM
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


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on April 13, 2018, 06:24:50 PM
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)


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on April 26, 2018, 06:28:09 PM
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 (http://randomcryptostuff.blogspot.nl/2018/04/rig-monitor-re-write-in-golang.html#more)


Title: Re: RIG-MONITOR v1.2 - NEW VERSION
Post by: rodney2250 on April 28, 2018, 07:31:10 PM
Download and installation instruction for 2.0 alpha release here:
http://randomcryptostuff.blogspot.nl/2018/04/new-version-20alpha1-released.html
 (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 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.0.a1)


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 11, 2018, 03:11:35 PM
version 2.0 has been released. Details on 1st post


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 11, 2018, 06: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

Anyone else has any suggestions?


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 11, 2018, 10:00:36 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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 11, 2018, 10: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

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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 12, 2018, 12:58:01 AM
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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 06:02:00 AM
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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 06:07:58 AM
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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 06:11:02 AM
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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 12, 2018, 04:11:19 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/<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}


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 12, 2018, 04:28:03 PM
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

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"}]}}



Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 12, 2018, 06:14:48 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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 06:41:37 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 <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  


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 06:46:31 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'


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 12, 2018, 07:19:38 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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 08:30:10 PM
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

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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 08:47:24 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/<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}

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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 12, 2018, 09:22:13 PM
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

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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 12, 2018, 09:37:24 PM
Ok. Please post a trace so I can look at the json and check how it’s being processed


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 12, 2018, 09:43:51 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] <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]:



Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 13, 2018, 12:07:27 AM
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 <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/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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: zeef on May 13, 2018, 01:26:51 AM
Any ideia to develop it in cast xmrstack?

Thanks


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 05:27:59 AM
Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627 (https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627)

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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 06:02:27 AM
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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 06:06:32 AM
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 <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/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


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/8 (https://github.com/rodneymo/rig-monitorv2/issues/8)
If the output is an html the please upload the html file not just the text output.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: Kaniel-ouots on May 13, 2018, 06:08:49 AM
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 )


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 06:12:28 AM
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 ;-)


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: syncro2017 on May 13, 2018, 10:30:27 AM
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.


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: syncro2017 on May 13, 2018, 11:04:11 AM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: rodney2250 on May 13, 2018, 11:58:55 AM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

Sure. I have created a new feature request on GitHub. Could you upload some json examples for both the "/" and "/workers.json" endpoints?


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 12:05:15 PM
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.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: zeef on May 13, 2018, 12:29:41 PM
Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627 (https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627)

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi,

Hope dev can give you.

Thanks


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 01:22:10 PM
Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627 (https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627)

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi,

Hope dev can give you.

Thanks

I have asked the dev, but have not gotten any reply so far. If you can provide it then I can add it tomorrow.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 13, 2018, 02:04:18 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 <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/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


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/8 (https://github.com/rodneymo/rig-monitorv2/issues/8)
If the output is an html the please upload the html file not just the text output.

Done.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 13, 2018, 03:12:39 PM
Ok. Please post a trace so I can look at the json and check how it’s being processed


Here ya go:


Thanks. Issue has been fixed on release 2.0.b.2. You can download it from GitHub


Thanks a lot man, now all the threads are showing up.
Let me know when you find a way to fix the supportxmr.com pool support.
I suppose one of the ways to do it could be just parsing the pool name and processing the json one way if its supportxmr or standard way if its not.

I'm trying to keep the binary file small. So I want to avoid duplication. I should have a solution by tomorrow.

Please check 2.1_development_2 release on GitHub: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.2

If you still face errors then please provide me with a trace:
>grm -r -1 -m -1 -p <pool index in config file 1..n>


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: syncro2017 on May 13, 2018, 05:58:54 PM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

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


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: rodney2250 on May 14, 2018, 06:09:00 AM
Got it. Thanks


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: rodney2250 on May 14, 2018, 01:26:23 PM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

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 (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.


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: syncro2017 on May 14, 2018, 02:26:00 PM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

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 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.4)). It includes support for XMRIG-PROXY and a dashboard template. Let me know if you have some issues.


Thanks for the update man,
I just tried it and got the following errors with xmrig-proxy:

No Trace:

Code:
devel@devel-vm:[~/WORK/RigMon2.1]: ./grm-2.0.d4
INFO: 2018/05/14 14:21:58 main.go:33: Starting rig-monitor...
INFO: 2018/05/14 14:21:58 main.go:50: Commmand line arguments: -config
INFO: 2018/05/14 14:21:58 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/14 14:21:58 config.go:92: Reading configuration file...
INFO: 2018/05/14 14:21:58 main.go:70: Commmand line arguments: -p 0
INFO: 2018/05/14 14:21:58 main.go:82: Commmand line arguments: -r 0
INFO: 2018/05/14 14:21:58 main.go:105: Commmand line arguments: -m 0
INFO: 2018/05/14 14:21:58 main.go:122: Connection to influxDB at http://localhost:8086 ...
INFO: 2018/05/14 14:21:58 influxdb.go:18: Starting DBDaemon routine...
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:146: Launching pool monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:152: Launching rig monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 0
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 1
INFO: 2018/05/14 14:21:59 main.go:158: Launching power monitor worker: 2
INFO: 2018/05/14 14:21:59 main.go:163: Launching market monitor worker: 0
INFO: 2018/05/14 14:21:59 pool-monitor.go:59: New pool monitor job received: label_supportXMR
INFO: 2018/05/14 14:21:59 nodejs-pool.go:62: Querying NODEJS-POOL minerStats.
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75
INFO: 2018/05/14 14:21:59 env.go:43: New environment monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
INFO: 2018/05/14 14:21:59 rig-monitor.go:40: New rig monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
INFO: 2018/05/14 14:21:59 market-monitor.go:58: New market monitor job received: XMR
INFO: 2018/05/14 14:21:59 rig-monitor.go:72:  Connection to rig MineRig2 OK.
INFO: 2018/05/14 14:21:59 rig-monitor.go:72:  Connection to rig proxy OK.
ERROR: 2018/05/14 14:21:59 xmrig-proxy.go:86: Could not decode response from proxy. Failed with json: cannot unmarshal number 0.0 into Go struct field XmrigProxyJson.donated of type int
INFO: 2018/05/14 14:22:00 market-monitor.go:174: Connection to https://api.coinmarketcap.com/v1/ticker?limit=0 OK.
INFO: 2018/05/14 14:22:00 rig-monitor.go:72:  Connection to rig MineRig1 OK.
INFO: 2018/05/14 14:22:00 market-monitor.go:174: Connection to https://whattomine.com/coins.json OK.
INFO: 2018/05/14 14:22:02 nodejs-pool.go:69: minerStats query succeeded!
INFO: 2018/05/14 14:22:02 nodejs-pool.go:74: Querying NODEJS-POOL workerIdentifiers.
INFO: 2018/05/14 14:22:02 nodejs-pool.go:81: workerIdentifiers query succeeded!
INFO: 2018/05/14 14:22:02 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(MineRig2).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(MineRig2) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(proxy).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(proxy) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:87: Querying NODEJS-POOL workerStats(MineRig1).
INFO: 2018/05/14 14:22:03 nodejs-pool.go:94: workerStats(MineRig1) query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:100: Querying NODEJS-POOL paymentStats.
INFO: 2018/05/14 14:22:03 nodejs-pool.go:107: paymentStats query succeeded!
INFO: 2018/05/14 14:22:03 nodejs-pool.go:112: Querying NODEJS-POOL networkStats.
INFO: 2018/05/14 14:22:03 nodejs-pool.go:119: networkStats query succeeded!
ERROR: 2018/05/14 14:22:03 functions.go:92: Could not parse 4783 string into float64. Exiting...

With Trace

Code:
devel@devel-vm:[~/WORK/RigMon2.1]: ./grm-2.0.d4 -p -1 -m -1 -r 3 -t
INFO: 2018/05/14 14:22:55 main.go:33: Starting rig-monitor...
INFO: 2018/05/14 14:22:55 main.go:46: Tracing is enabled!
INFO: 2018/05/14 14:22:55 main.go:50: Commmand line arguments: -config
INFO: 2018/05/14 14:22:55 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/14 14:22:55 config.go:92: Reading configuration file...
TRACE: 2018/05/14 14:22:55 config.go:109: Config file: &lib.Config{Grafana:lib.Grafana{Username:"grafana", Password:"grafana"}, Influxdb:lib.InfluxDb{Hostname:"http://localhost:8086", Database:"rigdata", Username:"grafana", Password:"grafana", WriteInterval:0xf, InfluxWriteBufferSize:0x64}, Dynu:lib.Dynu{Enabled:false, Username:"dynu", Password:"dynu", Hostname:"host.dynu.com", UpdateInterval:1800}, Profitability:lib.Profitability{QuoteCurrency:"USD", PowerCostKwh:0.15, PowerRatioDualMining:0.3, EnvPollingInterval:60, MarketPollingInterval:300}, Main:lib.Main{PoolWorkers:3, RigWorkers:3, PoolPollingInterval:600, RigPollingInterval:60, PoolConfig:[]string{"label_supportXMR,nodejs-pool,XMR,https://supportxmr.com,,45UCHuYkQfriTrWoCC2vhFYBSUHtrTsm4DJduNye42ssJagZPjG2tiFBmdgpvehAhSTCqBo2AfiS5Ukx8R1CVv1A2WiEoHk"}, RigConfig:[]string{"MineRig1,xmr-stak,label_supportXMR,,http://192.168.232.30:16000,16,4850,,,,650,75", "MineRig2,srbminer,label_supportXMR,,http://192.168.232.31:16000,5,4250,,,,550,75", "proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75"}}, PowerManagement:lib.PowerManagement{Enabled:false, Rules:[]string(nil)}}
INFO: 2018/05/14 14:22:55 main.go:70: Commmand line arguments: -p -1
INFO: 2018/05/14 14:22:55 main.go:82: Commmand line arguments: -r 3
INFO: 2018/05/14 14:22:55 main.go:105: Commmand line arguments: -m -1
TRACE: 2018/05/14 14:22:55 main.go:117: List of rigs: []string{"proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75"}
TRACE: 2018/05/14 14:22:55 main.go:118: List of pools: []string{}
INFO: 2018/05/14 14:22:55 main.go:122: Connection to influxDB at http://localhost:8086 ...
INFO: 2018/05/14 14:22:55 influxdb.go:18: Starting DBDaemon routine...
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:146: Launching pool monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:152: Launching rig monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 0
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 1
INFO: 2018/05/14 14:22:56 main.go:158: Launching power monitor worker: 2
INFO: 2018/05/14 14:22:56 main.go:163: Launching market monitor worker: 0
INFO: 2018/05/14 14:22:56 rig-monitor.go:40: New rig monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
TRACE: 2018/05/14 14:22:56 rig-monitor.go:42: New rig monitor job received: &lib.RigConfig{RigName:"proxy", Miner:"XMRIG-PROXY", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"http://159.65.227.6:8088", InstalledGpus:19, TargetHashRate:16000, TargetHashRate2:0, SmartPlugType:"noplug", SmartPlugIP:"", PSUMaxPower:0, TargetTemperature:75}
INFO: 2018/05/14 14:22:56 env.go:43: New environment monitor job received: proxy,xmrig-proxy,label_supportXMR,,http://159.65.227.6:8088,19,16000,,noplug,,1200,75
TRACE: 2018/05/14 14:22:56 env.go:45: New environment monitor job received: &lib.RigConfig{RigName:"proxy", Miner:"", PoolLabel:"label_supportXMR", PoolLabel2:"", URL:"", InstalledGpus:0, TargetHashRate:0, TargetHashRate2:0, SmartPlugType:"NOPLUG", SmartPlugIP:"", PSUMaxPower:1200, TargetTemperature:0}
TRACE: 2018/05/14 14:22:56 influxdb.go:51: New record received by DBDaemon: env_data map[label:label_supportXMR plug_type:NOPLUG rig_id:proxy] map[max_power:1200 power_usage:1200] <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





Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: rodney2250 on May 14, 2018, 02:40:06 PM
Also, for the new feature request, would you consider adding support for XMR-proxy?
Here is the link for their api https://github.com/xmrig/xmrig-proxy/wiki/API

I use this proxy with 20 miners, would be great to see individual stats for every miner
I can assist with JSON outputs if you are interested

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 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.4)). It includes support for XMRIG-PROXY and a dashboard template. Let me know if you have some issues.


Thanks for the update man,
I just tried it and got the following errors with xmrig-proxy:


It seems like a data type conflict, but I cannot troubleshoot it without the full trace. If you don't want to post it here then send it to me via telegram @rodneymo


Title: Re: rig-monitor v2.0 - Monitor rigs/pools/power/market on Windows/Linux/MacOSX
Post by: syncro2017 on May 14, 2018, 04:36:10 PM
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


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 14, 2018, 06:20:25 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 <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/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


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/8 (https://github.com/rodneymo/rig-monitorv2/issues/8)
If the output is an html the please upload the html file not just the text output.

Done.

I need a few more days. Unlike claymore the output from PhoenixMiner is not consistent e.g. most of the last paragraph does not include all the info. So I have to modified the regexs and logic.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: heavyarms1912 on May 14, 2018, 08:19:14 PM
Specific reason this is not open source?
any plans on making it open source?

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: Germini on May 14, 2018, 10:31:36 PM
Any ideia to develop it in cast xmrstack?

Thanks

Are you referring to this one? https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627 (https://bitcointalk.org/index.php?topic=2256917.msg37051627#msg37051627)

I posted there asking for a Json file and the URL to the remote management port. If you can provide both I can easily add support for it

Hi! , thanks for your work, pretty awesome dashboard i'm running it using windows 10 in a miner without any problems

When castxmr v1.0.0 is executed using --remoteaccess you go to the miner http://127.0.0.1:7777 and you get this, no file extension:
Code:
{
"total_hash_rate": 7381347,
"total_hash_rate_avg": 7268710,
"pool": {
"server": "xmr-us-east1.nanopool.org:14444",
"status": "connected",
"online": 16,
"offline": 0,
"reconnects": 0,
"time_connected": "2018-05-14 18:37:31",
"time_disconnected": "2018-05-14 18:37:31"
},
"job": {
"job_number": 1,
"difficulty": 120001,
"running": 15,
"job_time_avg": 0.00
},
"shares": {
"num_accepted": 0,
"num_rejected": 0,
"num_invalid": 0,
"num_network_fail": 0,
"num_outdated": 0,
"search_time_avg": 0.00
},
"devices": [
{
"device": "GPU0",
"device_id": 0,
"hash_rate": 1844253,
"hash_rate_avg": 1828105,
"gpu_temperature": 39,
"gpu_fan_rpm": 3657
},
{
"device": "GPU1",
"device_id": 1,
"hash_rate": 1845520,
"hash_rate_avg": 1764523,
"gpu_temperature": 41,
"gpu_fan_rpm": 3668
},
{
"device": "GPU2",
"device_id": 2,
"hash_rate": 1962401,
"hash_rate_avg": 1898305,
"gpu_temperature": 45,
"gpu_fan_rpm": 3749
},
{
"device": "GPU3",
"device_id": 3,
"hash_rate": 1729173,
"hash_rate_avg": 1777777,
"gpu_temperature": 45,
"gpu_fan_rpm": 3634
}
]
}

I will provide you with an URL so you can test it in a message

edit1: well, i can't send you messages because I am considered a newbie


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 15, 2018, 12:05:00 AM
I need a few more days. Unlike claymore the output from PhoenixMiner is not consistent e.g. most of the last paragraph does not include all the info. So I have to modified the regexs and logic.

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:

Code:
echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1","psw":"remote_monitor_password"}' | netcat MINERIP MINERPORT

If no password is used in the remote miner, you can remove the password and leave the psw in:
Code:
echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1","psw":""}' | netcat MINERIP MINERPORT

And the result from PhoenixMiner is:
Code:
{"id":0,"jsonrpc":"2.0","result":["PM 2.9e - ETH", "210", "61831;75;0", "31883;29948", "0;0;0", "off;off", "65;0;60;39", "eth-us-east1.nanopool.org:9999", "0;0;0;0"]}

A legend of what the data is:
Code:
"PM 2.9e - ETH" miner version.
""210" running time, in minutes.
"61831;75;0" total ETH hashrate in H/s, number of ETH shares, number of ETH rejected shares.
"31883;29948" detailed ETH hashrate for all GPUs. (there are 2 on this output)
"0;0;0" total DCR hashrate in H/s, number of DCR shares, number of DCR rejected shares.
"off;off" detailed DCR hashrate for all GPUs.
"65;0;60;39" Temperature and Fan speed(%) pairs for all GPUs.
"eth-us-east1.nanopool.org:9999" current mining pool. For dual mode, there will be two pools here.
"0;0;0;0" number of ETH invalid shares, number of ETH pool switches, number of DCR invalid shares, number of DCR pool switches.



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 15, 2018, 03:56:09 PM
Specific reason this is not open source?
any plans on making it open source?

That was probably the thing I thought the most about when I decided to re-write it golang. This is not set in stone and I'll re-evaluate the decision as time goes by.
My experience with rig-monitor 1.x, which is scripted and inherently open source was not really good. Got a bunch of ppl forking it, but only
one guy sporadically contributing. But, like I said I might re-evaluate the decision later on.

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.

right, but that requires an "agent" to be installed on every rig. Right now I am looking at developing all 3 options below:
1) monitor hr and power usage KPIs and reset smart plug in case of failure (currently under development; will support both TPLINK and Wemo plugs)
2) use GPIO to trigger external relays (raspberry PI only)
3) develop "agent" that can be signaled to force rig reboot via syscall


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 15, 2018, 03:58:12 PM

Hi! , thanks for your work, pretty awesome dashboard i'm running it using windows 10 in a miner without any problems

When castxmr v1.0.0 is executed using --remoteaccess you go to the miner http://127.0.0.1:7777 and you get this, no file extension:


I will provide you with an URL so you can test it in a message

edit1: well, i can't send you messages because I am considered a newbie

Thank you. I really appreciate it. I'll get on it as soon as I finish support for PhoenixMiner. I'll send you a message, maybe you can reply to it.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 15, 2018, 04:10:43 PM

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:



Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 15, 2018, 05:05:19 PM

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:



Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

I’m not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: heavyarms1912 on May 15, 2018, 07:02:50 PM
Specific reason this is not open source?
any plans on making it open source?

That was probably the thing I thought the most about when I decided to re-write it golang. This is not set in stone and I'll re-evaluate the decision as time goes by.
My experience with rig-monitor 1.x, which is scripted and inherently open source was not really good. Got a bunch of ppl forking it, but only
one guy sporadically contributing. But, like I said I might re-evaluate the decision later on.

I currently just use a simple bash script to autoreboot my rigs when power consumptions falls below a threshold value (hard system crash).  Soft crashes can be handled with mining software but not the hard crashes.  In house mining software watchdog timers fail here too.

right, but that requires an "agent" to be installed on every rig. Right now I am looking at developing all 3 options below:
1) monitor hr and power usage KPIs and reset smart plug in case of failure (currently under development; will support both TPLINK and Wemo plugs)
2) use GPIO to trigger external relays (raspberry PI only)
3) develop "agent" that can be signaled to force rig reboot via syscall

i didn't get what you meant by an agent being installed.  
I am using TP-Link HS110 and monitoring power using a bash script and power-cycle whenever it falls below the threshold value using curl http GET/POST requests, remotely (doesn't even have to be on same network).
Pretty sure the same thing can be done with a WeMo.  Or with IFFT.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 15, 2018, 07:53:30 PM

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:



Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

I’m not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.

Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 15, 2018, 07:57:01 PM
i didn't get what you meant by an agent being installed.  
I am using TP-Link HS110 and monitoring power using a bash script and power-cycle whenever it falls below the threshold value using curl http GET/POST requests, remotely (doesn't even have to be on same network).
Pretty sure the same thing can be done with a WeMo.  Or with IFFT.

I meant have a small piece of software running on the server which can receive a reboot signal from rig-monitor.
For TP-LINK I am using the provide API to read power usage and in the future reset the plug to restart the rig.
Indeed, Wemo also has an API for that. I just ordered one so I should be adding support soon.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: heavyarms1912 on May 15, 2018, 08:06:43 PM
i didn't get what you meant by an agent being installed.  
I am using TP-Link HS110 and monitoring power using a bash script and power-cycle whenever it falls below the threshold value using curl http GET/POST requests, remotely (doesn't even have to be on same network).
Pretty sure the same thing can be done with a WeMo.  Or with IFFT.

I meant have a small piece of software running on the server which can receive a reboot signal from rig-monitor.
For TP-LINK I am using the provide API to read power usage and in the future reset the plug to restart the rig.
Indeed, Wemo also has an API for that. I just ordered one so I should be adding support soon.

Oh yea got it.  but I don't get how that would solve situation in case of a hard crash.  In normal situation doesn't a good mining software handle the soft reboot?


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 16, 2018, 06:37:47 AM

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:



Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

I’m not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.

Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.

For some weird reason the dashboard was not included in the d.7 release. Will add it in the d.8 release in a couple of hours.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 16, 2018, 09:31:56 AM
development version d.8 has been published. I'll graduate this version to 2.1 (beta) in the coming days.

What's new:
Added support for SRBMiner including dashboard template.
Added support for XMRig-proxy including dashboard template.
Added support for PhoenixMiner including dashboard template.
Added support for CastXmr including dashboard template.
Added support for bastardized versions of node-js-pool API (cryptonote-pool API) e.g. supportxmr.com.

Tentative scope for 2.2:
Fairpool support
Wemo Insight smart-plug support
Power Mgmt rules (reset rigs if power or hashrate KPIs go below a configured value)


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 16, 2018, 09:39:14 AM

Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.

Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:



Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.

I’m not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.

check out dev version 2.1.d8

There a a few things that are not clear to me with regards mapping the son fields to the influxDB fields. FYI, I try to map to existing one for consistency and ability to do cross-miner reporting

      "hr":                 json.TotalHashRate,   //this is the instant HR
      "avg_result_time":    json.TotalHashRateAvg, //This seems to be the average HR since miner started
      "target_hr":          r.TargetHashRate,
      "shares_total":       json.Shares.NumAccepted + json.Shares.NumRejected + json.Shares.NumInvalid + json.Shares.NumNetworkFail + json.Shares.NumOutdated,
      "valid_shares":       json.Shares.NumAccepted,
      "invalid_shares":     json.Shares.NumInvalid,
      "stale_shares":       json.Shares.NumRejected, // Are these rejected by the pool?
      "outdated_shares":    json.Shares.NumOutdated, // are these stale shares i.e. shares submitted and block has been closed and a new block generated?
      "networkfail_shares": json.Shares.NumNetworkFail, // have no idea about these

Let me know if that's ok with you or if I should do some re-mapping


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 16, 2018, 04:08:06 PM
Hi, I'm get some errors when rig-monitor tries to get data from nanopool.
Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times
 
Code:
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range

goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits
when I'm running without pool data -p -1 it's OK
Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 16, 2018, 04:38:10 PM
Hi, I'm get some errors when rig-monitor tries to get data from nanopool.
Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times
 
Code:
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range

goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits
when I'm running without pool data -p -1 it's OK
Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ?

I noticed the same in my test setup and have created an issue (https://github.com/rodneymo/rig-monitorv2/issues/14 (https://github.com/rodneymo/rig-monitorv2/issues/14)) to handle these failures gracefully. I suggest you disable it in the meantime. I'll have a fix for it tomorrow.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 16, 2018, 07:18:01 PM
i didn't get what you meant by an agent being installed.  
I am using TP-Link HS110 and monitoring power using a bash script and power-cycle whenever it falls below the threshold value using curl http GET/POST requests, remotely (doesn't even have to be on same network).
Pretty sure the same thing can be done with a WeMo.  Or with IFFT.

I meant have a small piece of software running on the server which can receive a reboot signal from rig-monitor.
For TP-LINK I am using the provide API to read power usage and in the future reset the plug to restart the rig.
Indeed, Wemo also has an API for that. I just ordered one so I should be adding support soon.

Oh yea got it.  but I don't get how that would solve situation in case of a hard crash.  In normal situation doesn't a good mining software handle the soft reboot?

I am hoping that some syscalls are able to handle, but I won't know for sure until I test it.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 16, 2018, 07:43:20 PM
Hi, I'm get some errors when rig-monitor tries to get data from nanopool.
Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times
 
Code:
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range

goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits
when I'm running without pool data -p -1 it's OK
Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ?

I noticed the same in my test setup and have created an issue (https://github.com/rodneymo/rig-monitorv2/issues/14 (https://github.com/rodneymo/rig-monitorv2/issues/14)) to handle these failures gracefully. I suggest you disable it in the meantime. I'll have a fix for it tomorrow.

check version 2.1.d.9. It should be fixed now.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 16, 2018, 09:02:05 PM
Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.

Finally got around to testing (had a burst pipe in the basement). It seems as though it's not picking up all the details for all rigs. It shows the hashrates fine for all the rigs, but it is only reporting the gpu temp and fanspeed for one of the rigs.


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: rodney2250 on May 17, 2018, 02:05:06 AM
Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.

Finally got around to testing (had a burst pipe in the basement). It seems as though it's not picking up all the details for all rigs. It shows the hashrates fine for all the rigs, but it is only reporting the gpu temp and fanspeed for one of the rigs.

Ok. Please send me a trace and I’ll take a look at it.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 17, 2018, 09:58:27 AM
I just published a development release with Fairpool support. I'd appreciate if anyone using FairPool could test it and provide feedback (and bugs). In case of the latter please attach a trace.

Thank you


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 17, 2018, 07:58:21 PM
Anyone using cgminer? I need some real json outputs to add support to rig-monitor.

Thanks


Title: Re: NEW VERSION - RIG-MONITOR v2.0
Post by: iLLNiSS on May 17, 2018, 10:39:10 PM
Oh I never tested that.
Anyways please check the latest dev release (2.0.d.7). It includes support for PhoenixMiner and a dashboard template.

Finally got around to testing (had a burst pipe in the basement). It seems as though it's not picking up all the details for all rigs. It shows the hashrates fine for all the rigs, but it is only reporting the gpu temp and fanspeed for one of the rigs.

Ok. Please send me a trace and I’ll take a look at it.


https://pastebin.com/6McV8M08

At a quick glance I notice an error with parsing the GPU info. It's listing all the temperatures for all GPUs (line 43, 104 & 256) in the first GPU1 line instead of the standard GPU name info. The next parse with the hashrate (GPUs) is correct so that would explain why hashrates are working.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 18, 2018, 06:07:35 AM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 18, 2018, 09:30:28 PM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.

Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 18, 2018, 09:50:23 PM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.

Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.

Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that  up.
Could you also send me the  html output? Please make sure it’s complete and with the html tags.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 19, 2018, 01:45:41 PM
Hi, I'm get some errors when rig-monitor tries to get data from nanopool.
Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times
 
Code:
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range

goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits
when I'm running without pool data -p -1 it's OK
Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ?

I noticed the same in my test setup and have created an issue (https://github.com/rodneymo/rig-monitorv2/issues/14 (https://github.com/rodneymo/rig-monitorv2/issues/14)) to handle these failures gracefully. I suggest you disable it in the meantime. I'll have a fix for it tomorrow.

check version 2.1.d.9. It should be fixed now.

Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 19, 2018, 02:35:24 PM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.

Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.

Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that  up.
Could you also send me the  html output? Please make sure it’s complete and with the html tags.

This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JR


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 19, 2018, 03:49:30 PM
Hi, I'm get some errors when rig-monitor tries to get data from nanopool.
Today nanopool API is not working correctly: it gives me Error 0: undefined 8/10 times
 
Code:
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:116: minerGeneralInfo query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:123: Querying NANOPOOL minerShares.
ERROR: 2018/05/16 16:00:27 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:27 nanopool.go:128: minerShares query failed!
INFO: 2018/05/16 16:00:27 nanopool.go:147: Querying NANOPOOL networkAverageBlockTime.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:152: networkAverageBlockTime query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:159: Querying NANOPOOL networkBlocks.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:164: networkBlocks query failed!
INFO: 2018/05/16 16:00:28 nanopool.go:171: Querying NANOPOOL minerPayments.
ERROR: 2018/05/16 16:00:28 pool-monitor.go:32: Could not decode json response!
INFO: 2018/05/16 16:00:28 nanopool.go:176: minerPayments query failed!
panic: runtime error: index out of range

goroutine 34 [running]:
go-rig-monitor/pool.loadNanopoolData(0x10d90120, 0x4644b8, 0x10cfb3e0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:328 +0x2ddc
go-rig-monitor/pool.Monitor(0x4644b8, 0x10cfb3e0, 0x10d8e0c0, 0x10d27e80)
        /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:68 +0x2e8
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:147 +0x954
after this errors rig-monitor exits
when I'm running without pool data -p -1 it's OK
Is it possible to handle this error and not to stop the rig-monitor but make it retry reading jason from nanopool ?

I noticed the same in my test setup and have created an issue (https://github.com/rodneymo/rig-monitorv2/issues/14 (https://github.com/rodneymo/rig-monitorv2/issues/14)) to handle these failures gracefully. I suggest you disable it in the meantime. I'll have a fix for it tomorrow.

check version 2.1.d.9. It should be fixed now.

Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 19, 2018, 04:00:25 PM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.

Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.

Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that  up.
Could you also send me the  html output? Please make sure it’s complete and with the html tags.

This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JR

I dumped you file in my simulator and is running fine.

Code:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:165: Miner(PhoneixMiner) response from rig07:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:169: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:170: Eth speed: 238.965 MH/s, shares: 9508/0/0, time: 114:54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:173: GPUs: 1: 30.173 MH/s (1203) 2: 30.180 MH/s (1218) 3: 29.105 MH/s (1182) 4: 30.175 MH/s (1217) 5: 29.105 MH/s (1132) 6: 30.034 MH/s (1226) 7: 30.176 MH/s (1187) 8: 30.016 MH/s (1143)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:174: Eth: Average speed (5 min): 239.036 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:175: Eth: Maximum difficulty of found share: 37.8 TH (!!!)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:176: Eth: Effective speed: 229.84 MH/s; at pool: 229.84 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 1
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[1] Model: Radeon RX 570 Series (pcie 1)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[1] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[1] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[1] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 2
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[2] Model: Radeon RX 570 Series (pcie 2)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[2] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[2] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[2] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 3
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[3] Model: Radeon RX 570 Series (pcie 3)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[3] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[3] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[3] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 4
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[4] Model: Radeon RX 570 Series (pcie 4)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[4] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[4] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[4] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 5
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[5] Model: Radeon RX 570 Series (pcie 5)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[5] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[5] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[5] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 6
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[6] Model: Radeon RX 570 Series (pcie 6)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[6] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[6] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[6] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 7
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[7] Model: Radeon RX 570 Series (pcie 8)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[7] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[7] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[7] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 8
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[8] Model: Radeon RX 570 Series (pcie 9)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[8] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[8] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[8] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:187: PhoenixMiner line to parse: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:317: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[0] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[0] fan: 44
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[1] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[1] fan: 47
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[2] temperature: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[2] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[3] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[3] fan: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[4] temperature: 58
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[4] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[5] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[5] fan: 55
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[6] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[6] fan: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[7] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[7] fan: 54


Which version are you running? try with the latest 2.1.d.12


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 19, 2018, 04:21:07 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?

[/quote]

I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

[/quote]

Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?





Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 19, 2018, 04:24:07 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

[/quote]

Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?




[/quote]

And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 19, 2018, 04:42:59 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}


Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?


And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?
[/quote]

Still void:

pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:


I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 19, 2018, 04:44:56 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}


Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?


And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?

Still void:

pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:


I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs
[/quote]

I found the culprit. TP-Link 2.0 uses a slightly diff encryption. I'll need to adjust it. I'll have a fix tomorrow at latest. In the mean time I suggest you set it to "noplug"


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 19, 2018, 05:10:57 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}


Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?


And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?

Still void:

pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:


I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs
[/quote]

Paste this https://pastebin.com/27avXMEa (https://pastebin.com/27avXMEa) into a file called external/tplink2.0.py and run it e.g.
python external/tplink2.0.py -t 192.168.0.4 -c "info"


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 20, 2018, 11:43:41 AM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?

[/quote]

I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

[/quote]

Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?


And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?
[/quote]

Still void:

pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:


I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs
[/quote]

Paste this https://pastebin.com/27avXMEa (https://pastebin.com/27avXMEa) into a file called external/tplink2.0.py and run it e.g.
python external/tplink2.0.py -t 192.168.0.4 -c "info"

[/quote]



Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 12:53:37 PM
Now it runs continuously with nohup! But I got issues with tplink:

INFO: 2018/05/19 13:38:34 tplink.go:49: TPlink script execution succeeded!
ERROR: 2018/05/19 13:38:34 tplink.go:69: Could not decode response from rig03 rig's smart plug. Failed with EOF

do I have to set something or modify the firmware of HS110 ?


I am not sure. I have multiple HS110's which I bought at different periods throughout the last 12 months and been running them without issues.

Could you run this from within the grm dir and send me the output?

python  external/tplink.py -t 192.168.178.99 -j '{"emeter":{"get_realtime":{}}}'


You should get something like this:

Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

[/quote]

Thanks, but this is the output ((
Code:
pi@grafpi ~/dashboard $ python  external/tplink.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:

the IP is right because on other IP's it says me: "Cound not connect to host 192.168.0.3:9999"

Firmware version is 1.5.2 and hardware 2.0

Any ideas ?


And this one "python external/tplink.py -t 192.168.1.99 -c "info" ?

Which model exactly are you using?
[/quote]

Still void:

pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:


I'm using V3 >> https://www.tp-link.com/it/download/HS110_V3.html#FAQs
[/quote]

Paste this https://pastebin.com/27avXMEa (https://pastebin.com/27avXMEa) into a file called external/tplink2.0.py and run it e.g.
python external/tplink2.0.py -t 192.168.0.4 -c "info"

[/quote]



Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $

[/quote]

I meant after creating the new version of tplink2.0, could you run it and send me the output?

>python external/tplink2.0.py -t 192.168.0.4 -c "info"


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 20, 2018, 04:38:52 PM
Found the issue. The format of the GPU temp+fan line is very close to the GPU specs line so when one has rigs with more than 4 GPUs this issue happened. I never saw this issue as my test rig only has 2 cards.

Anyways, it's been fixed in 2.1.d10.

Let me know if you have any other problems.

Still not seeing it on anything but my 2 gpu rig. https://pastebin.com/T0XUbxey

It seems to be picking up the info, but still not parsing it correctly.

Arghh.... I tried to reconstruct the html output from the trace. Guess I screwed that  up.
Could you also send me the  html output? Please make sure it’s complete and with the html tags.

This is direct from an 8 GPU rig. https://pastebin.com/qkjGq8JR

I dumped you file in my simulator and is running fine.

Code:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:165: Miner(PhoneixMiner) response from rig07:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:167: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:169: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:170: Eth speed: 238.965 MH/s, shares: 9508/0/0, time: 114:54
TRACE: 2018/05/19 17:53:25 phoenixminer.go:173: GPUs: 1: 30.173 MH/s (1203) 2: 30.180 MH/s (1218) 3: 29.105 MH/s (1182) 4: 30.175 MH/s (1217) 5: 29.105 MH/s (1132) 6: 30.034 MH/s (1226) 7: 30.176 MH/s (1187) 8: 30.016 MH/s (1143)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:174: Eth: Average speed (5 min): 239.036 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:175: Eth: Maximum difficulty of found share: 37.8 TH (!!!)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:176: Eth: Effective speed: 229.84 MH/s; at pool: 229.84 MH/s
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 1
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[1] Model: Radeon RX 570 Series (pcie 1)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[1] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[1] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[1] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 2
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[2] Model: Radeon RX 570 Series (pcie 2)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[2] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[2] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[2] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 3
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[3] Model: Radeon RX 570 Series (pcie 3)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[3] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[3] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[3] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 4
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[4] Model: Radeon RX 570 Series (pcie 4)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[4] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[4] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[4] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 5
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[5] Model: Radeon RX 570 Series (pcie 5)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[5] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[5] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[5] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 6
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[6] Model: Radeon RX 570 Series (pcie 6)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[6] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[6] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[6] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU7: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 7
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[7] Model: Radeon RX 570 Series (pcie 8)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[7] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[7] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[7] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:181: PhoenixMiner line to parse: GPU8: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 4 GB VRAM, 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:298: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:299: Active GPUs: 8
TRACE: 2018/05/19 17:53:25 phoenixminer.go:300: GPU[8] Model: Radeon RX 570 Series (pcie 9)
TRACE: 2018/05/19 17:53:25 phoenixminer.go:301: GPU[8] Memory: 4 GB VRAM
TRACE: 2018/05/19 17:53:25 phoenixminer.go:302: GPU[8] Memory: OpenCL 2.0
TRACE: 2018/05/19 17:53:25 phoenixminer.go:303: GPU[8] Computer Units: 32 CUs
TRACE: 2018/05/19 17:53:25 phoenixminer.go:187: PhoenixMiner line to parse: GPU1: 59C 44%, GPU2: 59C 47%, GPU3: 53C 40%, GPU4: 59C 59%, GPU5: 58C 40%, GPU6: 59C 55%, GPU7: 59C 53%, GPU8: 59C 54%
TRACE: 2018/05/19 17:53:25 phoenixminer.go:317: Claymore line parsing result:
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[0] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[0] fan: 44
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[1] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[1] fan: 47
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[2] temperature: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[2] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[3] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[3] fan: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[4] temperature: 58
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[4] fan: 40
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[5] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[5] fan: 55
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[6] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[6] fan: 53
TRACE: 2018/05/19 17:53:25 phoenixminer.go:319: GPU[7] temperature: 59
TRACE: 2018/05/19 17:53:25 phoenixminer.go:320: GPU[7] fan: 54


Which version are you running? try with the latest 2.1.d.12

This was with 2.1.d.12.

I'm at a standstill now. I can't even run the app anymore. For whatever reason when I kill the app with ctrl+c, it refuses to run again. This seems to require me a wipe of everything to start over which is quite time consuming. I only get one chance to run it before it throws this error after killing it:
Code:
panic: runtime error: index out of range

goroutine 25 [running]:
go-rig-monitor/miner.loadPhoenixMinerData(0xc4200c6140, 0x9150c0, 0xc42014e0c0, 0xc4200a5c80, 0x1)
        /Users/ramf/go/src/go-rig-monitor/miner/phoenixminer.go:141 +0x28d0
go-rig-monitor/miner.Monitor(0x9150c0, 0xc42014e0c0, 0xc4200a5e60, 0xc4200a5c80)
        /Users/ramf/go/src/go-rig-monitor/miner/rig-monitor.go:57 +0x611
created by main.main
        /Users/ramf/go/src/go-rig-monitor/main.go:153 +0xcd2


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 04:44:39 PM
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.

I need to improve that error handling.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 20, 2018, 05:00:07 PM
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.

I need to improve that error handling.

Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 05:35:49 PM
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.

I need to improve that error handling.

Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already.

About hat error, there’s a double square bracket at the end. It’s a typo. If you delete one of them then it fixes it.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 20, 2018, 05:47:37 PM

Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $

[/quote]

I meant after creating the new version of tplink2.0, could you run it and send me the output?

>python external/tplink2.0.py -t 192.168.0.4 -c "info"
[/quote]

running with new tplink code gives me this error:

Code:
INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76:  Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 06:48:37 PM

Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $


I meant after creating the new version of tplink2.0, could you run it and send me the output?

>python external/tplink2.0.py -t 192.168.0.4 -c "info"
[/quote]

running with new tplink code gives me this error:

Code:
INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76:  Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!


[/quote]

Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv (https://pastebin.com/Z42cBYkv)


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 20, 2018, 08:31:47 PM
That's probably the rig index that you are using. Rig index start from 1 and if select, say, -r 4, but you only have 3 rigs in your list it will fail with that error.

I need to improve that error handling.

Oh sweet. This error occurs just by launching the program, but manually setting the rig index (in my case -r -4) the program appears to run. Will have to setup again as I purged grafana and influx already.

About hat error, there’s a double square bracket at the end. It’s a typo. If you delete one of them then it fixes it.

In my case that isn't the problem. I removed that when I first edited the conf, but the app still throws the error. With the double square it throws this error:
Code:
pi@raspberrypi:~/grm $ ./grm-2.1.d12
INFO: 2018/05/20 20:30:38 main.go:33: Starting rig-monitor...
INFO: 2018/05/20 20:30:38 main.go:50: Commmand line arguments: -config
INFO: 2018/05/20 20:30:38 main.go:54: No config file specified. Using default config.toml file: config.toml
INFO: 2018/05/20 20:30:38 config.go:92: Reading configuration file...
ERROR: 2018/05/20 20:30:38 config.go:100: Couldn't load config: While parsing config: (97, 2): unexpected token

Currently I'm no longer able to see any data populated to the phoenixminer dashboard in 2.1.d.12. I think it has to do somehow with being forced to launch with the -r -4 flag as I never had issues with that prior.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 08:33:02 PM
Check the config file. You probably have 2 "]" at the end.

should have only one. It was a typo on the release.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 20, 2018, 09:10:53 PM
Check the config file. You probably have 2 "[" at the end.

should have only one. It was a typo on the release.

I removed the second ] before I was even getting any errors. There is no second ] at the end like in the original config on your release.

Here is a trace without the index flag set:
https://pastebin.com/srpaxU1X

Here is a trace with the index set to 4 to match the 4 in the config:
https://pastebin.com/xEkZHLur

It seems as though despite specifying the index to allow the program to run without error, it doesn't actually do anything after.

As I was typing this and verifying all my ducks were in a row before submitting, I found the issue. The 'riglist = [ ]' section throws an error when I have 4 rigs added. Removing 1 and the app runs just fine.



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 20, 2018, 09:16:47 PM
Check the config file. You probably have 2 "[" at the end.

should have only one. It was a typo on the release.

I removed the second ] before I was even getting any errors. There is no second ] at the end like in the original config on your release.

Here is a trace without the index flag set:
https://pastebin.com/srpaxU1X

Here is a trace with the index set to 4 to match the 4 in the config:
https://pastebin.com/xEkZHLur

It seems as though despite specifying the index to allow the program to run without error, it doesn't actually do anything after.

As I was typing this and verifying all my ducks were in a row before submitting, I found the issue. The 'riglist = [ ]' section throws an error when I have 4 rigs added. Removing 1 and the app runs just fine.



On my cell now so it’s hard to read the traces.

So is phoenixminer working properly now?

Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 20, 2018, 10:19:31 PM
On my cell now so it’s hard to read the traces.

So is phoenixminer working properly now?

Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config?

It's working properly, but only with 3 rigs. Any more and it throws errors.

I've tried with and without the "," after the last rig line and all others have a "," after them.

Forgot to mention, I sent a link to my config via PM.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 06:10:28 AM
On my cell now so it’s hard to read the traces.

So is phoenixminer working properly now?

Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config?

It's working properly, but only with 3 rigs. Any more and it throws errors.

I've tried with and without the "," after the last rig line and all others have a "," after them.

Forgot to mention, I sent a link to my config via PM.

Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 21, 2018, 07:15:47 AM

Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $


I meant after creating the new version of tplink2.0, could you run it and send me the output?

>python external/tplink2.0.py -t 192.168.0.4 -c "info"

running with new tplink code gives me this error:

Code:
INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76:  Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!


[/quote]

Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv (https://pastebin.com/Z42cBYkv)
[/quote]

Great ! Seems that it works now !!!

Code:
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:  {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h                                                                  w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03",                                                                   "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45                                                                                                                                  5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000                                                                    0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D                                                                    AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}


pi@grafpi ~/dashboard $ python  external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 11:25:03 AM

Now it runs endless and when I interrupt I got this:

Code:
pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
  File "external/tplink.py", line 71, in <module>
    sock_tcp.connect((ip, port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $


I meant after creating the new version of tplink2.0, could you run it and send me the output?

>python external/tplink2.0.py -t 192.168.0.4 -c "info"

running with new tplink code gives me this error:

Code:
INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76:  Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!



Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv (https://pastebin.com/Z42cBYkv)
[/quote]

Great ! Seems that it works now !!!

Code:
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:  {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h                                                                  w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03",                                                                   "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45                                                                                                                                  5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000                                                                    0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D                                                                    AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}


pi@grafpi ~/dashboard $ python  external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}


[/quote]

I PM'd you. The latest 2.1d14 version should fix the data insertion into influx


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 21, 2018, 02:37:00 PM


Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv (https://pastebin.com/Z42cBYkv)
[/quote]

Great ! Seems that it works now !!!

Code:
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:  {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h                                                                  w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03",                                                                   "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45                                                                                                                                  5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000                                                                    0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D                                                                    AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}


pi@grafpi ~/dashboard $ python  external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}


[/quote]

I PM'd you. The latest 2.1d14 version should fix the data insertion into influx
[/quote]

I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0



Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 02:42:18 PM


Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv (https://pastebin.com/Z42cBYkv)

Great ! Seems that it works now !!!

Code:
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent:      {"system":{"get_sysinfo":{}}}
Received:  {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h                                                                  w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03",                                                                   "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45                                                                                                                                  5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000                                                                    0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D                                                                    AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}


pi@grafpi ~/dashboard $ python  external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}


[/quote]

I PM'd you. The latest 2.1d14 version should fix the data insertion into influx
[/quote]

I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


[/quote]
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 21, 2018, 03:04:26 PM
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.

That was the case originally, but I've since added another card to it.

Here is the html output from phoenix:
https://pastebin.com/m4WEtyrR

Here is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config:
https://pastebin.com/Y6UkYAkZ

The only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay).


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 03:18:48 PM
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.

That was the case originally, but I've since added another card to it.

Here is the html output from phoenix:
https://pastebin.com/m4WEtyrR

Here is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config:
https://pastebin.com/Y6UkYAkZ

The only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay).

Got it. Now I am able to reproduce it.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 03:38:03 PM
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.

That was the case originally, but I've since added another card to it.

Here is the html output from phoenix:
https://pastebin.com/m4WEtyrR

Here is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config:
https://pastebin.com/Y6UkYAkZ

The only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay).

Try version 2.1.d15


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 21, 2018, 03:43:13 PM
Try version 2.1.d15

Thanks! I'll respond with an update if an incorrect pops up again.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 21, 2018, 07:14:46 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...




Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 08:02:10 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...



Yes, I had already coded that part but as I cannot test it ....
Could you check test version 2.1.d14a
I have added extra tracing info


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 21, 2018, 09:09:34 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...



Yes, I had already coded that part but as I cannot test it ....
Could you check test version 2.1.d14a
I have added extra tracing info

Still 0s in grafana, but the grm message is slightly different:

INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded!
INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded!
version 2.0 517792


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 21, 2018, 09:11:02 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...



Yes, I had already coded that part but as I cannot test it ....
Could you check test version 2.1.d14a
I have added extra tracing info

Still 0s in grafana, but the grm message is slightly different:

INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded!
INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded!
version 2.0 517792


OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 21, 2018, 11:52:15 PM
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 22, 2018, 04:26:45 AM
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 22, 2018, 01:51:46 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...



Yes, I had already coded that part but as I cannot test it ....
Could you check test version 2.1.d14a
I have added extra tracing info

Still 0s in grafana, but the grm message is slightly different:

INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded!
INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded!
version 2.0 517792


OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.


Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)




Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 22, 2018, 02:11:20 PM
I tried with v 2.1d14 and this are the results:
1) python file "tplink.py" works
2) grm process says : "...response from rig decoded"
3) in grafana "power_usage" is still 0


Quote
ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
 this on a trial and error basis ...
Which OS are you using?

I'm using raspbian

pi@grafpi ~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


Python 2.7.9

Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close!

I noticed that your output of tplink.py is different from mine!

Your example:

You should get something like this:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}

My output:
Code:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}

names of parameters are different...



Yes, I had already coded that part but as I cannot test it ....
Could you check test version 2.1.d14a
I have added extra tracing info

Still 0s in grafana, but the grm message is slightly different:

INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded!
INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded!
version 2.0 517792


OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.


Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)




Have you check the power detail template dashboard? Are the values showed there correct?


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: tradersblog on May 22, 2018, 03:00:18 PM
Quote

OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.

Quote

Thanks a lot!
Now I got values in grafana, but I cannot understand them:

1) selecting "power_usage" mean 1m >> 258
2) selecting "power_usage" last 1m >> 362

here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5E

and this is my python output:
Sent:      {"emeter":{"get_realtime":{}}}
Received:  {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}}

226 volts OK
518 Whats OK (4 RX 570 GPU)



[/quote]

Have you check the power detail template dashboard? Are the values showed there correct?
[/quote]

I've uploaded the txt file of the output of the influxdb query >> http://textuploader.com/dfy1e

can you create a grm developing channel in telegram ? it's more simple to communicate with frequent messages and attachements...


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 22, 2018, 05:58:32 PM
Hi all,

I have created a telegram group for the rigmonitor community. Here's the link: https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q (https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q)

rodneymo


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 22, 2018, 10:08:47 PM
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.

Nah, on an RPI.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 23, 2018, 04:02:19 AM

So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the  influx log


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: iLLNiSS on May 24, 2018, 12:16:26 AM

So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the  influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 24, 2018, 02:16:59 PM

So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the  influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.

Found some memory leaks, which have been fixed in 2.1.d17.

I have tested it on my raspberry PI 1 and it's been running fine for almost 3 hours now.


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: Germini on May 25, 2018, 07:04:20 AM
Hi, I've been trying to customize the panels available from claymore and castxmr but when copying overall rig status from claymore to other dashboard I see that Mining Time has incorrect values. How to fix this?

After some debugging I realized that the query from the original panel is different than the copied one. Is there any way to make it the same?. Where to specify $timeFilter in the copied one?

in the query of the original panel it says:
Code:
"SELECT installed_gpus,active_gpus/installed_gpus,last(hr)*1000000, target_hr*1000000,"mining_time" FROM "miner_system" WH ERE miner='CLAYMORE' and time >= now() - 24h group by "rig_id""
in the query of the copied panel it says:
Code:
"SELECT installed_gpus,active_gpus/installed_gpus,last(hr)*1000000, target_hr*1000000,"mining_time" FROM "miner_system" WH ERE miner='CLAYMORE' and time >= 1527129649148ms and time <= 1527151249150ms group by "rig_id""

I separated the word WHERE to avoid blocking from forum

EDIT: The time range in the top right was between an old time that is the $timeFilter so that's why the values are outdated. I leave the post for anyone with the same problem to fixit.

Thanks for your work rodney2250!!  :D :D


Title: Re: rig-monitor 2.0 - Monitor rigs/pools/power/market on any OS
Post by: rodney2250 on May 25, 2018, 02:09:21 PM

So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is:
Code:
ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...

I can fire the app back up and it runs fine. Any ideas?
I had that problem before. Are you running it on a laptop? Check your power settings.

Nah, on an RPI.

Try to increase the influx write interval eg 30s.

If that doesn’t work then send me a trace together with the  influx log

Below is after increasing to 30s in the rig-monitor conf.

Influx log (line 499 has the timeout):
https://pastebin.com/qE4v6rr1

rig-monitor log with console output at the end:
https://pastebin.com/k55KpGbM

As you can see, this was almost 1 hour on the button. So far all have crashed at 15min intervals around an hour.

New (stable) version 2.1 has been released. That issue  should be permanently fixed in that version. I have it running for many hours now and both influxDB connection as well as memory usage are stable.


Title: Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Post by: rodney2250 on May 25, 2018, 02:11:03 PM
Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo


Title: Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Post by: iLLNiSS on May 26, 2018, 03:58:32 AM
Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.


Title: Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Post by: rodney2250 on May 26, 2018, 06:31:06 AM
Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.

About the timeout, I think we need to rule out a grm issue as I have been running it on a raspberry PI 1 for almost days without issues.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?

I'll. take a look at the Nvidia output and provide you a fix.


Title: Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Post by: rodney2250 on May 26, 2018, 02:05:50 PM
Hi all,

version 2.1 (stable) has been released. Besides the new features this version solves multiple memory management issues so I suggest you upgrade ASAP.

rodneymo

Trying it out now. The last release still errored out for the same influxdb timeout with the 30s limit.

I seem to have found another issue with the parsing. My Nvidia card sometimes errors out and the driver stops reporting fanspeed. After that happens, rig-monitor does not report the fanspeed or the temperatures for the other cards despite them being available in the html output.

HTML output:
https://pastebin.com/JYRwbNbS

Grafana just lists all 3 cards as 0 for fanspeed/temps.

Fix in 2.1.1


Title: Re: [NEW VERSION] rig-monitor 2.1 now support for SRBMiner,XMRig-proxy,PhoenixMiner
Post by: iLLNiSS on May 26, 2018, 04:44:11 PM
About the timeout, I think we need to rule out a grm issue as I have been running it on a raspberry PI 1 for almost days without issues.
Could you PM you config file, I'll set up my simulator to see if everything checks out.
Also, what's the command you are using to start grm? and are you running it as a service or from the command line?

I'll. take a look at the Nvidia output and provide you a fix.

With 2.1.0 it has stopped crashing on me and has now been running for 13 hours, so that's good :)

With 2.1.1 the fanspeed issue is resolved on my end. Good work. Your efforts are much appreciated.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: sergey1301 on May 27, 2018, 07:05:48 AM
I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 27, 2018, 07:07:31 AM
I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

Hi Sergey,

you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/ (https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/)


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: sergey1301 on May 27, 2018, 07:20:08 AM
I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

Hi Sergey,

you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/ (https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/)

Thank you!


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: iLLNiSS on May 27, 2018, 04:10:45 PM
I use raspberry pi as a server. I need to be able to follow the rest of the settings. In raspberry there is control of the installation.

Hi Sergey,

you can find the instructions here: https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/ (https://www.rigmonitor.app/blog/version-2-0-beta-installation-instructions/)

Thank you!

I use a script to simplify the influx and grafana install for raspberry pi (tested on raspbian stretch) if you're having any trouble installing them.

Code:
# Create InfluxDB and Grafana 4.4.3 (latest)
source /etc/os-release
OPSYS=${ID^^}
curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
test $VERSION_ID = "8" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
test $VERSION_ID = "9" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list
curl https://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv6"* ]] && echo "deb https://dl.bintray.com/fg2it/deb-rpi-1b jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
[[ $OPSYS == *"BIAN"* ]] && [[ $(uname -m) == *"armv7l"* ]] && echo "deb https://dl.bintray.com/fg2it/deb jessie main" | sudo tee -a /etc/apt/sources.list.d/grafana.list
sudo apt-get -y $AQUIET remove --purge grafana grafana-data
sudo apt-get -y $AQUIET autoremove
sudo apt-get -y update && sudo apt-get install -y apt-transport-https curl influxdb grafana
sudo systemctl daemon-reload
sudo systemctl enable influxdb
sudo systemctl start influxdb
sudo systemctl enable grafana-server
sudo systemctl start grafana-server

And if you're looking to set up rig monitor as a system service, here is a systemctl service file you can create (/lib/systemd/system/grm.service). Just make sure to set the execstart and workingdirectory to where your grm files are. If you do not set the workingdirectory grm will error out that it can't locate your config file even if you specify the location with -config.
Code:
[Unit]
Description=Rig Monitor
After=multi-user.target

[Service]
Type=idle
WorkingDirectory=/opt/grm
ExecStart=/opt/grm/grm

[Install]
WantedBy=multi-user.target

After creating the file do a daemon-reload, enable the service and start the service.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 28, 2018, 09:49:45 AM
Would you mind if I add this to future release packages? Of course I'll add the necessary info and license about the author


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 28, 2018, 09:51:00 AM
For those of you using CastXMR, version 2.1.2 has been released.  It adds support for "mining_time" and updates the "Rig Overall status" panel on the respective dashboard template.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: iLLNiSS on May 28, 2018, 12:43:36 PM
Would you mind if I add this to future release packages? Of course I'll add the necessary info and license about the author

I didn’t create the script, it was sourced from here:
https://tech.scargill.net/grafana-and-influxdb/

If that’s what you’re referring to.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 29, 2018, 12:06:34 PM


Hi all,

I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.

If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2)


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 30, 2018, 05:05:41 AM

I have just create a mining overview example dashboard that combines rig, pool and market data. See picture below. This example will be included in future releases, but in the meantime you can download it from here https://github.com/rodneymo/rig-monitorv2/issues/10 (https://github.com/rodneymo/rig-monitorv2/issues/10)

https://www.rigmonitor.app/blog/wp-content/uploads/2018/05/final.jpg


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 30, 2018, 07:26:59 AM


I just published a post on the blog explaining the power management feature. You can read about it here: https://www.rigmonitor.app/blog/using-rig-monitors-power-management-feature/ (https://www.rigmonitor.app/blog/using-rig-monitors-power-management-feature/)


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: iLLNiSS on May 30, 2018, 12:08:48 PM


Hi all,

I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.

If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2)

This link appears to only have the readme file included.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 30, 2018, 01:23:24 PM


Hi all,

I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.

If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2)

This link appears to only have the readme file included.

Yes. Sorry that’s because in the meantime I fixed several bugs.
The latest dev version is 2.2.d6


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 30, 2018, 06:32:15 PM


Hi all,

I have just published the 2.2_development_2 version. This version includes, amongst other things, the ability to reset rigs via Wemo or TP-Link smart plugs through user defined rules.

If you want to test it then you can download it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.2.d.2)

This link appears to only have the readme file included.

Yes. Sorry that’s because in the meantime I fixed several bugs.
The latest dev version is 2.2.d6

I just posted another dev version 2.2.d7, which adds automatic reload of rig, pool and power management rules in case of configuration file changes, during runtime.


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on May 31, 2018, 10:38:42 AM


Hi all,

just published version 2.1.3. This release fixes issues with rig-monitor crashing when
claymore output is out of order (sometimes Total speed & shares line come up before the GPU spec lines).

You can download it from here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.3 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.3)


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on June 01, 2018, 10:38:25 AM


I just came accross of a nice way to launch TeamViewer app and SSH from Grafana. Take a look at it here: https://www.rigmonitor.app/blog/launching-rig-management-applications-from-grafana/


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on June 01, 2018, 01:12:07 PM


I just came accross of a nice way to launch TeamViewer app and SSH from Grafana. Take a look at it here: https://www.rigmonitor.app/blog/launching-rig-management-applications-from-grafana/

Version 2.2 is out!!

What's new in version 2.2:


-Support for fairpool
-Support for monitoring power consumption via Wemo smart plugs
-Automatically reset rigs - via TP-Link and  Wemo smart plugs - based on power consumption, hashrate or any other available KPI in influxDB (power mgmt rules)
-Ability to trigger custom scripts (e.g. control external device that resets rig PSU) based on power consumption, hashrate or any other available KPI in influxDB (power mgmt rules)
-Automatic reload of rig, pool and power management rules in case of configuration file changes, during runtime. Other settings are not updated during runtime.
-Launch remote management applications like ssh or Team Viewer from Grafana
-CastXMR now includes "mining_time"
-Fixed issue with crashing due to claymore output being out of order (sometimes Claymore outputs the Total speed & shares line before the GPU spec lines)
-Several other minor bug fixes and improvements

You can download it here: https://github.com/rodneymo/rig-monitorv2/releases (https://github.com/rodneymo/rig-monitorv2/releases)


Title: Re: [NEW VERSION]rig-monitor now supports SRBMiner,XMRig-proxy,PhoenixMiner,CastXmr
Post by: rodney2250 on June 01, 2018, 05:01:16 PM


I just came accross of a nice way to launch TeamViewer app and SSH from Grafana. Take a look at it here: https://www.rigmonitor.app/blog/launching-rig-management-applications-from-grafana/

Version 2.2 is out!!

What's new in version 2.2:


-Support for fairpool
-Support for monitoring power consumption via Wemo smart plugs
-Automatically reset rigs - via TP-Link and  Wemo smart plugs - based on power consumption, hashrate or any other available KPI in influxDB (power mgmt rules)
-Ability to trigger custom scripts (e.g. control external device that resets rig PSU) based on power consumption, hashrate or any other available KPI in influxDB (power mgmt rules)
-Automatic reload of rig, pool and power management rules in case of configuration file changes, during runtime. Other settings are not updated during runtime.
-Launch remote management applications like ssh or Team Viewer from Grafana
-CastXMR now includes "mining_time"
-Fixed issue with crashing due to claymore output being out of order (sometimes Claymore outputs the Total speed & shares line before the GPU spec lines)
-Several other minor bug fixes and improvements

You can download it here: https://github.com/rodneymo/rig-monitorv2/releases (https://github.com/rodneymo/rig-monitorv2/releases)

Anyone has any new requirements/features for 2.3? I am currently working out the scope for release 2.3. Current candidates:

-profitability calc. and dashboard
-bminer support
-resetting PSU via raspberry GPIO


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: Buda on June 02, 2018, 12:33:51 PM
Hi!

Your job is awesome. Please add miner.rocks pool support, and sonofff plug support.

Thanks.


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 02, 2018, 05:38:39 PM
Hi!

Your job is awesome. Please add miner.rocks pool support, and sonofff plug support.

Thanks.

Thanks. I noticed you already created a GitHub feature request. I'll take it from here.


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 02, 2018, 07:08:30 PM
Anyone using raspberry PIs who would like to use the GPIO to reset rigs?


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: IndieMiner on June 02, 2018, 10:42:32 PM
This is a very useful tool, thank you for sharing! Will be looking forward to using this with more pools as they become supported.
Keep up the great work!


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 03, 2018, 12:29:10 PM
This is a very useful tool, thank you for sharing! Will be looking forward to using this with more pools as they become supported.
Keep up the great work!

Thanks. Do you have other pools in mind? Which ones?


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 04, 2018, 06:04:17 PM

Hi all, version 2.3.d1 (development) has been published. It includes support for bminer and EWBF miners. You can get it here:https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d1 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d1)
Later this week I'll make another release with the all-new (past ad future) profitability logic and dashboards.


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 04, 2018, 08:03:15 PM

Hi all, version 2.3.d1 (development) has been published. It includes support for bminer and EWBF miners. You can get it here:https://github.com/rodneymo/rig-monitorv2/releases/tag/untagged-c30d233b2b307bbc6d7a
Later this week I'll make another release with the all-new (past ad future) profitability logic and dashboards.

this is the correct link for version 2.3.d1:
https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d1 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d1)


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 08, 2018, 01:52:58 PM

Hi all,

version 2.3.d3 (development) has been published. It includes support for:
bminer
EWBF
Ethminer
suprnova pools

You can get it here:https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d.3 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.d.3)
Next this week I'll make another release with the all-new profitability logic and dashboards.


Title: Re: [New version]rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 09, 2018, 07:30:38 AM

Hi all,
I found a bug on the claymore praser during the stability testing (10 days). It's rare, I have only seen it once, but I am issuing a patch nonetheless to both developement and stable branches:
2.2.2 (stable)
2.3.d.5 (developement)

you can download them here: https://github.com/rodneymo/rig-monitorv2/releases


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: eXta on June 09, 2018, 11:20:45 AM
Hi !

First, many thanks for this very usefull tool !

I was planning for tests with https://github.com/Kasmetski/auto-hard-reset for Pi GPIO until I found your project. I'm interested in testing your solution with Pi 3 if needed.
I'm looking after nicehash pool, minergate pools and cryptoknight.cc pools support if you still take feature requests. For this last pool, I'll try to look into the sources, I think it may be close to node-js/fairpool code.
Would be glad to contribute if I can, I really appreciate that you have opened your sources.

Again, thank you for your awesome Rig Monitor



Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 09, 2018, 07:33:54 PM
Hi !

First, many thanks for this very usefull tool !

I was planning for tests with https://github.com/Kasmetski/auto-hard-reset for Pi GPIO until I found your project. I'm interested in testing your solution with Pi 3 if needed.
I'm looking after nicehash pool, minergate pools and cryptoknight.cc pools support if you still take feature requests. For this last pool, I'll try to look into the sources, I think it may be close to node-js/fairpool code.
Would be glad to contribute if I can, I really appreciate that you have opened your sources.

Again, thank you for your awesome Rig Monitor



Hey, thanks dude.

about pool support, could you create the respective feature requests on here: https://github.com/rodneymo/rig-monitorv2/issues (https://github.com/rodneymo/rig-monitorv2/issues)
Which one is highest prio for you?
I have plans to add raspberry GPIO to rig-monitor soon. That will probably be in version 2.4 (ETA 2 weeks).

cryptoknight.cc implementation is not based on cryptonote-api, which is the standard for nodejs pools. After some googling, I found and tested the network stats API: https://cryptoknight.cc/rpc/karbo/stats, but not the other ones.
If you can help me finding out the other apis then I can get it to the next 2.3 dev version. I need miner stats, worker stats (if available)
 and payments.


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 09, 2018, 07:58:23 PM
Hi !

First, many thanks for this very usefull tool !

I was planning for tests with https://github.com/Kasmetski/auto-hard-reset for Pi GPIO until I found your project. I'm interested in testing your solution with Pi 3 if needed.
I'm looking after nicehash pool, minergate pools and cryptoknight.cc pools support if you still take feature requests. For this last pool, I'll try to look into the sources, I think it may be close to node-js/fairpool code.
Would be glad to contribute if I can, I really appreciate that you have opened your sources.

Again, thank you for your awesome Rig Monitor



I spoke with the cryptoknight.cc discord mods and they provided me with a list of APIs. Could you send me the results of the APIs?
for the coming 6-7 days I am away from home so I can't setup my test server.
You can PM me the results on telegram @rodneymo

Pool Stats: https://cryptoknight.cc/rpc/ipbc/stats
Miner Stats: https://cryptoknight.cc/rpc/ipbc/stats_address?address=
Miner Payments: https://cryptoknight.cc/rpc/ipbc/get_payments?time=&address=
Miner Blocks: https://cryptoknight.cc/rpc/ipbc/get_userblocks?height=&address=
Pool Payments: https://cryptoknight.cc/rpc/ipbc/get_payments?time=
Pool Blocks: https://cryptoknight.cc/rpc/ipbc/get_blocks?height=


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: eXta on June 09, 2018, 09:04:52 PM
Of course,

I sent you the results.

https://cryptoknight.cc/rpc/ipbc/get_userblocks?height=&address= gave me an Invalid API call no matter what (recent) height I put.

Was searching about your code trying to contribute when I realised that only the v1 was open sourced :(

Been fooled by the generated "Source code" on github that contain only the README.


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 10, 2018, 03:24:52 PM
Of course,

I sent you the results.

https://cryptoknight.cc/rpc/ipbc/get_userblocks?height=&address= gave me an Invalid API call no matter what (recent) height I put.

Was searching about your code trying to contribute when I realised that only the v1 was open sourced :(

Been fooled by the generated "Source code" on github that contain only the README.

I already have an implementation but need to do some testing. I should release a dev version in the coming 1-2 days.

True about the open source, I am not really sure what to do about it, given my past experience with v1: a bunch of ppl forking the code but only 1 guy contributing. Anyways, I am still thinking about it and it's not set in stone.


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: starmax on June 11, 2018, 05:24:53 PM
Hey, I just set this up over the weekend.  Very cool software!!  I'm having some trouble with getting the TP-Link info.  I tried with 2.3.6d and 2.2.2 (installed Python 2.7.13 and set the PATH var), getting this in the log:

ERROR: 2018/06/11 11:33:48 tplink.go:139: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/06/11 11:33:48 tplink.go:28: TPlink script execution failed!

This is my rigList config for 1 of my TP-Link HS110 plugs:

"6xGTX1070,phoenixminer,label_nanopool,,http://192.168.5.8:3333,6,197,,tplink,192.168.5.80,850,70",


I don't know the cause of the exit is, or how to get more logging info.  Any help would be appreciated!


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 11, 2018, 05:29:04 PM
Hey, I just set this up over the weekend.  Very cool software!!  I'm having some trouble with getting the TP-Link info.  I tried with 2.3.6d and 2.2.2 (installed Python 2.7.13 and set the PATH var), getting this in the log:

ERROR: 2018/06/11 11:33:48 tplink.go:139: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/06/11 11:33:48 tplink.go:28: TPlink script execution failed!

This is my rigList config for 1 of my TP-Link HS110 plugs:

"6xGTX1070,phoenixminer,label_nanopool,,http://192.168.5.8:3333,6,197,,tplink,192.168.5.80,850,70",


I don't know the cause of the exit is, or how to get more logging info.  Any help would be appreciated!


Hi,

if you cd to grm's folder and run the following command then what is the output?

Code:
python ./external/tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}' 


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: starmax on June 11, 2018, 05:33:23 PM
Hi,

if you cd to grm's folder and run the following command then what is the output?

Code:
python ./external/tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}' 

Here it is (thank you!!!):

C:\Users\bryan\Mining\monitoring\grm-2.3.d.6-windows-amd64\external>python ./tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}'
Traceback (most recent call last):
  File "./tplink.py", line 57, in <module>
    args = parser.parse_args()
  File "C:\Program Files\Python27\lib\argparse.py", line 1701, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1733, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1939, in _parse_known_args
    start_index = consume_optional(start_index)
  File "C:\Program Files\Python27\lib\argparse.py", line 1879, in consume_optional
    take_action(action, args, option_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 1791, in take_action
    argument_values = self._get_values(action, argument_strings)
  File "C:\Program Files\Python27\lib\argparse.py", line 2231, in _get_values
    value = self._get_value(action, arg_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 2260, in _get_value
    result = type_func(arg_string)
  File "./tplink.py", line 10, in validIP
    socket.inet_pton(socket.AF_INET, ip)
AttributeError: 'module' object has no attribute 'inet_pton'


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 11, 2018, 05:41:38 PM
Hi,

if you cd to grm's folder and run the following command then what is the output?

Code:
python ./external/tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}' 

Here it is (thank you!!!):

C:\Users\bryan\Mining\monitoring\grm-2.3.d.6-windows-amd64\external>python ./tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}'
Traceback (most recent call last):
  File "./tplink.py", line 57, in <module>
    args = parser.parse_args()
  File "C:\Program Files\Python27\lib\argparse.py", line 1701, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1733, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1939, in _parse_known_args
    start_index = consume_optional(start_index)
  File "C:\Program Files\Python27\lib\argparse.py", line 1879, in consume_optional
    take_action(action, args, option_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 1791, in take_action
    argument_values = self._get_values(action, argument_strings)
  File "C:\Program Files\Python27\lib\argparse.py", line 2231, in _get_values
    value = self._get_value(action, arg_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 2260, in _get_value
    result = type_func(arg_string)
  File "./tplink.py", line 10, in validIP
    socket.inet_pton(socket.AF_INET, ip)
AttributeError: 'module' object has no attribute 'inet_pton'


Ok. This seems to be an issue with python's socket module. Check the last comment from this GitHub issue.:
https://github.com/mitsuhiko/python-geoip/issues/4 (https://github.com/mitsuhiko/python-geoip/issues/4)


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 11, 2018, 05:46:49 PM
Hi,

if you cd to grm's folder and run the following command then what is the output?

Code:
python ./external/tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}' 

Here it is (thank you!!!):

C:\Users\bryan\Mining\monitoring\grm-2.3.d.6-windows-amd64\external>python ./tplink.py -t "192.168.5.80" -j '{"emeter":{"get_realtime":{}}}'
Traceback (most recent call last):
  File "./tplink.py", line 57, in <module>
    args = parser.parse_args()
  File "C:\Program Files\Python27\lib\argparse.py", line 1701, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1733, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "C:\Program Files\Python27\lib\argparse.py", line 1939, in _parse_known_args
    start_index = consume_optional(start_index)
  File "C:\Program Files\Python27\lib\argparse.py", line 1879, in consume_optional
    take_action(action, args, option_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 1791, in take_action
    argument_values = self._get_values(action, argument_strings)
  File "C:\Program Files\Python27\lib\argparse.py", line 2231, in _get_values
    value = self._get_value(action, arg_string)
  File "C:\Program Files\Python27\lib\argparse.py", line 2260, in _get_value
    result = type_func(arg_string)
  File "./tplink.py", line 10, in validIP
    socket.inet_pton(socket.AF_INET, ip)
AttributeError: 'module' object has no attribute 'inet_pton'


Ok. This seems to be an issue with python's socket module. Check the last comment from this GitHub issue.:
https://github.com/mitsuhiko/python-geoip/issues/4 (https://github.com/mitsuhiko/python-geoip/issues/4)

Sorry something that escaped me. For the last step, you should actually replace
Code:
import socket

with

Code:
import win_inet_pton

in the tplink.py script


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: starmax on June 11, 2018, 06:10:01 PM

Sorry something that escaped me. For the last step, you should actually replace
Code:
import socket

with

Code:
import win_inet_pton

in the tplink.py script

I ended up needing to add
Code:
import win_inet_pton
, rather than replace
Code:
import socket
.  I needed to import both.  Thank you!!!


I know it's been requested before, but adding Nicehash monitoring would be huge for me.  Nicehash has been paying more for CryptonightV7 mining than straight XMR mining for a while now, so I keep mining there.

Thanks again!


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 12, 2018, 09:14:57 AM
Of course,

I sent you the results.

https://cryptoknight.cc/rpc/ipbc/get_userblocks?height=&address= gave me an Invalid API call no matter what (recent) height I put.

Was searching about your code trying to contribute when I realised that only the v1 was open sourced :(

Been fooled by the generated "Source code" on github that contain only the README.

I just published version 2.3.d.7, which includes cryptoknight pool support. Bear in mind the API data is very limited, basically: hr, paid, balance and payments.


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 13, 2018, 02:01:04 PM

version 2.3.0 has been released https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.0 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.0)

What's new?
Support for Bminer, includes dashboard template
Support for EWBF, includes dashboard template
Support for Ethminer, includes dashboard template
Support for suprnova pools
Support for cryptoknight pools
Ethminer fix to support 0.14 and earlier versions
Fixed grm crashes in rare occasions when claymore html output will not include GPU specs


Title: Re: free rig-monitor now supports Wemo plugs,FairPool,power reset triggers
Post by: rodney2250 on June 19, 2018, 05:25:53 PM

I have just released the 3.0.d.1 development version. This version includes the profitability dashboard as well as an updated Mining Overview Dashboard that requires no configuration.

https://www.rigmonitor.app/blog/wp-content/uploads/2018/06/Screen-Shot-2018-06-17-at-9.24.39-PM.png

https://www.rigmonitor.app/blog/wp-content/uploads/2018/06/Screen-Shot-2018-06-18-at-2.09.48-PM.png

You can get it here: https://github.com/rodneymo/rig-monitorv2/releases/tag/3.0.d.1 (https://github.com/rodneymo/rig-monitorv2/releases/tag/3.0.d.1)

And please make sure you read my blog post about it https://www.rigmonitor.app/blog/rig-monitor-3-0-preview/ (https://www.rigmonitor.app/blog/rig-monitor-3-0-preview/)


Title: Re: [New version]rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: starmax on June 19, 2018, 06:23:52 PM
Look cool, already downloaded it.  Do I need to do anything to migrate from 2.3?  Should I delete my existing Dashboards?

thanks for all your hard work!


Title: Re: [New version]rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on June 19, 2018, 06:57:35 PM
Look cool, already downloaded it.  Do I need to do anything to migrate from 2.3?  Should I delete my existing Dashboards?

thanks for all your hard work!

You can keep those  and use those dashboards and in that case you might need to adjust some queries. This is because, and has I mentioned in my blog post, from this version hashrates are always stored in H/s.

And flush the influx measurements:

Code:
drop measurement coin_data
drop measurement miner_gpu
drop measurement miner_system
drop measurement network_stats
drop measurement pool_payments
drop measurement pool_stats
drop measurement worker_stats
drop measurement env_data
drop measurement market_data
drop measurement pool_shares
drop measurement future_profit
drop measurement past_profit
 


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: starmax on June 20, 2018, 02:20:21 PM
Still on 2.3.0, running on MacOS X 10.9.

Been getting this error the last 2 days, causes GRM to crash

INFO: 2018/06/20 04:54:07 nanopool.go:170: networkBlocks query succeeded!
INFO: 2018/06/20 04:54:07 nanopool.go:175: Querying NANOPOOL minerPayments.
INFO: 2018/06/20 04:54:07 nanopool.go:183: minerPayments query succeeded!
ERROR: 2018/06/20 04:54:07 influxdb.go:60: DBDaemon could not write record batch to influxDB...
panic: runtime error: index out of range

goroutine 51 [running]:
go-rig-monitor/pool.(*PoolConfig).LoadNanopoolData(0xc420120cc0, 0x1559640, 0xc42024a180, 0xc420073da0)
   /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:339 +0x3794
go-rig-monitor/pool.Monitor(0xc4200224e0, 0x15, 0xc420024eb0, 0x7, 0xc420024f50, 0x7, 0xc420024ff0, 0x7, 0x1e, 0x3e8, ...)
   /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:61 +0x1a5
created by main.main
   /Users/ramf/go/src/go-rig-monitor/main.go:143 +0xb50
 


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on June 20, 2018, 05:40:30 PM

Still on 2.3.0, running on MacOS X 10.9.

Been getting this error the last 2 days, causes GRM to crash

INFO: 2018/06/20 04:54:07 nanopool.go:170: networkBlocks query succeeded!
INFO: 2018/06/20 04:54:07 nanopool.go:175: Querying NANOPOOL minerPayments.
INFO: 2018/06/20 04:54:07 nanopool.go:183: minerPayments query succeeded!
ERROR: 2018/06/20 04:54:07 influxdb.go:60: DBDaemon could not write record batch to influxDB...
panic: runtime error: index out of range

goroutine 51 [running]:
go-rig-monitor/pool.(*PoolConfig).LoadNanopoolData(0xc420120cc0, 0x1559640, 0xc42024a180, 0xc420073da0)
   /Users/ramf/go/src/go-rig-monitor/pool/nanopool.go:339 +0x3794
go-rig-monitor/pool.Monitor(0xc4200224e0, 0x15, 0xc420024eb0, 0x7, 0xc420024f50, 0x7, 0xc420024ff0, 0x7, 0x1e, 0x3e8, ...)
   /Users/ramf/go/src/go-rig-monitor/pool/pool-monitor.go:61 +0x1a5
created by main.main
   /Users/ramf/go/src/go-rig-monitor/main.go:143 +0xb50
 

please you run a trace and create a GitHub issue. to run a trace use: ./grm -t > trace .txt  2>&1 &


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: starmax on June 21, 2018, 02:26:31 PM
submitted a Github issue, thank you!


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on June 26, 2018, 09:00:53 AM
submitted a Github issue, thank you!

Posted a hotfix for both issues. See here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.1_hf_46_47 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.1_hf_46_47)


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: starmax on June 27, 2018, 12:38:54 PM
The hot fix is working great, thank you so much!!!!


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on June 27, 2018, 08:12:55 PM
The hot fix is working great, thank you so much!!!!

Great. I’ll issue a minor release tomorrow together with a an updated 3.0 (development) release.

Thanks for the fast turnaround.


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on June 28, 2018, 08:07:51 AM
submitted a Github issue, thank you!

Posted a hotfix for both issues. See here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.1_hf_46_47 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.1_hf_46_47)

Version 2.3.2 release with both fixes.

https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.2 (https://github.com/rodneymo/rig-monitorv2/releases/tag/2.3.2)


Title: Re: free rig-monitor now supports miner,EWBF, Ethminer,suprnova,cryptoknight
Post by: rodney2250 on July 03, 2018, 02:21:28 PM

Version 3.0 is out!

What's new in version 3.0:

  • Added historical and future profitability logic and charts
https://www.rigmonitor.app/blog/wp-content/uploads/2018/06/Screen-Shot-2018-06-17-at-9.24.39-PM.png
  • Single, consolidated mining dashboard with drop-down menu to select pool
  • Miner, Pool specific dashboard templates deprecated; will no longer be maintained
  • Added hashrate correction factor to pool definition in config file
  • Added pool label to all miner_gpu measurements
  • Harmonized basic influx schema for both miners and pools to facilitate reporting in case of multiple pool, miner combination scenarios
  • Claymore measurement for coin+dcoin modified. Now both coins are stored using same influx schema
  • Fixed issue with noplug power measurments not being stored after startup
  • Fixed issue with ethminer outbound/inbound stream termination


Download and instructions here: https://www.rigmonitor.app/blog/ (https://www.rigmonitor.app/blog/)

If you'd like other miners/pools/APIs to be supported then please submit a feature request on github.
For support please join the telegram group https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q (https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q)

Buy me a beer if you find this app useful
ETH: 0x0f2d4397CecB53883411cfe75882622c312c8340
MUSICOIN: 0x9a44a57041acd5f1511bf13a663d136ddbde1fb1


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: higgy on July 03, 2018, 03:21:01 PM
I am so psyched that I found this - it is so very cool!!  I came across this today strictly by accident and very excited to install/work on it this week.
This is perfect for me- I'm mining primarily eth with nanopool and phoenix miner (latest version of phoenix).

I like your latest dashboard regarding profitability... one question, can you provide profitability per rig?   and overall?

In one case, I have one rig owned by one person, and a second one owned by a different person, and two rigs owned by a third person.
Different rig names, but same pool (nanopool).

Ideally, I'd like to generate a report for each based on their rig's performance and profitability.
Including electricity usage and pool performance.

For this example here is the nanopool output for these 4 rigs.
https://eth.nanopool.org/account/0x83a866fb17839931d267bb6868ff7131b9a3f76b

Thanks for your hard work thus far!!!!!



Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 03, 2018, 03:41:16 PM
I am so psyched that I found this - it is so very cool!!  I came across this today strictly by accident and very excited to install/work on it this week.
This is perfect for me- I'm mining primarily eth with nanopool and phoenix miner (latest version of phoenix).

I like your latest dashboard regarding profitability... one question, can you provide profitability per rig?   and overall?

In one case, I have one rig owned by one person, and a second one owned by a different person, and two rigs owned by a third person.
Different rig names, but same pool (nanopool).

Ideally, I'd like to generate a report for each based on their rig's performance and profitability.
Including electricity usage and pool performance.

For this example here is the nanopool output for these 4 rigs.
https://eth.nanopool.org/account/0x83a866fb17839931d267bb6868ff7131b9a3f76b

Thanks for your hard work thus far!!!!!



hey,

glad you like it!

Are all those rigs mining to the same wallet or different wallets?


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 03, 2018, 03:55:09 PM
I am so psyched that I found this - it is so very cool!!  I came across this today strictly by accident and very excited to install/work on it this week.
This is perfect for me- I'm mining primarily eth with nanopool and phoenix miner (latest version of phoenix).

I like your latest dashboard regarding profitability... one question, can you provide profitability per rig?   and overall?

In one case, I have one rig owned by one person, and a second one owned by a different person, and two rigs owned by a third person.
Different rig names, but same pool (nanopool).

Ideally, I'd like to generate a report for each based on their rig's performance and profitability.
Including electricity usage and pool performance.

For this example here is the nanopool output for these 4 rigs.
https://eth.nanopool.org/account/0x83a866fb17839931d267bb6868ff7131b9a3f76b

Thanks for your hard work thus far!!!!!



hey,

glad you like it!

Are all those rigs mining to the same wallet or different wallets?

Never mind. I looked into your link and noticed you are using a single wallet, which in that case won't work, because the past profitability calculation uses the pool payments to calculate the daily revenue.

I can look into it, but how would you split single wallet payments across the different rigs?


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: higgy on July 03, 2018, 05:43:54 PM
I am so psyched that I found this - it is so very cool!!  I came across this today strictly by accident and very excited to install/work on it this week.
This is perfect for me- I'm mining primarily eth with nanopool and phoenix miner (latest version of phoenix).

I like your latest dashboard regarding profitability... one question, can you provide profitability per rig?   and overall?

In one case, I have one rig owned by one person, and a second one owned by a different person, and two rigs owned by a third person.
Different rig names, but same pool (nanopool).

Ideally, I'd like to generate a report for each based on their rig's performance and profitability.
Including electricity usage and pool performance.

For this example here is the nanopool output for these 4 rigs.
https://eth.nanopool.org/account/0x83a866fb17839931d267bb6868ff7131b9a3f76b

Thanks for your hard work thus far!!!!!



hey,

glad you like it!

Are all those rigs mining to the same wallet or different wallets?

Never mind. I looked into your link and noticed you are using a single wallet, which in that case won't work, because the past profitability calculation uses the pool payments to calculate the daily revenue.

I can look into it, but how would you split single wallet payments across the different rigs?

Well, that' a good question.
Maybe as part of the dashboard have the ability to select 1 or more of the "workers" and logically join them to be one "customer" as such.  Then calculate based on worker stats and provide a chart/report?    We have all the individual data for each worker already, no?

Thx, H


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 04, 2018, 12:08:44 PM
I am so psyched that I found this - it is so very cool!!  I came across this today strictly by accident and very excited to install/work on it this week.
This is perfect for me- I'm mining primarily eth with nanopool and phoenix miner (latest version of phoenix).

I like your latest dashboard regarding profitability... one question, can you provide profitability per rig?   and overall?

In one case, I have one rig owned by one person, and a second one owned by a different person, and two rigs owned by a third person.
Different rig names, but same pool (nanopool).

Ideally, I'd like to generate a report for each based on their rig's performance and profitability.
Including electricity usage and pool performance.

For this example here is the nanopool output for these 4 rigs.
https://eth.nanopool.org/account/0x83a866fb17839931d267bb6868ff7131b9a3f76b

Thanks for your hard work thus far!!!!!



hey,

glad you like it!

Are all those rigs mining to the same wallet or different wallets?

Never mind. I looked into your link and noticed you are using a single wallet, which in that case won't work, because the past profitability calculation uses the pool payments to calculate the daily revenue.

I can look into it, but how would you split single wallet payments across the different rigs?

Well, that' a good question.
Maybe as part of the dashboard have the ability to select 1 or more of the "workers" and logically join them to be one "customer" as such.  Then calculate based on worker stats and provide a chart/report?    We have all the individual data for each worker already, no?

Thx, H

Ok. there are 2 ways you can ratio the revenue, based on worker shares/total_shares_for_all_workers or similar for avg_worker_hashrate/total_hashrate. I think shares is probably more fair as it will factor in situations when a specific rig is down, which is something that avg hashrate calculations would not consider.
I will create a custom chart for you, but I don't think I will add it to the dashboard at this point.


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 05, 2018, 10:29:42 AM


 have just released a development version (3.1.d.1) , which includes multiple fixes, particularly on the past profitability calculation.
You can get it here: https://www.rigmonitor.app/blog/downloads/ (https://www.rigmonitor.app/blog/downloads/)

3.1.d.1 (development)
---------------------------------------------------------------------
-Added check for number of rigList and poolList configuration items
-Updated whattomine url to use https
-Fixed issue (#54) with "INVALID SHARES REPORTED BY RIG" not starting at 0
-Fixed issue (#53) with "VALID SHARES REPORTED BY RIG" not honoring selected pool
-Fixed issue with time/day boundaries used in past profitabily calculation
-Fixed issue with TLS/SSL errors when connecting to whattomine.com


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: evlo on July 24, 2018, 08:36:29 AM
Hi,

firt of awesome work :)

I just started with it and it looks really good, my goal is to have rpi run monitoring SW and display dashboard at the same time.
So far I think my pi is configured as headless, so I need to figure all the stuff out, but I also have few struggles as I'm new to grafana:

I have currently two pools ETH pool addresses configured and will have 3 when i'm done - sometimes I want to display it separate and sometimes not :)

1. rig hashrate v pool hasharte:
I get pool hashrate only every 10 minutes so my chart is not very nice, but missing bars/line - how should i fix this
https://i.imgur.com/4gTWpGI.png
UPDATE: This one solved 1m for rigs, 10m for pools, no bars


2. Same thing with pool reported hashrate - it jums from value to zero between each chart value
(this one i will make individual line for each pool for valid and invalid in the end)
https://i.imgur.com/OU1DBqZ.png
UPDATE: This one solved itself when I switched to 4 line - 2 for each pool

Can someone more skilled help me?

I also did not figured out how to make profitability work, but that is last thing on the list.

Feature request:
1. custom power consumption scripts - ie. so we can write our own python scripts to get power consumption from sonoff devices (or maybe in the future even revogi ones that use https and internet for everything)
2. multipe currency - ie. switch between sek/eur/usd - but i'm not sure how to even implement it reasonably, for me it would be more then enough if market cap and rate data in influxDB could be gathered in multiple currencies so I could have power consumption and profitability in sek a watch market in eur and usd

#       script - use external script for power management. Obviously power monitoring will be disabled. You can read more about it here: https://www.rigmonitor.app/blog/using-rig-monitors-power-management-feature/
I did not try it, but maybe it would work if I implement command info and return json in tp-link format?


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 24, 2018, 03:31:54 PM
Hi,

firt of awesome work :)

I just started with it and it looks really good, my goal is to have rpi run monitoring SW and display dashboard at the same time.
So far I think my pi is configured as headless, so I need to figure all the stuff out, but I also have few struggles as I'm new to grafana:

I have currently two pools ETH pool addresses configured and will have 3 when i'm done - sometimes I want to display it separate and sometimes not :)

1. rig hashrate v pool hasharte:
I get pool hashrate only every 10 minutes so my chart is not very nice, but missing bars/line - how should i fix this
https://i.imgur.com/4gTWpGI.png
UPDATE: This one solved 1m for rigs, 10m for pools, no bars


2. Same thing with pool reported hashrate - it jums from value to zero between each chart value
(this one i will make individual line for each pool for valid and invalid in the end)
https://i.imgur.com/OU1DBqZ.png
UPDATE: This one solved itself when I switched to 4 line - 2 for each pool

Can someone more skilled help me?

I also did not figured out how to make profitability work, but that is last thing on the list.

Feature request:
1. custom power consumption scripts - ie. so we can write our own python scripts to get power consumption from sonoff devices (or maybe in the future even revogi ones that use https and internet for everything)
2. multipe currency - ie. switch between sek/eur/usd - but i'm not sure how to even implement it reasonably, for me it would be more then enough if market cap and rate data in influxDB could be gathered in multiple currencies so I could have power consumption and profitability in sek a watch market in eur and usd

#       script - use external script for power management. Obviously power monitoring will be disabled. You can read more about it here: https://www.rigmonitor.app/blog/using-rig-monitors-power-management-feature/
I did not try it, but maybe it would work if I implement command info and return json in tp-link format?

which version are you using?


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: evlo on July 24, 2018, 07:27:28 PM
I'm currently on 3.1 dev - I already figured a lot of stuff I had issues with.

Now my nice to have list:
Multiple fiat currencies for power consumption, profitability and "quote and marketcap" - I have no idea how to implement this and probably I'm only one who cares
Track different currency pairs and market cap - but I guess i can add different dataset for this, i'm really new to grafana

My feature reqest:
custom power monitoring python scripts "api"

Ad profitability (at least profitability history):
It is still not showing anything for me - I messed up and changed wallets on pool labels, so I have wrong stats. I guess profitability starts showing after payment from pool? In my case it can take up to 30 hours.
Maybe I should somehow purge influxDB?
UPDATE:
I now get one profitability history record for today for one pool, so that is Nice, but power cost is not calculated.
Also I noticed that for rig reported vs pool hashrate I can't do filter by pool to get rig hashrates, but I need to filter by rigs - so that may be related?
sorry can't post example, bitcointalk blocks the post
UPDATE2:

It was me being stupid
#RIG_ID, MINER, PRIMARY_POOL_LABEL,
I put rig label in config instead of PRIMARY_POOL_LABEL (so I have rig label and rig id kinda duplicate and I even wonder why you would do that :) )

I think my setup is kinda weird because I have multiple rigs on different ethermine wallets (different pools in in config).


But really great work as it just works.


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on July 25, 2018, 05:49:49 AM
I'm currently on 3.1 dev - I already figured a lot of stuff I had issues with.

Now my nice to have list:
Multiple fiat currencies for power consumption, profitability and "quote and marketcap" - I have no idea how to implement this and probably I'm only one who cares
Track different currency pairs and market cap - but I guess i can add different dataset for this, i'm really new to grafana

My feature reqest:
custom power monitoring python scripts "api"

Ad profitability (at least profitability history):
It is still not showing anything for me - I messed up and changed wallets on pool labels, so I have wrong stats. I guess profitability starts showing after payment from pool? In my case it can take up to 30 hours.
Maybe I should somehow purge influxDB?
UPDATE:
I now get one profitability history record for today for one pool, so that is Nice, but power cost is not calculated.
Also I noticed that for rig reported vs pool hashrate I can't do filter by pool to get rig hashrates, but I need to filter by rigs - so that may be related?
sorry can't post example, bitcointalk blocks the post
UPDATE2:

It was me being stupid
#RIG_ID, MINER, PRIMARY_POOL_LABEL,
I put rig label in config instead of PRIMARY_POOL_LABEL (so I have rig label and rig id kinda duplicate and I even wonder why you would do that :) )

I think my setup is kinda weird because I have multiple rigs on different ethermine wallets (different pools in in config).


But really great work as it just works.

Well done mate! I appreciate you putting the time to fix it instead of simply asking for help ;-)

So AFAIU you have no operational issues, just a couple of feature requests:

1) Custom power monitoring. Yeah, I have the sonoff request pending for a couple of months. I don't have such a plug, but if you provide me with an example API calls I'll implement it (and you test it for me)

2) Multiple fiat currencies for power consumption, profitability and "quote and marketcap" - Can you elaborate on your use-case? Why do you need this? For cloud service?

3) Track different currency pairs and market cap - So that you can adjust the market, profitability per geography instead of being limited by the pool definition?



Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: evlo on July 26, 2018, 07:58:39 PM
I'm doing some research on sonoff today, POW R2s.
Official api trough cloud seems doable, but too much work http://iotgo.iteadstudio.com/api

There is tool to upload unofficial firmware, that supports MQTT, which should be easier to interface, and probably has json API - I will research further how this works.
Unfortunatelly POW R2 is not possible to upload unofficial firmware over the air, but all other sonoffs are (but does not power, so meh). Anyway I was able to upload firmware in supper ghetto way, but no soldering required, and now i'm researching this alternative firmware for easy to implement API.
https://i.imgur.com/4qWwHw2.jpg

This looked interresting thought as you already support wemo, but it is only for alexa :(
https://i.imgur.com/tQXFRDE.png


Web "API"
http://192.168.500.400/cm?cmnd=Power%20On
returns json
Code:
{"POWER":"ON"}

/cm?cmnd=Power%20Off
Code:
{"POWER":"OFF"}

/cm?cmnd=Power%20TOGGLE
Code:
{"POWER":"OFF"}
Code:
{"POWER":"ON"}
that is state after toggle

/cm?cmnd=Status%208
Code:
{"StatusSNS":{"Time":"2018-07-26T22:34:08","ENERGY":{"Total":0.000,"Yesterday":0.000,"Today":0.000,"Power":10,"Factor":0.52,"Voltage":236,"Current":0.083}}}
So I guess it is 10W?

/cm?cmnd=status
Code:
{"Status":{"Module":43,"FriendlyName":["Sonoff"],"Topic":"sonoff","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0}}
"Power":1=On
"Power":0=Off


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: evlo on July 30, 2018, 07:37:47 PM
So I tried to modify tplink.py to return
Code:
{"emeter":{"get_realtime":{"current":%c%,"voltage":%v%,"power":%p%,"total":0,"err_code":0}}}
For sonoffs, Obviously with replaced tokens, but I guess you don't really call tplink.py from your script, but handle everyhting internally or maybe you do call some commands before
Code:
{"emeter":{"get_realtime":{}}}
which I also should fake output ? I'm to lazy to sniff the traffic right now :)


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 06, 2018, 01:24:48 PM
So I tried to modify tplink.py to return
Code:
{"emeter":{"get_realtime":{"current":%c%,"voltage":%v%,"power":%p%,"total":0,"err_code":0}}}
For sonoffs, Obviously with replaced tokens, but I guess you don't really call tplink.py from your script, but handle everyhting internally or maybe you do call some commands before
Code:
{"emeter":{"get_realtime":{}}}
which I also should fake output ? I'm to lazy to sniff the traffic right now :)

Hey, I'll pick this up this week


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 11, 2018, 07:28:43 AM
So I tried to modify tplink.py to return
Code:
{"emeter":{"get_realtime":{"current":%c%,"voltage":%v%,"power":%p%,"total":0,"err_code":0}}}
For sonoffs, Obviously with replaced tokens, but I guess you don't really call tplink.py from your script, but handle everyhting internally or maybe you do call some commands before
Code:
{"emeter":{"get_realtime":{}}}
which I also should fake output ? I'm to lazy to sniff the traffic right now :)

I looked into the official API and I can easily use it, but then I found this https://blog.ipsumdomus.com/sonoff-switch-complete-hack-without-firmware-upgrade-1b2d6632c01 (https://blog.ipsumdomus.com/sonoff-switch-complete-hack-without-firmware-upgrade-1b2d6632c01), which seems even easier. Coming week I'll give it a go


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 11, 2018, 09:16:48 AM

Version 3.1 released. You can download it here: https://www.rigmonitor.app/blog/downloads/ (https://www.rigmonitor.app/blog/downloads/)

3.1
---------------------------------------------------------------------
-Added check for number of rigList and poolList configuration items
-Updated whattomine url to use https
-Support for payment correction factor for pools that report payments in currency subunits
-Fixed issue (#54) with "INVALID SHARES REPORTED BY RIG" not starting at 0
-Fixed issue (#53) with "VALID SHARES REPORTED BY RIG" not honoring selected pool
-Fixed issue with time/day boundaries used in past profitabily calculation
-Fixed issue with TLS/SSL errors when connecting to whattomine.com


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 15, 2018, 08:02:49 AM
So I tried to modify tplink.py to return
Code:
{"emeter":{"get_realtime":{"current":%c%,"voltage":%v%,"power":%p%,"total":0,"err_code":0}}}
For sonoffs, Obviously with replaced tokens, but I guess you don't really call tplink.py from your script, but handle everyhting internally or maybe you do call some commands before
Code:
{"emeter":{"get_realtime":{}}}
which I also should fake output ? I'm to lazy to sniff the traffic right now :)

I ended up ordering a plug. It's hard to develop and test without one. I should get it today so tomorrow I'll start development.


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 22, 2018, 06:54:44 PM

Hi all,

version 3.2.d.2 (development) has just been published.
What's new:
-Support for XMRig (tested with 2.7.1-beta)
-Support for Yiimp API (and extended API e.g. Unimining)
-Support for cgminer
-Telegram notifications support to grm. Power Rule Manager will send notifications to telegram every time a rig is rebooted.
-Extended support for reloading configuration params during runtime. All params, except telegram, are updated during runtime.
-Major code refactoring to reduce executable size and memory footprint
-Fixed profit calculation errors by adding retying strategy to whattomine.com connections
-Fixed issue with xmr-stak not recording gpu hashrate to "hr" field in miner_gpu table

Download it here: https://www.rigmonitor.app/blog/downloads/


Title: Re: [New version] rig-monitor now includes profitability charts, single dashboard
Post by: rodney2250 on August 28, 2018, 07:06:58 AM

Hi everyone,

version 3.2 of rig-monitor is out. What's new:

-Support for XMRig (tested with 2.7.1-beta)
-Support for Yiimp API (and extended API e.g. Unimining)
-Support for cgminer
-Telegram notifications support to grm. Power Rule Manager will send notifications to telegram every time a rig is rebooted.
-Extended support for reloading configuration params during runtime. All params, except telegram, are updated during runtime.
-Major code refactoring to reduce executable size and memory footprint
-Fixed profit calculation errors by adding retying strategy to whattomine.com connections
-Fixed issue with xmr-stak not recording gpu hashrate to "hr" field in miner_gpu table
-Fixed issue with Dynu DNS updater only updating once during runtime

Download it here: https://www.rigmonitor.app/blog/downloads/ (https://www.rigmonitor.app/blog/downloads/)


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: GKumaran on September 03, 2018, 04:26:41 PM
@rodney2250 Great project bro!!

But your blog has instruction for earlier versions. I'm having difficulties setting up the latest version. This is my first try and disclaimer: Im a complete noob.

This is what im getting :
INFO: 2018/09/03 21:51:10 config.go:65: Reading configuration file...
ERROR: 2018/09/03 21:51:10 config.go:74: Couldn't load config: While parsing config: invalid base

grafana and influxdb are up and running.


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 03, 2018, 04:57:43 PM
@rodney2250 Great project bro!!

But your blog has instruction for earlier versions. I'm having difficulties setting up the latest version. This is my first try and disclaimer: Im a complete noob.

This is what im getting :
INFO: 2018/09/03 21:51:10 config.go:65: Reading configuration file...
ERROR: 2018/09/03 21:51:10 config.go:74: Couldn't load config: While parsing config: invalid base

grafana and influxdb are up and running.

Glad you like it.

The latest instructions can be found here: https://www.rigmonitor.app/blog/installing-rig-monitor/ (https://www.rigmonitor.app/blog/installing-rig-monitor/)

wrt the error, config files should go in the conf folder. if you want to specify a different config file name (config.toml is the default) then you'd use it like this: grm -config my config.toml

If you need more support then I suggest to join our telegram group: https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q (https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Q)


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 04, 2018, 07:00:05 AM
Ok! I'll telegram!

BTW there was a typo on my first reply to you. It should have been:

grm -config my_config.toml


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: hellsnake on September 04, 2018, 07:23:28 AM
Hi.hero!
i need you help!

 I am going to run  it  in UBUNTU 18.04

but i cant run grm  In last step  .

snake@snake-VirtualBox:~/grm-3.2$ ./grm -config  config.toml
INFO: 2018/09/04 15:03:50 main.go:32: Starting rig-monitor version 3.2 ...
INFO: 2018/09/04 15:03:50 main.go:48: Commmand line arguments: -config config.toml
INFO: 2018/09/04 15:03:50 main.go:62: Config file specified. Using config.toml file.
INFO: 2018/09/04 15:03:50 config.go:65: Reading configuration file...
ERROR: 2018/09/04 15:03:50 config.go:74: Couldn't load config: While parsing config: invalid base

plz help me to run it . thx!


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 04, 2018, 07:56:12 AM
Hi.hero!
i need you help!

 I am going to run  it  in UBUNTU 18.04

but i cant run grm  In last step  .

snake@snake-VirtualBox:~/grm-3.2$ ./grm -config  config.toml
INFO: 2018/09/04 15:03:50 main.go:32: Starting rig-monitor version 3.2 ...
INFO: 2018/09/04 15:03:50 main.go:48: Commmand line arguments: -config config.toml
INFO: 2018/09/04 15:03:50 main.go:62: Config file specified. Using config.toml file.
INFO: 2018/09/04 15:03:50 config.go:65: Reading configuration file...
ERROR: 2018/09/04 15:03:50 config.go:74: Couldn't load config: While parsing config: invalid base

plz help me to run it . thx!

Hi,

there's a typo on the default config file. Under the telegram section the chatID should be
chatID = 43592

and not

chatID = 043592

even if you do not use it, you should remove the leading 0. That's what's causing grm to crash.

Let me know


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 04, 2018, 07:56:47 AM
Ok! I'll telegram!

I found what your issue is. See my previous reply.


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: GKumaran on September 04, 2018, 09:34:35 AM
Thx man looks beautiful !!

p.s: also had to remove the last "," from pool and rig setting, cheers


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: GKumaran on September 04, 2018, 12:29:57 PM
Sry ive reached the PM limit so posting here:

Code:
> select fan, temp from miner_gpu where miner='SRBMINER' order by time desc limit 10
name: miner_gpu
time                fan  temp
----                ---  ----
1536063923000000000 4200 63
1536063923000000000 4132 61
1536063923000000000 4202 63
1536063923000000000 4138 64
1536063923000000000 4219 66
1536063923000000000 4083 61
1536063862000000000 4219 65
1536063862000000000 4078 63
1536063862000000000 4202 63
1536063862000000000 4203 64
These are for 6 cards

WRT pool :  "supportxmr,nodejs-pool,xmr,https://www.supportxmr.com,


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 05, 2018, 06:12:16 AM
Sry ive reached the PM limit so posting here:

Code:
> select fan, temp from miner_gpu where miner='SRBMINER' order by time desc limit 10
name: miner_gpu
time                fan  temp
----                ---  ----
1536063923000000000 4200 63
1536063923000000000 4132 61
1536063923000000000 4202 63
1536063923000000000 4138 64
1536063923000000000 4219 66
1536063923000000000 4083 61
1536063862000000000 4219 65
1536063862000000000 4078 63
1536063862000000000 4202 63
1536063862000000000 4203 64
These are for 6 cards

WRT pool :  "supportxmr,nodejs-pool,xmr,https://www.supportxmr.com,

I am running this though my simulator. In the meantime please join our telegram group as it's easier to help you.


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on September 05, 2018, 06:29:00 AM


Version 3.2.2 released. What's new?
---------------------------------------------------------------------
-Fixed issue with SRBMINER and XMRRIG-PROXY not showing gpu data on dashboard.


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: xsoft on November 06, 2018, 07:47:33 PM
Hello,
any tips or support for EthOS?

Their panel is already gathering all kind of info (hostname, ip, uptime, temp., free space, load, ram, hashrate, vlt/mem/core, est. watts consume ..) at JSON format.
See example:

http://virosa.ethosdistro.com/
http://virosa.ethosdistro.com/?json=yes


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: eXta on November 11, 2018, 12:24:44 PM
Hello,
any tips or support for EthOS?

Their panel is already gathering all kind of info (hostname, ip, uptime, temp., free space, load, ram, hashrate, vlt/mem/core, est. watts consume ..) at JSON format.
See example:

http://virosa.ethosdistro.com/
http://virosa.ethosdistro.com/?json=yes

I saw on telegram that he is short on time and planning to open sources, I think you will have to wait the sources.

Rodney, you prefer BTC or Eth for donation ? I want to thank you for opening the code


Title: Re: [NEW] rig-monitor 3.2 now incl. support cgminer, Xmrig, Yiimp and Revive devices
Post by: rodney2250 on June 28, 2019, 07:46:26 PM
After almost 1 year hiatus I am resuming the development of rig-monitor.

I have not done any extensive testing yet, but I notice the coinmarketcap API has changed so the profitability and market data are not working.

Anything else not working, miners, pools, etc....?



Title: Re: [NEW] rig-monitor 4.0 (alpha released)
Post by: rodney2250 on January 20, 2020, 08:23:33 PM
After a long wait, I finally release rig-monitor 4.0

What's new in version 4.0 (alpha):

Updated market monitor module to use update coinmarketcap.com API
Refactored code base to make it simpler to extend/add new miners/pools/smartplugs