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

[philipma1957]

Well it is my birthday. I wrote I would wait til my birthday to decide what to do.  I wrote this during the deadly December we had.


Monthly Statistics

UTC-- Month----Pool Avg--...Blocks--...Expected---Mean Diff%-----MeanTx%----Luck%---PPS%
2017- Jan-------22.78PHs--..36------...37.10.......103.05%..........105.38%.....97.04%.....101.34%
2016- Dec------.28.63PHs--..41----.....58.65.......143.04%..........105.24........69.91%......72.91%

So we improved from a PPS% of 72.91% to a PPS% of 101.34%

I will stay in place until Feb 28th and make a new assessment.

[GWhisper]

Well it is my birthday.

Happy birthday!

[kano]

In case anyone did, or didn't notice.
The NYA server dropped all the miners at 00:26 UTC - almost an hour ago - it woke me up
The network problem lasted for only about a minute, but that meant all miners failed over and then back ~5 minutes later.
Nothing else was affected, it was local to the NYA server network.

[kano]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

[clgrissom3]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Thanks for continuously looking for ways to improve things...and for keeping us in the loop

[Newko]

Haven't been here for about a week (too busy with other stuff). Just saying hi to my fellow miners.
@Philipma1957  Happy Birthday!
Nice to see the pool luck over 100% - mine on! 

[firetreeactual]

Beatcha! Block there, Sonny... 

[VRobb]

Gotta be fast to beat carl!  Saw a couple payments show up in my wallet, blocktabulous!!

Cheers schmokeandapancake!

[kano]

Beatcha! Block there, Sonny... 

S9v2

[clgrissom3]

Beatcha! Block there, Sonny... 

Haha!  I went to a hockey game tonight...I saw the notification come across my iPhone!

[bit2255]

always good to wake up to good mining news!

[BannedDK]

kano can you see any connection from me at your end? i got a new router and modem setup, but seems i cant send any info to you. my ip is the same.

i got the same name here as on your site

nevermind me.. some lame auto AIprotection the router  has.. works now

[dance191]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Kano, how long are you leaving the old server in Vegas up for?  I have a bunch of things that are hard coded to point to only to the IP address of the old server and need to change everything to the IP address of the new server before that old Vegas server is taken down.  I like to lock everything down as much as possible.

[kano]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Kano, how long are you leaving the old server in Vegas up for?  I have a bunch of things that are hard coded to point to only IPX and need to change everything to IPY before that old Vegas server is taken down.  I like to lock everything down as much as possible.

Using the IP address is a bad idea for anyone.
The new IP address doesn't point to the new server, just to a front end passthru (which uses truck loads of CPU even though it does nothing else, and reports zeros for everything, I guess no one actually ever tested/used it including the developer )
Thus if ever something drastic happens (e.g. like an extended DDoS, which hasn't happened before, or an extended server/provider failure) it's a minor change to move the front end and change the IP address via DNS.

Soon after I complete the changes I'll contact a few of the large miners and give them a 2nd front end whitelisted to allow a second (similar) access.
(i.e. I'll only allow access to that server from a set of IP addresses)
However, of course, there's no guarantee that one could never be DDoSed either, since a large DDoS can affect a whole data center, and of course server failures are always possible.

A redirect to point miners to another frontend, if an outage is known in advance, will fail if you mine to the IP address.
Redirect in cgminer works based on matching your current connection with the redirect, if they don't match, the redirect will be ignored.
e.g. stratum.kano.is => zomg.kano.is would work, but IPADDRESS => zomg.kano.is wont.

You could use a passthru at your data center, and point all your miners to that and then only need to change that if ever anything needed changing.
(Edit: or a straight proxy since that uses a lot less bandwidth and thus means slightly faster block changes for your miners when you have a lot of miners - usually setup as multiple proxies if you have lots of miners, so your miners can failover among them if one ever fails/restarts/whatever, but also, of course, have a final pool failover in the miner pool list)

[kano]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

The process is progressing well.
A few minor issues with the old backend provider, supplying a problematic server for a frontend, so I wont be using them for that ever again (i.e. none of the new servers are from them)

As I've already mentioned, I've pointed the DNS to a new frontend for mining.
When I change the backend over to the new one in the next 24-36 hours, I'll simply modify where it sends/gets it's work so, of course, no one will need to change anything when I do that, but as mentioned above, there will be about a 5 minute mining outage when that happens.

I'm also setting up (almost done) a new front end server to the web site - the 2nd new server mentioned above.
That will be done before the final change over.
It will also be able to be easily switched from getting data from the old server to the new server when the change over occurs.
Web/API access will probably be a longer outage when the changeover occurs, since there's 2 steps, the back end move, and then a ckdb restart (or 2) which adds another 5-10 minutes to the outage.
i.e. it could be up to a 15 minute web/api outage when I do the final change.

[beltsniffer]

Over an hour since the last network block. Sure would be nice to get this one with all those fees out there!  

Come on Blocks!

[dance191]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Kano, how long are you leaving the old server in Vegas up for?  I have a bunch of things that are hard coded to point to only to the IP address of the old server and need to change everything to the IP address of the new server before that old Vegas server is taken down.  I like to lock everything down as much as possible.

Kano, while I appreciate that you think using an IP isn't the way to do it (in general DNS is a much easier way to propagate any IP address changes), please realize it is what works best for my setup.  If, for nothing else the firewalls I use restrict by IP address only, and I assume you agree that people should use firewalls.  So, let me ask again, Kano, how long are you leaving the old server in Vegas up for?

[kano]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Kano, how long are you leaving the old server in Vegas up for?  I have a bunch of things that are hard coded to point to only to the IP address of the old server and need to change everything to the IP address of the new server before that old Vegas server is taken down.  I like to lock everything down as much as possible.

Kano, while I appreciate that you think using an IP isn't the way to do it (in general DNS is a much easier way to propagate any IP address changes), please realize it is what works best for my setup.  If, for nothing else the firewalls I use restrict by IP address only, and I assume you agree that people should use firewalls.  So, let me ask again, Kano, how long are you leaving the old server in Vegas up for?

24-36 hours
They can't both run.

So basically you are saying you cannot access any sort of DNS where your miners are?
I guess point it at the IP of the new passthru.
If that ever changes, then you'll have to change it again.

[dance191]

I'm rearranging the server layout.

Anyone paying close attention will notice some time over the next day, that if they reconnect, they will move from pointing to LasVegas, to pointing to LosAngeles.

It's a new front end server for the pool and will simplify the next change.

That being: the back end pool will be moving in the next 2 days.
When I move the back end there is likely to be a mining outage of up to 5 minutes.
I'll post more about the changes before they happen.

If you mine to nodes, you'll see no changes.
If you mine to the main pool in LasVegas, you'll see a change to LosAngeles.
The difference is about 8ms between the 2, so nothing major (or slightly better depending on where you are)

Edit: and in case anyone was wondering - it's an upgrade, not a down grade, a better back end server and 2 more servers in front of it

Kano, how long are you leaving the old server in Vegas up for?  I have a bunch of things that are hard coded to point to only to the IP address of the old server and need to change everything to the IP address of the new server before that old Vegas server is taken down.  I like to lock everything down as much as possible.

Kano, while I appreciate that you think using an IP isn't the way to do it (in general DNS is a much easier way to propagate any IP address changes), please realize it is what works best for my setup.  If, for nothing else the firewalls I use restrict by IP address only, and I assume you agree that people should use firewalls.  So, let me ask again, Kano, how long are you leaving the old server in Vegas up for?

24-36 hours
They can't both run.

So basically you are saying you cannot access any sort of DNS where your miners are?
I guess point it at the IP of the new passthru.
If that ever changes, then you'll have to change it again.

Thank you for the info, I will get on changing things over to the new IP address in the next 24 hours.  

The problem with using DNS is the firewalls I use only allow rules using an IP address.  So in a way, yes, I can not use DNS where the miners are as the firewalls do not use DNS (only IP addresses).  100% understood that if you change stratum.kano.is to point to a new IP address then I will need to update it again.

Thanks again for the info!

[-EOS-]

Thank you for the info, I will get on changing things over to the new IP address in the next 24 hours.  

The problem with using DNS is the firewalls I use only allow rules using an IP address.  So in a way, yes, I can not use DNS where the miners are as the firewalls do not use DNS (only IP addresses).  100% understood that if you change stratum.kano.is to point to a new IP address then I will need to update it again.

Thanks again for the info!

Since the firewall you use only works with IP addresses in the rules, maybe allow your miners to 8.8.8.8 and 8.8.4.4 port 53 for DNS?  Set your miners DNS to those 2 IP's, then you wouldn't have to worry next time an IP changes.  Just throwing out options for you..