|
version 2.0 has been released. Details on 1st post
|
|
|
|
rig-monitor is a free monitoring tool for rigs and pools. v2.0 is a complete re-write in Golang. You can read the reasons for the re-write http://randomcryptostuff.blogspot.nl/2018/04/rig-monitor-re-write-in-golang.html. Feature overview of v2.0 release: - NEW: single executable for monitoring pools, rigs, power and market data with support for logging, tracing
- NEW: custom config file replaced with toml-based config file
- ability to pool hundreds of rigs and dozens of pools simultaneously
- NEW: configurable polling times
- miner support
- claymore single/dual-mining (tested v11.6)
- NEW: xmr-stak (tested v2.4.2)
- NEW: sgminer (tested v5.5.5)
- pool support
- nanopool (all coins)
- ethermine (all coins)
- mpos based pools e.g. miningpoolhub.com (all coins)
- NEW: nodejs-pool based pools e.g. hashvaultpro.com (all coins)
- power monitoring using smartplugs
- Market data monitoring
- Coinmarketcap.com
- whattomine.com
- Data storage using influxDB
- NEW: Cross-platform support
- raspberry Pi 1 Model B/ARMv6
- raspberry Pi 2/3/ARMv7
- linux/x86-64
- macOS/x86-64
- windows/i386
- windows/x86-64
- Dashboard templates includes:
- Claymore miner
- Xmr-Stak miner
- Sgminer
- Power Usage (TPLink HS110 smartplug)
- Ethermine Pool
- Nanopool
- Mpos-based pools
- Node-js based pools
- Notifications via Telegram
Get it here: https://github.com/rodneymo/rig-monitorv2Installation instructions here: https://randomcryptostuff.blogspot.comIf you'd like other miners/pools/APIs to be supported then please create an issue on github Mining dashboard example  Buy me a beer if you find this useful ETH: 0x0f2d4397CecB53883411cfe75882622c312c8340 MUSICOIN: 0x9a44a57041acd5f1511bf13a663d136ddbde1fb1 |
|
|
|
Hi, Are you woking with the forked version of Wishbone1138 ? https://github.com/wishbone1138/rig-monitor2 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) |
|
|
|
|
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
|
|
|
|
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? |
|
|
|
|
Question for the dev team and their cronies. When are you guys updating your roadmap w/ realistic, updated milestones? I have been reading through the whole thread and is seems that, aside from the "launch", you have been missing all milestones
|
|
|
|
Sorry for the late reply 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. Sure. 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 |
|
|
|
Check out our low-latency ethereum pool: http://xeminer.net/Zero pool and payout fees. Current pool hashrate is 367 Gh/s. Online support available. |
|
|
|
Check out our low-latency ethereum pool: http://xeminer.net/Zero pool and payout fees. Current pool hashrate is 300 Gh/s. Online support available. |
|
|
|
|
Hey all,
I am planning to develop pool software for ethereum (and forks). I have installed linux, geth on an old PC and created a private chain.
In order to develop and test I need a CPU miner (not the geth miner ) so that it connects to my ethereum node via stratum.
I understood ethminer used to have CPU support, but I cannot find any old version in github.
Anyone has a link where I can download an old version of ethminer (linux) which has support for CPU mining (-C flag)?
Thanks
|
|
|
|
|
Hey all,
I am planning to develop pool software for ethereal (and forks). I have installed linux, geth on an old PC and created a private chain.
In order to develop and test I need a CPU miner (not the geth miner ) so that it connects to my ethereum node via stratum.
I understood ethminer used to have CPU support, but I cannot find any old version in github.
Anyone has a link where I can download an old version of ethminer (linux) which has support for CPU mining (-C flag)?
Thanks
|
|
|
|
Check out our low-latency ethereum pool: http://xeminer.net/No pool nor payout fees. Current pool hashrate is 11 Gh/s. Online support available. |
|
|
|
|
You need to replace <mysql root password> with the password
|
|
|
|
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 |
|
|
|
hey all I just set up my musicoin pool and have both gmc (geth's equivalent) and pool software up and running: -gmc synched and up and running -pool connected to gmc node and collecting stats -website up and running However, when I try to connect one of my (claymore) miners I get a socket time out. On the pool server logs I see this message: "Unknown request method mining.subscribe" Any ideas how to fix it? One other question, do I need to run the gmc/geth client with the base account unlocked (I am no processing payments yet)? Thanks UPDATE: I fixed it by changing the stratum server mode in claymore to -esm 0 |
|
|
|
Quote
Did you create address Wallet?
No i read instruction only on 70% . I don't know where insert adress wallet. which wallet?
Im just testing correctly work program and server or not.
This is normal activity of program?
If i do last steps - Json problem gone?
It's really very HARD for me. you need to run in order to create an account/wallet |
|
|
|
Ok. I think rejected and incorrect shares are different. Look at the example below (Claymore 9.  : GPU #0: Ellesmere, 4096 MB available, 36 compute units
GPU #1: Ellesmere, 4096 MB available, 36 compute units
GPU #2: Ellesmere, 4096 MB available, 36 compute units
GPU #3: Ellesmere, 4096 MB available, 32 compute units
GPU #4: Ellesmere, 8192 MB available, 32 compute units
GPU #5: Ellesmere, 8192 MB available, 32 compute units
ETH - Total Speed: 162.347 Mh/s, Total Shares: 13023(2222+2204+2132+2168+2187+2227), Rejected: 0, Time: 100:05
ETH: GPU0 27.513 Mh/s, GPU1 27.380 Mh/s, GPU2 26.206 Mh/s, GPU3 27.200 Mh/s, GPU4 27.025 Mh/s, GPU5 27.024 Mh/s
Incorrect ETH shares: GPU0 25, GPU1 76, GPU2 10
1 minute average ETH total speed: 162.193 Mh/s
Pool switches: ETH - 0, DCR - 0
Current ETH share target: 0x00000000ffb34c02 (diff: 4300MH), epoch 34(1.27GB)
GPU0 t=73C fan=60%, GPU1 t=73C fan=50%, GPU2 t=72C fan=40%, GPU3 t=74C fan=49%, GPU4 t=69C fan=37%, GPU5 t=69C fan=38%
zero (0) rejected shares, but multiple incorrect shares: GPU0 25, GPU1 76, GPU2 10 Any ideas? |
|
|
|
Total Shares: the sum count of all shares found by your GPUs since the last time you started Claymore.
Rejected share: share that you computed and sent to your mining pool, but which the mining pool rejected as not being correct. This might point to memory on your GPU being corrupted, perhaps because of overheating or because of an OC that is too high. If the memory is not faulty, a restart can clear it up, if it doesn't get driven too hard again.
Stale share: a share that you found and sent to the pool and was confirmed as correct, but which arrived too late; you sent a share when the pool had already moved on to a new block. This may point to a slow network connection, or perhaps your system is overtaxed and is unable to move your GPUs to the new work quickly enough when new work comes in. Everyone will have some small portion of stale shares, unless their miners are pretty much directly connected to the pool's servers and can get new work notices with almost no delay (which is pretty much impossible, unless you're running the pool servers and install the miners next to them.) If your pool provides multiple addresses, ping them and see which is "closest" to you (has the shortest time delay) and make sure you work with that address. Thanks. What about incorrect share (as reported by claymore's miner)? |
|
|
|
|
Show Posts
