Eligius is working just fine for me FWIW.
Even to the extent that I can cleanly use the stats for testing.
Maybe it's hardware specific? I'm using Ants... two S2s and one S1s, going through a stratum proxy. M |
|
|
|
My worker just went idle again.  M EDIT: Just saw my proxy was showing every hash submission as rejected again. |
|
|
|
I to have several s2 miners drop off for some reason seems like the past several days this has been happening.
Not sure why.
I was thinking of a DDOS attack for a Internet traffic or routing issue between me and eligius.
I'm getting a fraction of the proper hash speed. Yet nothing looks wrong. Is that mitm thing going on again? M EDIT: to clarify, all 2.2 TH/s is going through a proxy to eligius. It was showing difficulty of 128, and not acting like there was 2.2 TH/s going there, ie, not pages of hashes between restarts. Yet the miners reported proper speeds, and stats showed me running at 1/20th my normal speed. I just restarted the proxy, things look normal again. |
|
|
|
hey mdude, just some feedback.
I now have the monitor open with 1 second refresh as a live view of hash and error/reject rates. the api makes this possible.
thanks for adding that in and thanks for the updates.
Great!  M |
|
|
|
Thanks for the program. I have been using it to monitor a bunch of S1's. I still end up using another program along with this one as it has the ability to show/change the current pool the miner is on.
I have found one thing in the sorting of columns that could use some code adjustment.
First off, I have three S1's that have some problems that alerted me to the sorting issue.
I have one S1 that has a bad temp sensor so it always shows it at 177 degrees celsius. This temp is erroneous but what I found is that with the leading "1" in the 177, it is sorted as the first temp, with the second temp listed at 43 and on up to 50. So, on my display, I see the following when the temp field is sorted "lowest-highest";
177
43
43
44
45
50
The same sorting error happens in the hashing field. I have two S1's that like to slow down their hash and when they get under "100", they are sorted at the end of the list in the "highest" spot. You can test this yourself by removing power to the blade opposite of the controller board on a S1. This will keep the miner running with only one blade hashing so it will show about "90GH/s". Instead of this sorting as the lowest number, it will be listed as the highest number.
Thanks for the program.
Thanks for the info. That's because the data is stored as text, not a number. I'll change that so you can sort properly. M |
|
|
|
Something up with the pool? My stratum proxy is going beserk. I think they are connecting normally directly..
M
Mine has been doing the same but I thought it was on my end because my internet lost connection for a few minutes. I'm getting a ridiculous amount of rejects. M |
|
|
|
|
Something up with the pool? My stratum proxy is going beserk. I think they are connecting normally directly..
M
|
|
|
|
I already told you to do all that stuff a month or two ago, if it's the same project we're talking about, heh.. It won't have any impact on memory usage really, but you only need 2 connections on your bitcoind.
Using your settings I had virtually zero transactions. That's why I asked... M |
|
|
|
For miner who are active with many miners, pools, rental that feature is great.
Now I'm visiting the 192.168.x.xx many times a day just to see pools and change.
Got it. I'll see what I can do. M |
|
|
|
Thanks for the example. However, I'm confused why you'd want to see that? None of that data changes from the time you set it, aside from whether the pool is up or down. And pool status already shows (UUU). M |
|
|
|
Excellent. Can you add a feature to see all the three pools?
In which regard? What exactly are you looking for? That's a lot of data to try to show on the grid. M The list of 3 pools we can now see in the Ant Status page need to be bring somewhere in MAntMonitor. May be as a popup on mouse over to the row or like that. Just the pool names? What stats exactly are you looking for? M |
|
|
|
|
I updated the front end to my p2pool node to use Norgan's code. Looks good, thank you Norgan!
M
|
|
|
|
Excellent. Can you add a feature to see all the three pools?
In which regard? What exactly are you looking for? That's a lot of data to try to show on the grid. M |
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? Its not p2pool issue, use ssd disk and should be able to put blockprioritysize=0 #blockminsize=2000 blockmaxsize=1000000 mintxfee=0.00001 minrelaytxfee=0.00001 With just 0.2s, with merged mining namecoin, fusioncoin, ixcoin and devcoin I don't have control over the disk being used, as I'm using a VPS. My maxconn is at 50, though, maybe that's my issue. I'll tweak it and see what happens. Thanks! M |
|
|
|
It just gets better and better...
thanks...
sent another token of appreciation...
Thank you! M |
|
|
|
Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!
Excellent! M |
|
|
|
Since I had a little bit of time... here's v2.1. Lots of little things. v2.1 - Added some more error handling and debug code around the API logic. - Enabled alerts for the web screenscraping logic (non API). - Fixed a typo that would complain about an S2 temp alert not being set when it was S1 turned on not S2. - Visual change to make it clear how to add Ant addresses, and the local IP address is for scanning, nothing else. - Added an email governor to prevent email alert spam. Set to this minimum time between EMail alerts. Note this runs by Ant, and defaults to 10 minutes. - Added a difficulty column to the Ant output grid. It assumes the last difficulty for the first "Alive" pool is the right one. - Added the ability for it to remember column positions. - Added single instance logic, to prevent you from accidentally running more than one at a time. Download link: MAntMonitor21.zipM |
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? I thought anything more than 0.1 sec is too high? If that's wrong I'll adjust my settings.. M Well my node seems fine with anything up to 1s. I only have 1 orphan out of 13. www.norgzpool.net.au Any other node ops thoughts on this? M |
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
Is that reliant on bitcoind only or also peers? I've been doing some tuning of bitcoind but struggle to keep it below 0.5 secs and not topping 1s. Is that a bitcoind issue or a p2pool issue? I thought anything more than 0.1 sec is too high? If that's wrong I'll adjust my settings.. M |
|
|
|
|
Another thing I'd add to the list...
Fix being able to get lots of transactions without GetBlocktemplate Latency going through the roof. OR something that alleviates the problem. Long term p2pool isn't going to cut it if it can't get transactions.
M
|
|
|
|
|
Show Posts
