KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2192.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Digitalmocking on January 16, 2015, 03:27:16 AM

Quote from: kano on January 16, 2015, 03:25:27 AM

... and in case anyone didn't notice

We just found another one at 58.37% of expected (network diff) Cheesy

Yay, I felt a little silly joining right as the pool hit a +210% block, I felt like a bad luck charm.

... and to really get that worry off your chest

We just found another one at 3.44% Cheesy

Edit: so that makes 3 blocks, total under 300%

Digitalmocking

full member

Activity: 224

Merit: 100

Quote from: kano on January 16, 2015, 03:25:27 AM

... and in case anyone didn't notice

We just found another one at 58.37% of expected (network diff) Cheesy

Yay, I felt a little silly joining right as the pool hit a +210% block, I felt like a bad luck charm.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

... and in case anyone didn't notice

We just found another one at 58.37% of expected (network diff) Cheesy

dmwardjr

legendary

Activity: 1302

Merit: 1318

Technical Analyst/Trader

Thanks for your hard work in putting this pool together and for keeping it going!

BIG thumbs up!!!

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ?? on ??

... the separation of ckdb and ckpool makes for some interesting results Cheesy

We just found block 339142 ... awaiting a confirm.
The web will show it with the actual stats and time that it happened once the sync completes

Confirmed
https://blockchain.info/block/000000000000000008aed20f57154cd55c2519e64e65dc072ed61eefe4dc1675

bitwitt

full member

Activity: 157

Merit: 100

Well the only issues for the last hour should have been that you can't see the web site.
Mining dropped off twice much earlier but it should only have been the web site that was unavailable after the 2nd time.
Web is back up now (ckdb reload has completed properly) and ckdb is syncing with ckpool (that red number at the bottom left)
Once that reaches 0 (may take a while) all the web site should be up to date.

Thanks for the update. Time to round up some wild miners, it reminds me of trying to find cattle when the pasture gate is left open.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: bitwitt on January 15, 2015, 08:11:48 PM

Quote from: kano on January 15, 2015, 06:06:22 PM

Quote from: ?? on ??

Quote from: hurricandave on January 15, 2015, 05:53:12 PM

One of my worker instances is a collection of 30 U2's. It is stuck with the pool default Diff at 1.02k since the restart. I'm guessing that won't change till everything is back in sync?

Hmm ...
If you have a worker diff on the web site, then yes the sync will affect that.
If on the other hand, you don't have a worker diff specified, it will just take a while for ckpool to decide to change the diff.
Diff starts at 1024 by default.

Unfortunately, the auth part of the reload is taking quite a long time, so stats are still not up on the web site yet.
... that was the main problem, authorisation was taking too long so everyone was failing to authorise and repeat authorising.
That's ok for normal workers, but for the few big miners with thousands of connections, it wasn't able to deal with it, thus why the code change I mentioned above that will go in later today also.

Any updates? I have some miners that have gone back to CK but others that have not.

It's times like this I don't envy you. Thank you for your hard work.

Well the only issues for the last hour should have been that you can't see the web site.
Mining dropped off twice much earlier but it should only have been the web site that was unavailable after the 2nd time.
Web is back up now (ckdb reload has completed properly) and ckdb is syncing with ckpool (that red number at the bottom left)
Once that reaches 0 (may take a while) all the web site should be up to date.

ZACHM

hero member

Activity: 777

Merit: 1003

Quote from: bitwitt on January 15, 2015, 08:11:48 PM

It's times like this I don't envy you. Thank you for your hard work.

Absolutely!

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: hurricandave on January 15, 2015, 06:08:45 PM

I set it on the website, to 46 I think but this instance is still mining at 1.02k even though failover returned to Pool 0 about 45 mins ago. Usually when I have to restart for reasons on my end, I get a couple minutes worth of rejected- share above target. But not this time, just kinda takes awhile to get one at 1.02k min. Undecided

Well the actual diff you are submitting shares does not affect the expected payout.
A lower diff just means you submit more lower diff shares so you get less variance in your accepted share rate.
However, over the length of a block (like the current one around 200%) it will make no noticeable difference.

bitwitt

full member

Activity: 157

Merit: 100

Quote from: kano on January 15, 2015, 06:06:22 PM

Quote from: ?? on ??

Quote from: hurricandave on January 15, 2015, 05:53:12 PM

One of my worker instances is a collection of 30 U2's. It is stuck with the pool default Diff at 1.02k since the restart. I'm guessing that won't change till everything is back in sync?

Hmm ...
If you have a worker diff on the web site, then yes the sync will affect that.
If on the other hand, you don't have a worker diff specified, it will just take a while for ckpool to decide to change the diff.
Diff starts at 1024 by default.

Unfortunately, the auth part of the reload is taking quite a long time, so stats are still not up on the web site yet.
... that was the main problem, authorisation was taking too long so everyone was failing to authorise and repeat authorising.
That's ok for normal workers, but for the few big miners with thousands of connections, it wasn't able to deal with it, thus why the code change I mentioned above that will go in later today also.

Any updates? I have some miners that have gone back to CK but others that have not.

It's times like this I don't envy you. Thank you for your hard work.

hurricandave

legendary

Activity: 966

Merit: 1003

I set it on the website, to 46 I think but this instance is still mining at 1.02k even though failover returned to Pool 0 about 45 mins ago. Usually when I have to restart for reasons on my end, I get a couple minutes worth of rejected- share above target. But not this time, just kinda takes awhile to get one at 1.02k min. Undecided

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ?? on ??

Quote from: hurricandave on January 15, 2015, 05:53:12 PM

One of my worker instances is a collection of 30 U2's. It is stuck with the pool default Diff at 1.02k since the restart. I'm guessing that won't change till everything is back in sync?

Hmm ...
If you have a worker diff on the web site, then yes the sync will affect that.
If on the other hand, you don't have a worker diff specified, it will just take a while for ckpool to decide to change the diff.
Diff starts at 1024 by default.

Unfortunately, the auth part of the reload is taking quite a long time, so stats are still not up on the web site yet.
... that was the main problem, authorisation was taking too long so everyone was failing to authorise and repeat authorising.
That's ok for normal workers, but for the few big miners with thousands of connections, it wasn't able to deal with it, thus why the code change I mentioned above that will go in later today also.

hurricandave

legendary

Activity: 966

Merit: 1003

One of my worker instances is a collection of 30 U2's. It is stuck with the pool default Diff at 1.02k since the restart. I'm guessing that won't change till everything is back in sync?

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Yeah everything back to OK finally.
I was busy sorting it out - so I wasn't replying here.
I actually stopped the web site temporarily since it was playing a part in the problem.
Again, the shift changes that will go in later today should deal with most of the issues that happened, and ckolivas is doing another change to ckpool to avoid the reconnect problem that ckdb was unable to service fast enough.
Once the ckdb reload completes (about 10minutes?) all the stats will be back on the web site also.

sjc1490

hero member

Activity: 546

Merit: 500

Looks like all miners are back home now, site is down but miners are submitting now.

scotty2u2

newbie

Activity: 36

Merit: 0

Same here... can't connect to the website. Not sure about my miners because I'm at work.

DevonMiner

sr. member

Activity: 471

Merit: 250

For 30 minutes now I can't load the website, all I get is a blank page.

Two of my miners are still on a back-up pool, but others have reconnected.

I'm not concerned, obviously shares are being accepted ... just sharing my blank screen Grin