To put it simply, we're dealing with the usual fuckage and nothing can really connect to the pool while it's happening even though the pool is still running, and try to restart things as soon as possible to minimise the downtime. We've excluded quite a few possible causes but not found the problem yet and are still investigating and hopefully narrowing in on the true cause.
We all appreciate the effort you both put into keeping this ship afloat, I've no doubt this bug will be squashed.
Wow, gotta say, totally awesome.
Bitmain of course dropped the ball on this and have given up on anyone who bought their S1/S2/S3 saying they don't care.
However, someone (who wants to remain anonymous) has sent me 10BTC and asked me to do the S1/S2/S3 work.
Guess I'll be spending the time on this over the next 2 weeks that I was asking to do and get the S1/S2 updated and sort out some p2pool issues, and also merge a working S3 into cgminer master
(and of course dust off my old S1/S2 and get them working again)
The kano.is pool problems (and a backend ckdb change I've been working on) have been taking a lot of my (and of course -ck's) time, but I think I can handle both (if I ignore everything else
)
Good news
I have to agree, totally awesome! Thank you, anonymous. My S1 and S3+ thank you as well.
Good luck, Kano, should be a fun project.