Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2099. (Read 5352067 times)

There's a bug there that's been around for a few months now and rears its ugly head every so often - lately more so than usual. It's likely in my ckpool code but I'm still unsure of what it is, and it seems to affect only kano's pool, not solo ckpool though they're different workloads, hardware, database etc etc so there are multiple confounding variables. We're continually investigating and kano goes to great lengths to spot when it happens and restart the pool as soon as possible which seems to correct it.

Kano

It not the not found block issue it is the miner disconnects from the pool in the past few days there have been large drops where the moners slowed to 25% of there capabilities,  I have seen this several times then they drop completely,  I suspect a pool issue and they come back to normal and then i see there was a server reset.

I am very happy with CK pool and am grateful for all your support here.  So no I am not complaining at all.

Just wanted to make sure you know whats going on and to see if there is a issue that might need to be addressed.

Been a few ckpool restarts due to the problem I mentioned earlier, but it's still happening.
It doesn't lose blocks. The block luck is simply that - luck.
We don't count up to finding a block, we simply find a block randomly every so often, but expect to average finding a block (or orphan) every 100% Diff.

The affect of an outage is that for the seconds/minutes that the pool is acting up, that means less hashes trying to find a block.
The current block luck, is just that, bad luck finding it, as represented by the Diff% being high.

If you look at the stats up to the last block, they are still very good for 5 blocks, 25 blocks and 50 blocks, but bad for 10 blocks, even though there are a few high Diff % blocks there. 6 over 200% and 2 of those almost 400%
There's nothing unexpected in those numbers - if you look at the CDF[Erl] that gives an idea of how often those numbers are expected to be worse than they are.
So for the bad 10 block number, 16% of the time you expect it to be worse than that, 84% better than that.

The main issue with those numbers, I've mentioned before, is that even 50 blocks is not much of a sample to be able to infer any problems unless the CDF[Erl] was very close to 1.0000

Expected Block finding time is, of course, related to the pool hash rate. So since the rate has dropped quite a bit recently, the expected tim to find a block has increased also. So a 200% block at 2PHs takes twice as long as a 200% block at 4PHs, but since you are a larger % of the pool due to the pool having a lower hash rate, then you will get a larger % of the rewards.

Cool, that would be a better idea even.

Yes, and the name needs to be Kano ckpool... 

I noticed a restart today a few hours ago.  I've also notice my miner hash steadily declines over the past about a week, but didn't know if that was pool related or not.

Kano

Any idea whats up with the pool the past few days.  It seems like the pool needs to be reset every several days or the ability to catch blocks is non existence.  And my miners that are normally extremely stable have been dropping hash rate and almost going to 0.0...   Seems like something is up, even the p2p pools are catching blocks, and we have not in almost 3 and a half to 4 days


Just was wondering if there was a issue

... and the name?

This is doable, I'll add it to my list
Perhaps I'll keep the exclamation mark for rate warnings, but change the block found icon to the bitcoin symbol.

may you want to open an extra topic for it  

I have a suggestion.  Currently the app has one notification icon for if the pool found a block and/or if your hash rate drops below the threshold you set:


I suggest keeping that icon for when the pool finds a block, but use a ? version for when your hash rate drops.  It's disappointing to get a notification only to find out it's low hash rate (turned my threshold way, way down, basically an on/off toggle, recent restarts were setting it off left and right).

Sorry about that, had a whole lot of trouble there with ckpool dropping connections left, right and centre.
I've rolled it back to a version last week and that has sorted it all out for now.
That older version is the one that has this same problem that shows up about once a week, so it's not a complete fix for it, but at least it's a lot rarer than happening almost immediately with the latest version.

I've tweaked as much as I can.  I can't seem to go up in the miner list any further without doubling my THs.  Don't think the wife is going to go for that.

This block feels a little crunchy ... let's see how it goes 

The bright green gods will return ...

No worries man, life gets in the way ;p

Sorry about the delay for all the planned features for the app. I've been swamped with other responsibilities.

49 hours

(155.69%) 

  We could use a lucky streak.  I can't rent any hashpower since it is all over 0.015 due to a new alt coin.  If the rates drop tonight I will toss 100 or 200th at the pool.

I've only restarted ckdb - not the mining since I posted.
That only affects viewing the web pages ... as I said above.

Anyway,
Seems I need to do a few more changes to the ckdb code so that'll delay anything else until tomorrow.
The new version of ckdb was over zealous reporting information in the restart
>570k log messages on the console during startup - oops
Have to just fix that tomorrow, then I'll update ckpool also after that.

Tell me what it is you have such frequent rebooting the server

Just had another lockup.
-ck has some new changes for ckpool for the lockup, so I'll be testing them a bit later.

I've also got some ckdb changes that I'll put live shortly - nothing noticeable on the web site, just the db being more reliable with an unreliable data source.
so if you see the web site go off and on you know that's just the new ckdb changes going live - that has no affect on mining.

After I'm happy that ckdb's update is ok I'll update ckpool also to see if that fixes the lockup problem.
the ckpool restart should just be a reconnect in your miners so you might see that.

I'll post after it's all done.

speaking of locking up, found the laptop running the miners dropped its wifi chipset, found out much later and had to give it a boot, should of done some updates whilst i was at it... :-?