Anyone wondering ... CKDB crashed 12 minutes after that block and is restarting (automatically)
Looks like I've got a bug I need to track down.
Of course nothing is lost, it's just a normal CKDB restart after the crash ... restart will finish in about 10 minutes.
No miners are affected.
That's what happens when you suddenly awaken a sleeping sentient entity...
Oddly - I woke up, for no obvious reason, a few mins before the block ...
The reward generation code is what crashed - I'm looking into it now.
Just need to fix it before that payout comes due
Feels like you have an margin failure in the code, since 700%+ duration is so rarely seen, if ever. I'd rather it fails on condition (lim -> 0).
No, it's a line of code with a null value that's (years) old and I've no idea how it ever worked to start with
(It's data that doesn't matter - a field that is always blank, but somehow the code doesn't seem to mind that it's null)
Still trying to discover why it worked fine in all but the latest code.
Maybe being half awake is dulling my senses
I'll do a restart again once it's sorted out but that may be a while off yet.
I'll do a CKDB restart at ~22:45pm UTC in roughly 1.5hrs (the shift that should complete around then)
No miners will be affected.
Web site/api will show lotsa ? for about 10 minutes.
It's the bug fix for the reward calculation code that crashed.
Just in case anyone was worried, it didn't affect anything in the past - it's 3 as yet unused text fields that are always blank, but for some reason being null (the bug) never crashed the code before. They are now blank and not null.
I've also added a check for anything else being null that may have unexpectedly worked in the past - it now spits out a warning about where in the code it was null, so I can fix any others that might have been hiding for the past year or 2
Check the git commit log if you are curious.