KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2437 blocks

[kano]

Payout 355773 sent
7a98fee384cd0d00662327135f28b9a8502b67ccc37925f6ace449c1980e576c
and confirmed

(It's unaffected coz it's before the 3 shifts)

[sorry2xs]

and Tin TinTin hits 355952, and i am not going to say anything about smelling another back to back

[kano]

and Tin TinTin hits 355952, and i am not going to say anything about smelling another back to back

That block actually crashed ckdb That of course doesn't affect anything except it caused a ckdb restart.

The shift problem hasn't been 'repaired' yet coz it got too late (2am) before I completed testing the changes.
But of course this block crash showed up another (silly) bug in my code that will be fixed with the changes in the morning.

Yay finally a block under 100% diff

[Mikestang]

I got a fake Block Found notice, it almost worked...

I've received two fake notices over the weekend, always a bummer.

Probably when I restart ckdb?
There a period of time when I restart ckdb, when it won't reply or gives back nothing useful - maybe the app forgets the last block when that happens?

Yay finally a block under 100% diff

Yay indeed!  I got a warning that my hash rate dropped to 0, and then got a block found message, so I assumed it was another fake find restart generated message until I checked the last block found date/time, woo hoo!

[CapnBDL]

Whew...what just happened? Can't pull up site.

edit; did we just hit?

[sorry2xs]

it seems like the pool is got about of block indegestion

[kano]

Whew...what just happened? Can't pull up site.

Another block - same ckdb crash
Last one 3hrs ago was 3:20am for me - now 6:20am
Will fix the crash when I fix the shifts.

Gotta love a crash each time we find a block
Mining is of course unaffected.

[tlhIlwI]

FWIW - It looks like the two shifts today where blocks were found may be missing some shares (though not nearly as bad as the shift probelm from yesterday).  The crash when finding a block and the missing shares issue may be related.  I thought you might want to know in case it helps narrow down the code you are looking at.

[kano]

FWIW - It looks like the two shifts today where blocks were found may be missing some shares (though not nearly as bad as the shift probelm from yesterday).  The crash when finding a block and the missing shares issue may be related.  I thought you might want to know in case it helps narrow down the code you are looking at.

Yeah when I fix the 3 bad shifts I'll reset it back to before them and have it redo all the shifts since yesterday when it first happened.
(It will also recalculate the rewards for these 2 blocks so they will be different, but for most people not much different)

In the ckdb crash that's happening now, one of the processing threads locks up when we find a block (it also says the cause so it's fixed in my testing code already)

Was just that at 2am I was real tired and decided to stop there and finish it in the morning
Oh well, it's morning now (almost 7am) better get to it once I'm a little more awake.

[DevonMiner]

A 0.080 CDF block ... nice ... only 3hrs until it popped   ... with confirms

Not seen a bright green label since 23rd April.

[TheOneJester]

It is a block party! I'll bring the beers!


Not sure what the server returns as the last block found after a reset, but the app just checks the last known block found stored on your device compared to the servers last block found when it checks for an update.

SO you can run into a few issues. 

If you set your update interval to several hours, and the server actually finds multiple blocks between checks it will only report 1 block found.


Also if your phone happens to pull api data when the server is offline/restarting it will report 0's for all the hash rates. Hence the rate warning. (When I get a chance to learn about ckpool and how it handles these exceptions, I can also handle these exceptions more gracefully in the app.)

I'm also still working on all the promised features, but several other projects are also keeping me busy.

Cheers and party hard!

[xZork]

I'm crossing my fingers for some more bright green!

[kano]

Anyone paying attention to the shift data - yep there's now (temporarily) an empty one in there too.
But code seems all ok and ready to roll back the shares/rewards back to yesterday and get it to reprocess them all again.
Will do that soon then post if/when ckdb is finally all back to ok (which might still be a while)
Should be done before the payout is due so there should be no delay when they reach 101.

[CapnBDL]

AWWWW....no freakin' way...oh, yes way...I just bricked my S3+. Crap...there goes my main miner. Sorry...gonna be in limp mode until I get a break-out board.

edit; not that I was top of the leader board anyway.

edit2; aww...crap, I think I really did it! Thought I'd try a trick...no luck. Switching to that forum...but I am screwed!!!

[kano]

I'm about to do the reload of the shares from yesterday before the bad shift - so that will take a while - and the web site will do the usual ? stats while that's happening.
I'll post here again when it's finished.

Sorry - pool is in a state of havoc for the last 10 min or so.
Reloading 1.5 days of data is pushing it to the limits.
It's almost finished, but you will have been failing over pretty much all the time for the last 10 minutes.
Should be ok again with the next 5 or 10 min (processing the last 2 files)

Ended up causing pretty much constant ckpool failures due to ckdb eating up all the ram
ckdb was using more than total ram and ckpool can't be allowed to swap since mining definitely should not be getting disk swapping delays

I added in a fix to the problem (seeing a problem happen always helps to make you think hard and fast about how to fix it)
So it's been reloading again from scratch the 1.5 days of data for the last half hour and should be done in about an hour, without all the problems ckdb caused before.

[thedreamer]

Whoa. Pools on a meltdown.

[BlInK311]

Whoa. Pools on a meltdown.

Yeah I have been watching it all morning.  they must be updating some of the code and updating the database.  My miners still say the pool is alive so its all good.(I hope) 

[thedreamer]

Whoa. Pools on a meltdown.

Yeah I have been watching it all morning.  they must be updating some of the code and updating the database.  My miners still say the pool is alive so its all good.(I hope) 

Mine have already switched over to the failover please get it back up so I don't have to give more money to eligius, they are on a week-long backlog for payments.

[BlInK311]

Whoa. Pools on a meltdown.

Yeah I have been watching it all morning.  they must be updating some of the code and updating the database.  My miners still say the pool is alive so its all good.(I hope)  

Mine have already switched over to the failover please get it back up so I don't have to give more money to eligius, they are on a week-long backlog for payments.

(Unrelated to pool maintenance)
All my miners and home server just went offline.  Power company must be messing with the lines again.  Yesterday my modem needed a forced reset and I lost a whole day.  Lets hope everything comes back up correctly when they turn everything back on.  Fingers crossed.

EDIT: everything came back up.  phew

[mrquick]

My miners have been failing over all morning (here in UK) but as my failover is solo.ckpool its not so bad. (maybe I get lucky)
 I think they are mining on Kano pool at the moment.

I imagine not much sleep for Kano, again.