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

[baazju]

I'm back up on all my miners.


kano is up on irc so he is aware.

[citronick]

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.

[wolfen]

Glad I went with dec 11. All on dec 11 since dec 11

[d57heinz]

well here is the issue.. not too sure a ddos causes that..

Shift               Start UTC   Length   Your Diff   Inv Diff      Avg Hs       Shares   Avg Share   Rewards   Rewarded*   PPS%
5trpu rika   Jan-10 16:54:32   47m 1s   14.588k   0               22.21GHs   14   1,042.00   0   0   0.00%

14 shares submitted in 47 ming with 22 th/s

Theres the issue.

Maybe a pool crash. idk

edit>>  so i checked my backup pool.. seems it was down for over 45 min. so that shift is correct i presume.   Whats odd is 5 of my miners are showing alive on kano. but hashing at 0.. Cpu load on the antminer is 2.87  not sure what kind of glitch gets thrown to the miners that they wont all failover.   these were on s3 miners


BEst Regards
d57heinz

[wolfen]

Have all miners at 60% manual. I think that helped keep the hardware stable as opposed to the last ddos when they were auto.
Took out 4 that time, had to power cycle.

[kano]

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)

[wolfen]

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)

Excellent Kano

[AriesIV10]

----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?----

[altcointalk14]

So is  

De.Ckpool.org  

the backup we should use?

[citronick]

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.

[left-ca]

turn it off, ill edit this when i find the guide

[altcointalk14]

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.

[citronick]

----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.

[e46btc]

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.

[thedreamer]

I'm still having trouble reconnecting stably to the pool.

[left-ca]

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://asktom.cf/index.php?topic=1165628.msg12982754#msg12982754

i did it, it works

[kano]

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.

[bittalc1]

----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://asktom.cf/index.php?topic=956098.msg10462772#msg10462772

[d57heinz]

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  on his charts im sure some could easily hop this pool aswell  prolly could easily with the 25 the way it  looks
https://kano.is/index.php?k=luck

Best Regards
d57heinz

[AriesIV10]

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.