Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1651. (Read 5352367 times)
March 07, 2016, 08:00:02 AM
yea a s7 i had rented went down aswell
March 07, 2016, 07:25:55 AM
Regarding the above disk problem, I've promoted that now to a high alert in my checks (i.e. it'll even wake me up)
Before it was only a twice daily message since it's been well under control for a while now, but as usual, there's always something new to appear to cause an unexpected problem.
In this case the log file consumed well over 50GB of SSD system disk space in a couple of hours.
The new alert will pick that up very quickly.
Before it was only a twice daily message since it's been well under control for a while now, but as usual, there's always something new to appear to cause an unexpected problem.
In this case the log file consumed well over 50GB of SSD system disk space in a couple of hours.
The new alert will pick that up very quickly.
March 07, 2016, 05:23:26 AM
Sorry again - there was a catastrophe caused by the earlier failure that I didn't detect before it basically killed the main server.
The nonce proxy went rampant and consumed all the system disk
Once I'd detected the problem (it didn't fall inside any of the parameters for an alert until it was too late) I simply killed everything.
The reason behind killing everything (as I've implied before) is that I don't want people mining on a pool that's not giving out work properly.
Killing the pool means everyone should failover to their backups until the problem was sorted out.
No share logging failed since the share log disk is seperate (and a lot larger) than the system disk, so now everything is back up and working, all shares and data will catch back up to everything that happened up to and during the problem.
ckdb is reloading and will be finished in a the next couple of minutes and then the web site will be all back to where it should be also.
Edit: ckdb back up and running also.
The nonce proxy went rampant and consumed all the system disk
Once I'd detected the problem (it didn't fall inside any of the parameters for an alert until it was too late) I simply killed everything.
The reason behind killing everything (as I've implied before) is that I don't want people mining on a pool that's not giving out work properly.
Killing the pool means everyone should failover to their backups until the problem was sorted out.
No share logging failed since the share log disk is seperate (and a lot larger) than the system disk, so now everything is back up and working, all shares and data will catch back up to everything that happened up to and during the problem.
ckdb is reloading and will be finished in a the next couple of minutes and then the web site will be all back to where it should be also.
Edit: ckdb back up and running also.
Thanks for the update, I am also now able to log back in without been kicked out.
March 07, 2016, 05:19:26 AM
Sorry again - there was a catastrophe caused by the earlier failure that I didn't detect before it basically killed the main server.
The nonce proxy went rampant and consumed all the system disk
Once I'd detected the problem (it didn't fall inside any of the parameters for an alert until it was too late) I simply killed everything.
The reason behind killing everything (as I've implied before) is that I don't want people mining on a pool that's not giving out work properly.
Killing the pool means everyone should failover to their backups until the problem was sorted out.
No share logging failed since the share log disk is seperate (and a lot larger) than the system disk, so now everything is back up and working, all shares and data will catch back up to everything that happened up to and during the problem.
ckdb is reloading and will be finished in a the next couple of minutes and then the web site will be all back to where it should be also.
Edit: ckdb back up and running also.
The nonce proxy went rampant and consumed all the system disk
Once I'd detected the problem (it didn't fall inside any of the parameters for an alert until it was too late) I simply killed everything.
The reason behind killing everything (as I've implied before) is that I don't want people mining on a pool that's not giving out work properly.
Killing the pool means everyone should failover to their backups until the problem was sorted out.
No share logging failed since the share log disk is seperate (and a lot larger) than the system disk, so now everything is back up and working, all shares and data will catch back up to everything that happened up to and during the problem.
ckdb is reloading and will be finished in a the next couple of minutes and then the web site will be all back to where it should be also.
Edit: ckdb back up and running also.
March 07, 2016, 05:08:32 AM
There are some major issues at the moment on the server. As always, make sure you have a backup pool set up. If you have any rentals directed here that you can interrupt, stop them now.
everything failed over here to de.ckpool...
Wish me luck :p
March 07, 2016, 05:04:04 AM
There are some major issues at the moment on the server. As always, make sure you have a backup pool set up. If you have any rentals directed here that you can interrupt, stop them now.
everything failed over here to de.ckpool...
Wish me luck :p
March 07, 2016, 04:46:39 AM
There are some major issues at the moment on the server. As always, make sure you have a backup pool set up. If you have any rentals directed here that you can interrupt, stop them now.
March 07, 2016, 04:41:44 AM
same issue here...
March 07, 2016, 04:28:48 AM
Um 3 little red darth vader helmets in the top left corner of the website and can't log in... Ima go to sleep.
March 07, 2016, 04:20:23 AM
Anyone else miners all stopped submitting shares, also when I login I get kicked out straight away, Kano can you please help, username is Ares on website?
Same issue here. Besides my hashrate on kano.is is zero and the rental on NH seems to be working just fine (status on NH is OK).
Kano can you please check if shares are going through on my account since this way I'm losing BTC. Many thanks.
March 07, 2016, 04:17:10 AM
Anyone else miners all stopped submitting shares, also when I login I get kicked out straight away, Kano can you please help, username is Ares on website?
At least website is having issues atm.
March 07, 2016, 04:15:41 AM
Anyone else miners all stopped submitting shares, also when I login I get kicked out straight away, Kano can you please help, username is Ares on website?
Pool is having some issues as kano posted above. My miners are submitting shares but have the same results as you trying to log in. Just have back up pools on your miners and let kano get things sorted out.
March 07, 2016, 04:07:16 AM
Anyone else miners all stopped submitting shares, also when I login I get kicked out straight away, Kano can you please help, username is Ares on website?
March 07, 2016, 02:20:31 AM
Kano.is having issues? no values! 
Yeah sorry about that - ckdb crashed and also took out ckpool on the way down.Both are back up and running - ckdb just completed it's restart.
Time for some bug tracking down ...
Its not a problem just glad your on top of your game, very much appreciate that
+1
March 07, 2016, 12:51:43 AM
Kano.is having issues? no values!
Yeah sorry about that - ckdb crashed and also took out ckpool on the way down.Both are back up and running - ckdb just completed it's restart.
Time for some bug tracking down ...
Its not a problem just glad your on top of your game, very much appreciate that
March 07, 2016, 12:46:10 AM
Yet another good day mining at Kano.is 
March 07, 2016, 12:44:55 AM
I'm liking these 50% blocks. Please sir, can I have some more?
Me too and fat blocks at that
March 07, 2016, 12:36:26 AM
I'm liking these 50% blocks. Please sir, can I have some more?
March 07, 2016, 12:31:13 AM
Kano.is having issues? no values!
Yeah sorry about that - ckdb crashed and also took out ckpool on the way down.Both are back up and running - ckdb just completed it's restart.
Time for some bug tracking down ...
March 07, 2016, 12:30:43 AM
I had a little hickup but everthing looks fine on my side minus the website.
Jump to: