-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow pools to be re enabled automatically #39
Comments
I agree. This should be automated somehow...or at least an option to not disable it but instead move on to the next profitable coin. |
Would you be so kind as to test this update which addresses this issue? Coin configurations are no longer permanently disabled. They are disabled for 1 hour, and manually stopping & restarting mining resets things: https://www.dropbox.com/s/ll1805ms0haydv8/MultiMiner-2.4.0.zip |
Downloading now, will report back :) Cheers |
Thanks I appreciate it. This one is tough to test for obvious reasons. |
Will the disabled message still showup, both onscreen until I acknowledge it and also in the logs? Just need to know how I can verify it's working? |
Visually everything should remain the same. Only the behavior changes. |
There'll be a message to say the pool has been rechecked or is back up? |
There is no checking or unchecking anymore - the coin configuration remains checked. The notification will display that all pools are down and that the configuration won't be used. There is no notification when the "re-checking" happens. It's every 1 hour or if you start & stop mining manually. That resets any "pool down" flags. |
Addressed in f19d729 |
Not sure if related to the release you gave me or a new issue but it just crashed on me - http://pastebin.com/u8fHuAuy Haven't had any pools disable yet, so no word on whether it does / doesn't work yet (unless this crash is related) |
Now I get this everytime I try and open it - http://pastebin.com/4faNeAwe |
hi installednewversion now get this past 2 hrs crashing On Tue, Jan 21, 2014 at 7:36 PM, k4n30 notifications@github.com wrote:
Regards |
I'd recommend using the CoinWarz API until CoinChoose.com works their issues out. |
Sorry for the delayed response as it's only just now my pools started going down again. I can confirm that it works :) |
Awesome thanks so much for confirming. It's very tough to reproduce and test something like this. |
as per https://bitcointalk.org/index.php?topic=248173.msg4334493#msg4334493
Is it possible to have a value that we can set to try and reenable a pool. Rather than have multiple pools for the odd chance when a pool goes down. Having strategies enabled is useful for profitability reasons and having a pool go down (sometimes for only a few minutes) disbales it until it's manually reenabled.
The value can either "ping" the pool to see if it's back up, or just blanket reenable it on the off chance it is (if not it will disable again)
Thoughts?
The text was updated successfully, but these errors were encountered: