Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 204. (Read 5352229 times)
May 22, 2018, 12:59:23 PM
I just noticed something a bit odd. The time of the last block found has an hour value of 24 with some minutes and seconds after it. The last I recall there are only 24 hours in a day. Is something a bit wobbley with the ckpook app?
May 22, 2018, 12:53:22 PM
Kano, thanks a lot for fixing this!
Just out of curiosity, do you know why ckpool crashed?
Was the problem somehow related to KDB / resource issue (I though ckpool is totally independent...)?
Just out of curiosity, do you know why ckpool crashed?
Was the problem somehow related to KDB / resource issue (I though ckpool is totally independent...)?
May 22, 2018, 12:53:07 PM
Hi, I am New with mining and on May 20 of 2018 antminer s3 has 44 block, what this means and do I going to get pay?
Thanks
They are not Bitcoin blocks and not blocks on this pool.Thanks
You have been mining altcoins - which this pool does not support in any way whatsoever.
If you are using a rental proxy then they have been pointing your miner at altcoins.
Very high fees on rental proxies make them a bad idea (along will all the other reasons)
May 22, 2018, 12:49:55 PM
Hi, I am New with mining and on May 20 of 2018 antminer s3 has 44 block, what this means and do I going to get pay?
Thanks
And May 21 2018 another 2, no pay, please help me , thanks...
Thanks
And May 21 2018 another 2, no pay, please help me , thanks...
May 22, 2018, 12:43:58 PM
KDB Restart NOW
Getting a resource problem - all is OK so far but I can see it causing problems shortly if I don't give it a kick.
Mining is unaffected - just the web site will show lotsa zeros and '?' while restarting.
Mine on.
Unfortunately the pool dropped all miners and thus everyone failed over initially from 14:08 until 14:13Getting a resource problem - all is OK so far but I can see it causing problems shortly if I don't give it a kick.
Mine on.
Not long after this the pool crashed - however in the crash it wrote a corrupt worker status record to the reload file and KDB couldn't handle the corrupt record and crashed also, until I found and removed the corrupt record from the reload file - which required stopping the pool while I did that.
The console log says all is OK, but I'll rerun the shifts on the backup server and make sure they match/correct any differences before any more payouts.
Sorry about the long mining outage - but all OK again finally.
Mining is still (currently) all OK.
The web site will be back up once KDB has finished restarting.
After shutting down a few things that mining can function without and yet again ckpool crashing, KDB finally was able to catch up and all finally OK at 17:05 UTC
One important point to note, however, is that no shares were lost in all this.
As per normal, a KDB restart does scan back to before it was up to when it stopped, then run forward using the reload files and in this case that was all OK other than the original corruption that did not lose any shares - all share sequence numbers were accounted for correctly.
Of course everyone was failed over to their backup pools for quite a while during this, but any shares submitted have been accounted for.
Sorry for the long delay fixing the problems, but finally all is OK again - and of course the web site is back up and all functioning OK again.
May 22, 2018, 12:40:12 PM
As much as I dislike Chinese sites... my final backup pool is ViaBTC - simply because they are PPS - so I get credit even if I'm only there for 5 minutes. Slush use to be my backup pool, but their ramp up of an hour or three doesn't make it a great fit unless we have a long outage. ViaBTC shares transaction fees as well.
I have my 3rd option to mine solo. Basically on fail over I start lottery mining...lol
May 22, 2018, 12:29:52 PM
Whew...had me goin' there for a bit... 
May 22, 2018, 12:25:45 PM
here all up as well. 
May 22, 2018, 12:22:32 PM
I have all the servers running, and the hashrate is normal, 
Ps.: The site works
Ps.: The site works
May 22, 2018, 12:22:05 PM
My bet is kano is downing a ton of coffee right now trying to fix this.
MINE ON WITH KANO-SAN!
^^^ what he said. Kano is totally on the case for sure. Must be a good one whatever it is!MINE ON WITH KANO-SAN!
Mine On (when applicable)tm
May 22, 2018, 12:18:32 PM
Miners are coming back online at kano again.
May 22, 2018, 12:14:31 PM
My bet is kano is downing a ton of coffee right now trying to fix this.
MINE ON WITH KANO-SAN!
MINE ON WITH KANO-SAN!
May 22, 2018, 12:13:31 PM
my miners are not mining 
May 22, 2018, 12:10:51 PM
so far i tried several servers and ports. Havn't found a working one.
My app is yelling that my hashrate went down (duuuuh) but when i open the app, it crashes...
kano, whats wrong fellow, we had such a great week...
Any server you want us to point or power to?
im happy to change pool settings temporary until you fix the rest...
Let us know.
My app is yelling that my hashrate went down (duuuuh) but when i open the app, it crashes...
kano, whats wrong fellow, we had such a great week...
Any server you want us to point or power to?
im happy to change pool settings temporary until you fix the rest...
Let us know.
May 22, 2018, 12:03:00 PM
both stratum and NYA are down ?
May 22, 2018, 11:55:52 AM
well, dont know whats wrong, but the german as the dutch pools are dead...
which ones are alive?
hate to see my 5n rate drop again...
which ones are alive?
hate to see my 5n rate drop again...
May 22, 2018, 11:52:35 AM
Where's ArielGopher when ya need him?
May 22, 2018, 11:03:11 AM
Website down again
But the miners are mining. That's all that matters.MINE ON!!!
May 22, 2018, 10:50:53 AM
KDB Restart NOW
Getting a resource problem - all is OK so far but I can see it causing problems shortly if I don't give it a kick.
Mining is unaffected - just the web site will show lotsa zeros and '?' while restarting.
Mine on.
Unfortunately the pool dropped all miners and thus everyone failed over initially from 14:08 until 14:13Getting a resource problem - all is OK so far but I can see it causing problems shortly if I don't give it a kick.
Mine on.
Not long after this the pool crashed - however in the crash it wrote a corrupt worker status record to the reload file and KDB couldn't handle the corrupt record and crashed also, until I found and removed the corrupt record from the reload file - which required stopping the pool while I did that.
The console log says all is OK, but I'll rerun the shifts on the backup server and make sure they match/correct any differences before any more payouts.
Sorry about the long mining outage - but all OK again finally.
Mining is still (currently) all OK.
The web site will be back up once KDB has finished restarting.
May 22, 2018, 10:48:51 AM
Website down again
But the miners are mining. That's all that matters.
Jump to: