Author

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

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
kano and ckpool down?

Update: Failover has been triggered. This includes the sg node and us node.
Anybody can reconfirm?
Yep a DDoS attack.
Effective for about 40 minutes.
It's still on going but next to no effect on the pool any more.
Pool is back up to 8.8P at this point.

I was mentioning in IRC about working on more mitigation of this sort of issue tomorrow ... looks like they got in a day early.

Anyway, mining is all back ok again (for about 25 minutes now)

Kano, could services like CloudFlare or similar help here? 
No, since redirecting via someone else's service adds latency.
Mining is all about latency and block change times.

We minimise those on kano.is and Solo CKpool and adding that latency back in permanently would obviously not be ideal at all.

Quote
... working on more mitigation of this sort of issue tomorrow ...
legendary
Activity: 1726
Merit: 1018
Last time this happened the failover part worked (and it did again today) but the failback part hosed one of my S7's.  Hopefully when we failback today I'll have better luck.  I'm not in a place where I can power cycle the miner today.
Looks like smooth failback on all s7's

In the last ddos, some of my S7 (the earlier batch) did not failback when kano came up again - I since then patched all with the Dec FW - and it seems to work nicely during this outage.

I haven't touched the firmware on mine but it failedback fine this time.


There is no pattern to luck.
You cannot predict luck.
Anyone who thinks they can, is deluded.

I don't want to put words in your mouth but it almost sounds like you are suggesting that eating chicken has no effect on finding blocks...

If the pool crashes due to an attack or fails .we as the miners should not be punished for downtime , that said is there some way around that , saying that if the pool crashes for 45 min, s our 5nd is shot out of the sky .

Nobody is punished.  If your 5ND was lowered then everyone else's will have been lowered in the exact same way.  Your share as a percentage of the pool is the same as ever.  As long as you have a backup pool then the shares you "lost" here will be paid there.
legendary
Activity: 2464
Merit: 1710
Electrical engineer. Mining since 2014.
If the pool crashes due to an attack or fails .we as the miners should not be punished for downtime , that said is there some way around that , saying that if the pool crashes for 45 min, s our 5nd is shot out of the sky .
Miners are totally responsible for their own mining in my opinion.
My rigs changed automatically to Eligius for the down time.
You can't prepare 100% against DDOS attacks like these.
newbie
Activity: 28
Merit: 0
kano and ckpool down?

Update: Failover has been triggered. This includes the sg node and us node.
Anybody can reconfirm?
Yep a DDoS attack.
Effective for about 40 minutes.
It's still on going but next to no effect on the pool any more.
Pool is back up to 8.8P at this point.

I was mentioning in IRC about working on more mitigation of this sort of issue tomorrow ... looks like they got in a day early.

Anyway, mining is all back ok again (for about 25 minutes now)

Kano, could services like CloudFlare or similar help against DDOS attacks?
legendary
Activity: 1694
Merit: 1002
Go Big or Go Home.....
I don't think you lose all your 5n shares, only the time you could not submit to the pool.
wcg
newbie
Activity: 31
Merit: 0
If the pool crashes due to an attack or fails .we as the miners should not be punished for downtime , that said is there some way around that , saying that if the pool crashes for 45 min, s our 5nd is shot out of the sky .
legendary
Activity: 1260
Merit: 1006
Mine for a Bit
I am hoping that we do not hit a block for a little while.  On my Workers page my "Hash Rate" is far less than my "Share Rate" due to downtime.  It took me some time to reset each of my miners individually.  I do believe that this effects my overall 5Nd rate; therefore, my payout.
Yes, shares not sent will not be paid.

The pool got very few if any shares for about 40 minutes.
Outside those 40 minutes, the hash rate was normal before and back to normal soon after.

If your miners have problems failing over, then you need to get that fixed.
I cannot guarantee (nor can anyone else) 100% pool uptime.


Kano, I have to give you a lot of respect for answering honestly about the issues.  This is a BIG positive about this site.  Thanks!
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I am hoping that we do not hit a block for a little while.  On my Workers page my "Hash Rate" is far less than my "Share Rate" due to downtime.  It took me some time to reset each of my miners individually.  I do believe that this effects my overall 5Nd rate; therefore, my payout.
Yes, shares not sent will not be paid.

The pool got very few if any shares for about 40 minutes.
Outside those 40 minutes, the hash rate was normal before and back to normal soon after.

If your miners have problems failing over, then you need to get that fixed.
I cannot guarantee (nor can anyone else) 100% pool uptime.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
No you can't hop the pool and expect to gain.
It has exactly the same effect as not hopping the pool. Luck decides.
You chances of hitting a lucky run are no better or worse than your chances of hitting an unlucky run.

The simple fact is that each share is paid exactly the same as every other share ignoring luck.
There is no pattern to luck.
You cannot predict luck.
Anyone who thinks they can, is deluded.
legendary
Activity: 1260
Merit: 1006
Mine for a Bit
I am hoping that we do not hit a block for a little while.  On my Workers page my "Hash Rate" is far less than my "Share Rate" due to downtime.  It took me some time to reset each of my miners individually.  I do believe that this effects my overall 5Nd rate; therefore, my payout.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
After such a stellar run Friday we are going to be due for some nasty red blocks.  Hopefully not too many, but it is a certainty that they will happen.

Yes dont let them fool you.. there is a def pattern to this. And most pool ops will tell you that its bs. but there most concern is that it hurts the loyal miners those that hop on pools and hop off.  You can gain quite an advantage doing this if your lucky. Maybe its a bit of a gamble but last i checked this whole bitcoin experiment is one hell of a gamble.. I say do what you wish.. Just know the consequences of hopping on and off pools.>

http://bitcoin.atspace.com/poolcheating.pdf
https://bitcoil.co.il/pool_analysis.pdf
https://en.wikipedia.org/wiki/Poisson_distribution
https://en.wikipedia.org/wiki/Erlang_distribution
 

some of the resources im using to base my research..

If Kano put the 50, 100 block and 200 block sma  Wink on his charts im sure some could easily hop this pool aswell  prolly could easily with the 25 the way it  looks Smiley
https://kano.is/index.php?k=luck

Best Regards
d57heinz
full member
Activity: 162
Merit: 100
----I had all of my miners pointed to CKPool.  When CKPool went down, all of my miners split their efforts between the pools I have on my miner control. When CKPool came back up, I had to go into each individual miner and reset them.  Is there a better way to reset all of them so that they will go back to CKPool?----
You can make batch file that will reset them all at once. I did that for my s4, havent tried on s7 but im sure that will work.
https://bitcointalksearch.org/topic/m.10462772
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I'm still having trouble reconnecting stably to the pool.
Well the pool is sitting happily at 8.8P at the moment
The ddos was (is still going) a router attack that uses the routers of bazillions of people unknowingly.
My only suggestion would be to check your router also.
I don't know the models involved though.
full member
Activity: 184
Merit: 100
btw..... the S7 beeping all at the same time was a scary affair because it's past midnight in this part of the world.

Any recommendations to soften the sound of the beeps - ie. not completely cut the speaker off - but perhaps cover the hole where the beep is coming from. Someone suggested "superglue" to cover the pinhole of the speaker - has anyone tried this yet? Ideally muting the beep via config panel is best.

https://bitcointalksearch.org/topic/m.12982754

i did it, it works Smiley
legendary
Activity: 1694
Merit: 1002
Go Big or Go Home.....
I'm still having trouble reconnecting stably to the pool.
full member
Activity: 157
Merit: 103
btw..... the S7 beeping all at the same time was a scary affair because it's past midnight in this part of the world.

Any recommendations to soften the sound of the beeps - ie. not completely cut the speaker off - but perhaps cover the hole where the beep is coming from. Someone suggested "superglue" to cover the pinhole of the speaker - has anyone tried this yet? Ideally muting the beep via config panel is best.
Superglue will not help I guess... But 'hot melting glue' will do.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
----I had all of my miners pointed to CKPool.  When CKPool went down, all of my miners split their efforts between the pools I have on my miner control. When CKPool came back up, I had to go into each individual miner and reset them.  Is there a better way to reset all of them so that they will go back to CKPool?----

have patched the s7s with Dec11 FW?

it worked nicely for me during failover and failback.

during the previous ddos attack, most of my earlier batch s7s, had problems falling-back, and I had to reboot them manually.
sr. member
Activity: 751
Merit: 253
Just FYI,

I am running all my miners thru the latest version of ckpool   via ckpool -P and everything failed ovr and back without any problems. 

that was not the case with previous versions of ckpool.

If you are not familiar with ckpool software, look at one of the first few posts of this thread.
full member
Activity: 184
Merit: 100
turn it off, ill edit this when i find the guide
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
btw..... the S7 beeping all at the same time was a scary affair because it's past midnight in this part of the world.

Any recommendations to soften the sound of the beeps - ie. not completely cut the speaker off - but perhaps cover the hole where the beep is coming from. Someone suggested "superglue" to cover the pinhole of the speaker - has anyone tried this yet? Ideally muting the beep via config panel is best.
Jump to: