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

CkMonitor does issue a notice every time your server restarts and is between their 5 minute check-in time.

Kano, do you have memcached running on your site?  how much ram is there?  My strandvision site has a home built ddos system using memcached (so it is fast) that auto slows all non important requests if the server load gets too high.  It also counts hits from each class c ip address range.  If it exceeds the max per minute hits, then the system instantly dies (for that ip address) for a day.  If they do not visit again for a minute, the memory is released.  I do have white lists for paying customers to prevent issues.  Anyway it sounds like you do not have issues with it, but if you do, this type of system does not take long to implement.  PM me if you would like details.

Might be the DDoS/restart?
THt was about 4:10am UTC to 4:35

Same here. Also got a flood of false notifications.

I've been using the CKPool android app for a while too.  Last week I got a whole bunch of block alerts coupled with "your hashrate has dipped below... " alerts... I got really excited that we scored a string of blocks until I realized how unlikely that really was given our luck lately  

Then it just happened again this morning.  Thought we had a block, but nope.  And got the same "your hashrate dipped" alert as well.

App problem, or related to the DDoS reported by Kano, or... ?  

Thanks all.  Still hanging in this pool since I started mining over the summer... I will be sacrificing a TURKEY tomorrow... two in fact... that must count for something!

*Edit:  crikeys, can you tell I really don't post too many messages here?? ha! 

I can only hope we stay at this size for as long as it can be. We will receive less but bigger inputs, making us save on transaction fees. And we still are finding 4 blocks per difficulty, which is good to fight variance, something a 1-2 block per difficulty pool would not be able to do.

I try to block not-nicehash as much as possible since nothing good comes of having miners from there mining here.

Remember that long double block, about half of that hash rate came from there ... so one single source of shares had VERY bad luck ... ... ... not in any way definitive proof ... but I certainly consider it better to stop a single source of horrible bad luck, than to wait to find it's actually 10 blocks of lost blocks and absolutely no recourse if we find it is the cause (they specifically state they will keep the BTC) ... ... ...

I've also blocked an IP of not-nicehash once before that had really bad luck.

The simple problem is that EVERYONE mining on the pool must trust EVERY single physical miner mining through not-nicehash,
Yet mining through not-nicehash has a clear financial advantage for any of them to at least sometimes withhold blocks, in a simple way that they will also never be caught by not-nicehash.
... and those miners pointed at not-nicehash get paid PPS ... which means it doesn't matter if they find blocks or not, they'll still be paid.

We're dealing with a lot of money ... and a lot of people in this world are easily swayed to make decisions that are to their own financial advantage, that may not be to the advantage of others.
To think otherwise is simple foolishness.

Firstly, Cloudflare wont help,
... and I'd have to give them control of my SSL certificate which no one in their right mind would do
who has a site that deals with something of great value.

and of course when was the last time you noticed a DDoS on my web site ... they aren't rare, just rarely have an effect
In this case I just have a command I wrote to deal with it, that doesn't stop anyone using the site except logging in.

I just sent a message to nicehash thread. Would it have anything to do with the insanely high diff they have on our machines.  S9 65536 diff. Lowest Vardiff will drop. Same goes with s3 etc. I have about a 4% loss just in rejects due to high diff also my local work completed showing on s3 since they remove it on s9 is almost double that of accepted shares.  Could this be a problem. A form of inadvertent block withholding. Nicehash being slow to push shares is causing stales etc. just curious

BR

That reminds me when you’ve mentioned Android.  Something about a new risk for Android wallets.  For those that keep the funds there might want to read this.

https://cointelegraph.com/news/major-risk-for-mobile-android-wallet-users

Good night and let’s please crack this block by morning! 

[/quote]Edit: nope, it was the DDoS that caused the crash, I'll disable logins for a while until the DDoS stops.
(yeah it crashed/restarted again - that why I disabled logins)
[/quote]

I just started using the ckpool android app about a week ago. Is it possible the app is being used as part of a DDos attack?
I like the ability to check my hash rate and to get an alert when the pool finds a block. It does check it every 10 minutes or so.
Just wondering. I realize the "distributed" part of the attack means it comes from a lot of different sources, but there is the possibility of over 900 users hitting your pool info at whatever interval the app is set for.

Anyone wondering about the web access in the last 10 minutes,
the DB restarted (unexpectedly) but all ok again now.
I've got the info for the cause and will track it down later.

Also someone is DDoSing the web site so you might get some timeouts - but prolly not since it's only a tiny DDoS
(and the web site doesn't even notice them unless they're sizeable)
(and that's another reason why it doesn't put out a lot of data - since that makes DDoSing it so much easier)

Edit: nope, it was the DDoS that caused the crash, I'll disable logins for a while until the DDoS stops.
(yeah it crashed/restarted again - that why I disabled logins)

Edit2: and it seems to be continuing again (no more DB crashes though) on and off
so you'll find on occasion not being able to login if I'm blocking the DDoS

Same here my man!!! EMBRACE YOSELF!!!!

I got a feeling that we’re about to get a block!  How about you comrades? 

Once we find next block it will show up in your wallet, end of story. 

Thanks for confirming. There is a lot of noise about killing goats, dolls, etc to sift through so after reading a page about that stuff I decided it was easier to just ask.


Thank you as well.

unfortunately 

Read the last couple of pages. The payment will be confirmed in our next block.

I am not showing the last payment in my wallet.

When I check https://blockchain.info/address/35efSwzRYdYFfxy82CgNSTdukd1gStVYEN the last I see are from 11/16/2017.

I have verified that the correct wallet address was used to send the payment.

Block   Address   Status   BTC   
495143   35efSwzRYdYFfxy82CgNSTdukd1gStVYEN       0.00584797   

Did it recently confirm and the payment hasn't been released?

ive got a s9 13.5 and a ebit e9+ 9.5 running on the same worker in and my invalids are only at .065 % is this the norm?