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

bitminter.com and solo.ckpool.org

just curious, what back up pools do you use guys?
im new in mining and had all pointed to kano; lesson learnt but  not sure which would be the best option
thanks

OK, everything should be all good now ... I'll update this post with more details shortly ...

Firstly the DDoS:
It started about 20 minutes after the block - at approximately (29th) 18:54 UTC
It was effective for almost 40 minutes.
According to the data centre, it was too small to trigger the base DDoS protection so until they manually intervened it was successful.

I'll look into their "more expensive" option to make it "always work" ... ... ... yeah even writing that sentence myself makes me wonder what that means ... ... ...


Server down time:
I was able to get into the server while the DDoS was happening due to how I have certain things configured ... details withheld
I actually shut everything down on the server, upgraded everything, rebooted the server and started all back up.
I started this (coincidentally) just at the end of the DDoS so although some miners may have eventually connected towards the end of the DDoS, they will have been disconnected shortly after.
Taking everything down correctly in order, upgrading everything, rebooting and restarting everything in order took me about half an hour - so I now know that time length, for future reference, if I need to plan that (ahead) some time in the distant future.

The dependency on each process starting and connecting is such that I prefer that all to be a manual process so I know that the final step of ckpool starting means that all miners will be mining valid work and not throwing hashes away.
There are all sorts of possible problems with starting everything automatically that I prefer to not have mining available until I'm sure it is all OK.
If it hasn't been obvious in the past, I will say it clearly, if the pool isn't running with up-to-date work and a good connection to bitcoin, I don't want miners connected risking wasting their hashes, thus on such occasions I would be stopping the main pool service until it's resolved and not allowing connections.
I don't expect this to happen, or if ever, only for a short time, but that's how I prefer to run it and that's also why (like on any pool) you should always have backup pools.

All should be good now (for the last 35 minutes)
If anyone has any problems connecting - of course let me know - or PM me with your account details

Edit: I've also updated the coinbase payout addresses since it's been more than 100 blocks since the last time I did that.

Well after the attack my s5 no longer wants to respond of course it's remote and can't gain access as I'm on my way out of town for the New Years. Guess I need to point one of my solo miners there to hash.

I have 1 B8 among those, it came with Dec 3 firmware but I upgraded to Dec 11 and it switched fine (currently at sidehack's place).

I took this unscheduled downtime to upgrade the firmware of my B8, since someone mentioned that the latest firmware failed over correctly.

My other batches switched fine, only had trouble with B8. B8's controller is different to all previous batches.

I had 2 batch 5 s7's drop at my second farm.  Drove 10 miles to power cycle them.  Might be time for some IP PDU's

My 6 S7s with Dec firmware and A6 switched back to Kano with no issues.

The only thing submitting shares that are not blocks is doing is proving to the pool that you have a certain amount of hashrate working on finding bocks so you can be compensated for your efforts.  If you have a lot of hashrate then it doesn't make sense to have you submit difficulty 1 shares because it just creates a lot of unnecessary traffic to the mining server.  So the more hashrate you have, the more often you can submit higher difficulty shares.  So the mining server strikes a balance and figures out how high the difficulty should be in order to have you submit the desired number of shares in a given period of time.

The difficulty refers to the number of leading zeros on the hash.  If you look at a block hash like this for instance: https://blockchain.info/block-index/1004980
You see a bunch of zeros on the front of the hash (looks like about 17 right now).  When you generate hashes the actual hash is more or less random so the odds of having a lot of zeros on the front is low.  The more zeros you require at the front the lower the odds get of finding a hash like that (hence the difficulty).  It's not technically all zeros, otherwise difficulty jumps would be fixed numbers but you get the idea.  In order to prove to the pool that my miners are working and that I have a given amount of hashrate I may submit shares that have 7 leading zeros for example, depending on what difficulty my miners are working at.

The reason a pool doesn't really know your hashrate and that it can appear off on the pool side is because the pool just uses the number of shares you submit of a given difficulty over a given period of time to calculate your hashrate.  Then it pays you based on that calculation.  But since hashes are more or less random sometimes your miner might find more or less of a given difficulty share in a given period of time.  Long term those fluctuations even out.  Working at a lower difficulty would even out those fluctuations but create more traffic to the mining server.  Working at a higher difficulty would reduce traffic to the server but create even greater fluctuations in the calculated hashrate.  So the mining server needs to find the sweet spot in terms of what difficulty is best to set an acceptable amount of traffic and still allow a fairly accurate measure of your real hashrate.

it is odd that they would change up ck cgminer when it works fine without modification. Maybe someone here knows why they would do such a thing??  My thought are the crappy controller they use cant handle full version cgminer. any thoughts?

Best Regards
d57heinz

What good is ddos mitigation if doesn't work

OK, everthing should be all good now ... I'll update this post with more details shortly ...

My B8 also shit the bed. Fucking garbage company that bitmain is.... Why can't they get software right?  

S7 with December firmware switched to backup with no probs, no actions required.

has anybody fail back yet

Two  of my three miners failed over properly , but all the shares of the third are being rejected.

i bet bitmain used the same crappy bugged cgminer for the s7 that they used for all the other models...

Same here, took out a batch 8 S7, does not reposed and can't ping. I'm not local to it, so could be a day out so before I can power cycle it. Bummer

Still no luck here :/ Site says mining all okay but still dead for me.