EDIT: You'll have to do this after every reboot unfortunately, as it will reset to defaults. Just don't reboot it......  Seriously?? Wow. Isn't this easier? /usr/bin/cgminer-api "setconfig|queue,0"
M |
|
|
|
vi /etc/init.d/cgminer.sh Press “i” (enter edit mode) Scroll down to line 60 in the code, starting with : PARAMS="--bitmain-dev.... change the queue parameters at the end of that string to: --queue 0 press "esc" (exit edit mode), then type: :wq & hit enter. Then click save & apply in the web UI miner configuration tab  EDIT: You'll have to do this after every reboot unfortunately, as it will reset to defaults. Just don't reboot it...... tyvm. Do you set your worker difficulty, or just live with the p2pool varying one? So far it setting the queue to 0 hasn't made a smidgen of difference on the rejects. Trying 1 now. M |
|
|
|
The number 1 issue is fixed with latest firmware, which runs cgminer 4.6.1. When the work restart request comes in, I usually see the flush work within 1 second, then the new block task usually arrives in another second. Often there are new accepted shares submitted within 2 seconds of the work restart request. The new cgminer 4.6.1 has brought new life to the S2. I used to point the S2's to a different pool, while all my other miners used P2Pool. It's so nice to see them doing the full 1000 GH/s with P2Pool. I have 2x S2's and 2x C1's, and all 4 of them run neck-and-neck.
Are you sure this is fixed? I upgraded my S2 to the newest firmware, and yes I get 1 TH/s now, but I still get 10-15% rejects because of the 30 second work restarts that the Ant can't respond to quick enough. M I'm getting ~3% using the -queue 0 setting mdude - have you tried that? It's leveled out to 6.7%. I haven't adjusted the queue yet. What file do I need to change for that? I'm still a linux n00b. M |
|
|
|
The number 1 issue is fixed with latest firmware, which runs cgminer 4.6.1. When the work restart request comes in, I usually see the flush work within 1 second, then the new block task usually arrives in another second. Often there are new accepted shares submitted within 2 seconds of the work restart request. The new cgminer 4.6.1 has brought new life to the S2. I used to point the S2's to a different pool, while all my other miners used P2Pool. It's so nice to see them doing the full 1000 GH/s with P2Pool. I have 2x S2's and 2x C1's, and all 4 of them run neck-and-neck.
Are you sure this is fixed? I upgraded my S2 to the newest firmware, and yes I get 1 TH/s now, but I still get 10-15% rejects because of the 30 second work restarts that the Ant can't respond to quick enough. M |
|
|
|
Next block will found at: 2014-11-28 09:52:11
Well that gives your guess a 24 hour range since you didn't specify a timezone, so it could be quite possible  That's still a pretty specific guess. 60 seconds per minute, 60 minutes per hour, that's 1 out of 3600. Assuming I did my math right... M |
|
|
|
I discovered about 10 minutes ago as well 2 of the mners (one of which was the one giving the error) had the same hostname. I doubt that makes a difference, but I havechanged it to what it is supposed to be. I'll let you know how it goes either sometime tonight or when I get up in the morning when I see how its doing. Thanks. I set it to reboot every upcoming hour for a few hours in a row to make sure it worked. Hopefully I got it all right this time.  M |
|
|
|
Great I'll test it out right now!!!
But my refresh was set to 300 seconds not 30. You can see the picture that it is showing 266 seconds until next reboot.
Well.. that's what happened. And I read your screenshot wrong. Regardless it should be fine now. M |
|
|
|
Good to know, thanks!
Thanks for the screenshots. That helped me figure out what was going on. The problem was my reboot logic wasn't skipping Ants that had a status of "ERROR". So, in your case, since it was refreshing every 30 seconds, one of the Ants hadn't quite finished rebooting when the next scan ran, and then it got stuck. Here's v3.7 to fix that: MAntMonitor37.zipM |
|
|
|
Hi again, OK I just got back from dropping off my wife, and since my last post that i was turning it on, it received n error on the same IP and is frozen again even with the reboot on error message during refresh disabled.
I just reproduced this. That's good, it means I can fix it. More to come. M |
|
|
|
I should probably mention, that the program was frozen when I got to it, so it's possible the program got the error 44 minutes after reboot. It was non responsive I could click and change everything but it would not refresh anymore. clicking refresh did nothing.
I'll turn it back on now and see how it handles the Noon reboot. I have disabled the option to "Try to reboot ants that get error on refresh"
Aha! That's a good point. It's entirely possible it tried rebooting the Ant that just rebooted and wasn't responding, and got itself in a loop. Thanks for the feedback. I'll see if I can reproduce this. M |
|
|
|
I'm using an Corsair RM1000 and there aren't any leaks at all because I haven't needed to top anything off for a while. If I could just get 1000GH/s out of my units which is why I bought them I'd be happy. And now my Dad's C1 one of his entire boards is dead. Reads no temp and has -------------- on ASIC status area. I'm starting to doubt the reliability of this hardware. Will there be any compensation for when shipping hardware all the way back to China if needed?
From my experience they send you the replacement first. But, I did specifically say I need the replacement first.. downtime is unacceptable in my mind. If you're in the US, make sure you work with the Colorado office. M EDIT: Also, they included return shipping labels for me, so it was no cost out of pocket for shipping. |
|
|
|
Well I've got a few screen shots to show you on an error thats happening heres the following 3 screen caps, which show a situation 44 minutes after a midnight reboot where one Ant S3(+) gave an error on refresh, (Cap 1 shows this) 2nd cap shows the settings for reboot credentials, 3rd cap shows the program looks like its in an endless 1 second loop with internal error. Let me know if you require anything more from me.
Thanks, this gives me something to work with. The error on refresh could have been as it was rebooting, the next refresh should have shown it normally. I'll try the config you have and see what happens. I did test a similar setup with about the same number of Ants, actually, and it worked for me, so there must be something I overlooked. M |
|
|
|
Just saw the update. replaced v3.5 with it testing it over the next few days before the vacation starts, to reboot every 12 hours.
Great, let me know how it goes! M |
|
|
|
eleuthria - Do you or will you ever have an API? If you look under Settings, you will see your API key. Hahaha No way! How did I miss that. Thank you! If you're a Windows user, my Pool Monitor app supports BTC Guild's API. See my sig. M |
|
|
|
And the way they describe it, with their typical ambiguity, implies it's not compatible with the p2pool chain anyhow.
Yeah, I'm not sure it works at all tbh - but at least they open sourced the code The code released does work with the P2Pool chain. All it does is: - force all miners to mine on AntPool default address
- implements a database to track miners
These allow AntPool to run a sub-pool. But they are not necessary. NastyPool implements a sub-pool without changing P2Pool code. NastyPool allows miners to decide themselves if they want to use the sub-pool address (by adding -PoP to the username). NastyPool uses existing hooks in P2Pool software to track miners. That's a double edged sword. It means p2pool block time is going to decrease. It also means share difficulty is going to double or triple. And lastly .. I thought I read you don't get transaction fees if you use AntPool? Seems to me there are more downsides than upsides there. M |
|
|
|
What the hell. Now I have a complete row of X's. Is my miner slowly dying here?
BITMAIN- help!
I have an S2 that behaves like this. It'll run for a week or so and then an X appears. Sometimes if I power cycle it, it'll go away. Other times, I get more Xs. It's luck of the draw for me. Right now I've got 3 Xs, but it's running at 1 TH/s so I'm ignoring it. It's always been like this. I've replaced two chains, and the power board, and it still does it. It has an oversized PSU in it as well. <shrug> If I were you I'd work with Bitmain and get it replaced. If you're in the US, make sure you work with the Colorado branch, much quicker than the China branch. M |
|
|
|
Can someone explain what the freq and voltage settings do and if they need or should be changed to anything? Seems my hash rate is capping off at 980GH/s, and I'm looking to get that 1TH/s that is supposedly guaranteed. Right off the Bitmaintech's page:
Hash Rate: 1,008 GH/s guaranteed
Thanks
Also, maybe someone can chime on on why I'm getting so many STALE and DUPLICATE shares? Within the last hour:
Antminer C1: 980GH/s
STALE 5120
DUP 2048
Spondoolie SP10 1.4TH/s
STALE 1536
DUP 0
Have you tried different pools? Not all are created equal. M |
|
|
|
What makes NastyPoP so interesting is not that it is some magical payout method that magically uses P2Pool. It is interesting because it allows a sub-pool of miners to work together fairly on P2Pool. And it does this without taking any Bitcoin fees and makes all mining data public.
Totally agree, this is a fix that can work now for p2pool, it creates some centralization and trust is required, but it allows smaller miners to participate, this is a big step in the right direction. I expect the idea of sub-pools within P2Pool to become more popular as P2Pool gets bigger. It is obvious from the AntPool code that this is what they do also.
The difference with AntPool is that they will charge a fee, and as AntPool would already represent over double our hash rate it will hurt the majority of the other miners on p2pool if they were to simply jump in... And the way they describe it, with their typical ambiguity, implies it's not compatible with the p2pool chain anyhow. M |
|
|
|
The number 1 issue is fixed with latest firmware, which runs cgminer 4.6.1. When the work restart request comes in, I usually see the flush work within 1 second, then the new block task usually arrives in another second. Often there are new accepted shares submitted within 2 seconds of the work restart request. The new cgminer 4.6.1 has brought new life to the S2. I used to point the S2's to a different pool, while all my other miners used P2Pool. It's so nice to see them doing the full 1000 GH/s with P2Pool. I have 2x S2's and 2x C1's, and all 4 of them run neck-and-neck.
That's good to know. I haven't tried p2pool since recently with my limited hashrate. M |
|
|
|
|
Show Posts
