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

[kano]

As per the message on the notices web page: https://kano.is/index.php?k=notice

NL Network Maintenance at 3-May 3:00am UTC until 3-May 4:00am UTC
The data centre for the NL node will be performing network maintenance.
The provider has stated there may be a very short outage during the maintenance.

Any short outage would lead to a short failover to your backup mining settings in your miner.
Ensure you have a backup node configured in your miners in case of an outage, or unexpected problems.

In about 49 hours - see the web site for the countdown in the header.

Edit: oops - updated - it's the NL node, not the NYA node.

[kano]

Block! by blockmines
S9v2

[delicin33]

Pool hash rate down to 40pH, and my ckpool monitor is beeping

[beltsniffer]

Pool hash rate down to 40pH, and my ckpool monitor is beeping

All of mine failed over to their backup pool for about 15 min. All of them have reconnected now though. Must have been a problem with the main node.

[kano]

The pool hash rate dropped to an alarmingly low 20PH there for about 10 minutes.

The problem was that the passthru stopped accepting connections at all, and dropped everyone, but kept running along without a peep about there being a problem.
My alarms of course went crazy as the hash rate spiralled down, but it took a bit of time to realise it was the passthru (since it doesn't report anything at all when running - another TODO to fix in ckpool ...)
I restarted both the main pool and the passthru to rectify the problem.

All the nodes were mining OK - they total about 20PH - but of course everyone was failed over there when I restarted the main pool.

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

The outage started at 07:58 UTC and was resolved at 08:10 UTC, so 60% of miners should see at least a 12 minute gap in their mining on the pool for that time, 4 minutes after the block.

[smutboy420]

The pool hash rate dropped to an alarmingly low 20PH there for about 10 minutes.

The problem was that the passthru stopped accepting connections at all, and dropped everyone, but kept running along without a peep about there being a problem.
My alarms of course went crazy as the hash rate spiralled down, but it took a bit of time to realise it was the passthru (since it doesn't report anything at all when running - another TODO to fix in ckpool ...)
I restarted both the main pool and the passthru to rectify the problem.

All the nodes were mining OK - they total about 20PH - but of course everyone was failed over there when I restarted the main pool.

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

The outage started at 07:58 UTC and was resolved at 08:10 UTC, so 60% of miners should see at least a 12 minute gap in their mining on the pool for that time, 4 minutes after the block.

 looks like we also somehow lost a good amount of users from just yesterday. right now its saying 797 users. I could of swore that was over 900 yesterday if im remembering right.

[kano]

The pool hash rate dropped to an alarmingly low 20PH there for about 10 minutes.

The problem was that the passthru stopped accepting connections at all, and dropped everyone, but kept running along without a peep about there being a problem.
My alarms of course went crazy as the hash rate spiralled down, but it took a bit of time to realise it was the passthru (since it doesn't report anything at all when running - another TODO to fix in ckpool ...)
I restarted both the main pool and the passthru to rectify the problem.

All the nodes were mining OK - they total about 20PH - but of course everyone was failed over there when I restarted the main pool.

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

The outage started at 07:58 UTC and was resolved at 08:10 UTC, so 60% of miners should see at least a 12 minute gap in their mining on the pool for that time, 4 minutes after the block.

 looks like we also somehow lost a good amount of users from just yesterday. right now its saying 797 users. I could of swore that was over 900 yesterday if im remembering right.

Yep it was saying just over 900 - but the hash rate is still around 50PHs so I guess it was a couple PH of rentals ... and I'm certainly never concerned about losing rentals ...

Meanwhile, I've resolved the problem with the passthru (written some code to report the client count) so next time the passthru screws up like this I won't be in the dark about it.
The passthru machine runs 2 passthrus, one for kano.is and a 2nd for kano.space (that only a few people ever connect to)
The 2nd one, kano.space, was ok during all this except of course for the (unneeded) pool restart that made it reconnect.

[kano]

Block! by Lord2 with 17THs! The miner that found it was only 1THs
Maybe an S5?
and a payout

Edit: Restart block?

[-EOS-]

^ Just proves every little bit helps!

[cedarlug]

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

Can you confirm that the website authentication is functioning correctly?  I'm not able to log in to kano.is nor kano.space site.

ADVthanksANCE

[kano]

Restarting the passthru immediately fixed the problem and the hash rate is now back to 50PH

Can you confirm that the website authentication is functioning correctly?  I'm not able to log in to kano.is nor kano.space site.

ADVthanksANCE

You had an invalid email address.
I close accounts with invalid email addresses since I can't contact the person to tell them it's invalid

[cedarlug]

You had an invalid email address.
I close accounts with invalid email addresses since I can't contact the person to tell them it's invalid

Thanks for the response -

I can confirm 2 things - (1) the e-mail address is indeed valid and (2) the e-mail service for the domain is presently down - but will be back up in 3 hours.

[kano]

You had an invalid email address.
I close accounts with invalid email addresses since I can't contact the person to tell them it's invalid

Thanks for the response -

I can confirm 2 things - (1) the e-mail address is indeed valid and (2) the e-mail service for the domain is presently down - but will be back up in 3 hours.

email server currently has 140 errors like this for the last 24 hours
dsn=4.0.0, stat=Deferred: xxx: No route to host

I call that an invalid email address.

Yes it's a static IP, yes it pings, but no there's no email server there.

[clgrissom3]

Well alright, May is starting off on the right foot with 2 in the tank overnight!

Now I can go catch up on all those blocks that came in over the past 4 days while I was playing hunter out in the wild!

[cedarlug]

email server currently has 140 errors like this for the last 24 hours
dsn=4.0.0, stat=Deferred: xxx: No route to host

I call that an invalid email address.

Yes it's a static IP, yes it pings, but no there's no email server there.

Back online now.  Thanks for the follow-through.

[daemondazz]

email server currently has 140 errors like this for the last 24 hours
dsn=4.0.0, stat=Deferred: xxx: No route to host

I call that an invalid email address.

Yes it's a static IP, yes it pings, but no there's no email server there.

That is an email server problem, not an email address problem. An email address problem would result in a rejection, not a deferral.

[kano]

email server currently has 140 errors like this for the last 24 hours
dsn=4.0.0, stat=Deferred: xxx: No route to host

I call that an invalid email address.

Yes it's a static IP, yes it pings, but no there's no email server there.

Back online now.  Thanks for the follow-through.

OK once one of the queued messages gets through I'll PM you to say when I've re-enabled the account.

[kano]

email server currently has 140 errors like this for the last 24 hours
dsn=4.0.0, stat=Deferred: xxx: No route to host

I call that an invalid email address.

Yes it's a static IP, yes it pings, but no there's no email server there.

That is an email server problem, not an email address problem. An email address problem would result in a rejection, not a deferral.

Same thing.

[-EOS-]

ADVthanksANCE

 

[cedarlug]

That is an email server problem, not an email address problem. An email address problem would result in a rejection, not a deferral.

Same thing.

Not to belabor the point while sitting here with a suspended account, but they definitely are not the same thing.  None of the messages were rejected with an invalid address and they won't be.

When services go down it's an inconvenience for everyone - In light of today's outage, even you should grant me that, Kano.  

Your queued messages are now coming through.

Thanks again for the follow through.  It is greatly appreciated.