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

[kano]

Payouts 338962 and 338977 sent

Confirmed

[1713971762]

1713971762

[1713971762]

1713971762

[1713971762]

1713971762

[1713971762]

1713971762

[1713971762]

1713971762

[1713971762]

1713971762

[ZACHM]

Added found blocks to graph and a graph line representing the average time between blocks based on the last 10 blocks found by the pool.

http://ckpoolmonitor.zachmonroe.com/

[kano]

Payouts 338962 and 338977 sent

Confirmed

I missed commenting in the thread when I did the 338845 payout.
The payout was of course done, but for those who noticed that I missed posting it here, it was:
338845 f05afe131106639d861c2850513c8d09ce6c8e290253d27b2500de8aa7bc0cbb
https://blockchain.info/tx/f05afe131106639d861c2850513c8d09ce6c8e290253d27b2500de8aa7bc0cbb
Sent Jan 15 09:52 +11 (AEST time)
(~22 hours ago)

[hurricandave]

I can't find 338064 payment, its old I know but I left the house for a couple days and now my notes are all Fubard!

[kano]

I can't find 338064 payment, its old I know but I left the house for a couple days and now my notes are all Fubard!

Last 19 (338nnn) and their transaction numbers:
338064  f6f544e3f157c1048a8da86ec5d16850854b39a7544edd3919601528e6132d4d
338089  5d3b101f7dba56c86e48444967c900ccf4742a36bf8f98151380e82d35c10c05
338136  17e43d94c90bc8f450a077f97ea1d5e8dcace92556ec95483990db1921b45ef6
338160  c5996e3a630bda43b235bd86c074ba7a0dd0bd63fbf29a3e12d8bca5db35bfb0
338201  d04b6bf18b9209f29d57d7ca348083230503762b85de2cf43b311a480dfb0211
338287  387527094943ec6a817c45fcab6216967893ea2b513a4799e0cb41d75b8f80c0
338365  9069ee5d2bf89fc19eef984b509dffba9d37ea675fcbaee61e472f9cb5ac9a57
338391  623f5ffe8f1bd6d24a5af76ffa1a101e26e12074d9b696ca1c7abad692bd09fc
338440  4a7008b1249f84d380bd03c03b2dbe11b07ffaa287dca58dc61263a0f4743040
338471  2b62ae52b316d70cce0b9b35e0cca0814a9867a76c97cae8d39799df2c3858fe
338473  c2b3fb9994607d8e9a0a7d3df2dce10434c7fecc73f7de41f44e01f65abcdfb8
338639  0455e9b17d9e9d7f37da7ea9ebf34de08b7c1f505fcfcfb68233954d37a5f2a1
338713  bb329d480dd220fedd19d3b44cdd96fecca0704047ad47a71b5b0e0b41fea277
338765  38271611a223de346ced59e53b828c35398560b14fd185643edfda1ca11cd9d1
338787  a86c220fa82eaa12c6830fa8fa709cb3a85bef2d7cf8f74d494aac1aed26bcb4
338845  f05afe131106639d861c2850513c8d09ce6c8e290253d27b2500de8aa7bc0cbb
338893  7a238cc611fc71aa64fe93513fff169bc54b185e71e7d4850cef4f02c15d81d4
338962  b6f71e790780e4e981de11033cf0ddefc613546f50d6e8042d3fdafdaf56f74d
338977  cd38750a19285691bfc5e015f6a4db0b58a182f391aa57fc1a54027457f2fb2a

Edit: 19 out of 1000 - not bad - 1.9% of the network

[kano]

Pool went down unexpectedly for 95s so most people will have failed over.
It's back up of course.
I'll be working on moving the shift changes live later today which may help with the cause of the above short outage.
I'll post here when those changes are happening.

[dmwardjr]

LOL

Wow...  You weren't kidding.  211 TH/s

EDIT:  They're coming back.

[sjc1490]

Pool went down unexpectedly for 95s so most people will have failed over.
It's back up of course.
I'll be working on moving the shift changes live later today which may help with the cause of the above short outage.
I'll post here when those changes are happening.

Thanks, I was just going to ask as all mine have indeed have moved to backup pools.

[Digitalmocking]

Pool went down unexpectedly for 95s so most people will have failed over.
It's back up of course.
I'll be working on moving the shift changes live later today which may help with the cause of the above short outage.
I'll post here when those changes are happening.

Is that why 7 of my 8 workers show inactive?

Must have failed over to my backups.

[kano]

LOL

Wow...  You weren't kidding.  211 TH/s

EDIT:  They're coming back.

Yes if you look at the stats page you can see most have already switched back - but the pool stats is slower to adjust ... as it should be.

[727miner]

LOL

Wow...  You weren't kidding.  211 TH/s

EDIT:  They're coming back.

Yes if you look at the stats page you can see most have already switched back - but the pool stats is slower to adjust ... as it should be.

My miners are still not connecting back to the pool. I've cycled them twice but they show the pool as dead. Anything else going on?

[Beachguy]

....19 out of 1000 - not bad - 1.9% of the network

Not bad at all!

Thanks man! Great pool.

[sjc1490]

LOL

Wow...  You weren't kidding.  211 TH/s

EDIT:  They're coming back.

Yes if you look at the stats page you can see most have already switched back - but the pool stats is slower to adjust ... as it should be.

My miners are still not connecting back to the pool. I've cycled them twice but they show the pool as dead. Anything else going on?

Same here.

[DevonMiner]

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 

[scotty2u2]

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

[sjc1490]

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

[kano]

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.

[hurricandave]

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]

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]

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.