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

[ryen123]

What actually are you mining with and what's your username - (PM me if you want)
There's only a few users on the SG server that make up the ~135TH on there.

If you are running linux then do the following 2:

Code:

mtr --report sg.kano.is
mtr --report stratum.kano.is

Also if you swap to the main pool stratum.kano.is does that make any difference?

My userID is MiningAsia. Running Knc Neptune (only 2 cubes out of 5, cgminer 4.9.1). Running windows so can't test those commands.
Now mining at main pool (stratum.kano.is), everything running normal.

My config:
[Main pool]: sg.kano.is:3333
[Failover 1]: stratum.kano.is:3333
[Failover 2]: de.kano.is:3333

[stonebone]

What actually are you mining with and what's your username - (PM me if you want)
There's only a few users on the SG server that make up the ~135TH on there.

If you are running linux then do the following 2:

Code:

mtr --report sg.kano.is
mtr --report stratum.kano.is

Also if you swap to the main pool stratum.kano.is does that make any difference?

My userID is MiningAsia. Running Knc Neptune (only 2 cubes out of 5, cgminer 4.9.1). Running windows so can't test those commands.
Now mining at main pool (stratum.kano.is), everything running normal.

My config:
[Main pool]: sg.kano.is:3333
[Failover 1]: stratum.kano.is:3333
[Failover 2]: de.kano.is:3333

Sure you can...
http://winmtr.net/download-winmtr/

[ryen123]

@kano Managed to use my router to do a traceroute

Code:

traceroute to sg.kano.is (139.162.5.112), 30 hops max, 38 byte packets
 1  172.22.0.1 (172.22.0.1)  2.842 ms  3.574 ms  2.809 ms
 2  103-6-148-37.myrepublic.com.sg (103.6.148.37)  1.739 ms  2.184 ms  2.830 ms
 3  103-6-148-13.myrepublic.com.sg (103.6.148.13)  3.231 ms  2.129 ms  3.587 ms
 4  63949.sgw.equinix.com (202.79.197.235)  169.505 ms  171.319 ms  170.766 ms
 5  139.162.0.6 (139.162.0.6)  166.933 ms  167.413 ms  169.022 ms
 6  sg.kano.is (139.162.5.112)  169.502 ms  168.508 ms  167.880 ms

Code:

traceroute to stratum.kano.is (104.194.28.194), 30 hops max, 38 byte packets
 1  172.22.0.1 (172.22.0.1)  3.048 ms  2.251 ms  3.202 ms
 2  103-6-148-37.myrepublic.com.sg (103.6.148.37)  2.343 ms  1.684 ms  2.764 ms
 3  103-6-148-13.myrepublic.com.sg (103.6.148.13)  4.152 ms  2.756 ms  2.084 ms
 4  116.51.27.101 (116.51.27.101)  4.736 ms  5.488 ms  5.953 ms
 5  ae-1.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.146)  2.968 ms  4.664 ms  3.836 ms
 6  ae-8.r22.osakjp02.jp.bb.gin.ntt.net (129.250.3.109)  78.554 ms  84.637 ms  83.794 ms
 7  ae-8.r21.osakjp02.jp.bb.gin.ntt.net (129.250.6.193)  75.030 ms  88.953 ms  76.144 ms
 8  ae-4.r22.lsanca07.us.bb.gin.ntt.net (129.250.2.176)  193.132 ms  180.175 ms  188.132 ms
 9  ae-1.r00.lsanca07.us.bb.gin.ntt.net (129.250.3.17)  184.719 ms  182.881 ms  190.035 ms
10  xe-0-0-0-32.r00.lsanca07.us.ce.gin.ntt.net (129.250.202.38)  185.079 ms  189.353 ms  179.787 ms
11  192.228.109.50 (192.228.109.50)  175.558 ms  184.272 ms  178.243 ms

My miner has automatically switched back to the SG node. Seems to be running normal now.

[kano]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

[citronick]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Hi Kano,

SOS.

Pools are showing UP.

But no hashes reported at worker's page.

Email notification for low hash rates are coming in furiously.

The thing is my miners are NOT failing over.

I am tempted to reboot the all the miners....

[ryen123]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Yeah maybe jus a gremlin somewhere on the local national network. SG node was running fine for me since I connected to. No worries.
Thanks kano.

[citronick]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Hi Kano,

SOS.

Pools are showing UP.

But no hashes reported at worker's page.

Email notification for low hash rates are coming in furiously.

The thing is my miners are NOT failing over.

I am tempted to reboot the all the miners....

UPDATE:
1. rebooting seems to be working.
2. reverting to kano usa for the time being
3. total hash affected about 30+

TO INVESTIGATED:
4. miners are hashing but nothing appears on workers page.
5. pool failover did not trigger

I am not near my rigs now, so I will use kano usa temporarily until i get back home.

[gupik65]

I registered in( de.kano.is) miner, he is closer to me but for some reason he flew back and when it began to fall into place in the miner and the rate did not rise, though the second prescribed kano.is, what is the reason that the rate has not risen and fallen when he moved to de ?(
I am living in Ukraine)

[PPKi]

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Kano, do you plan to update "Mining configuration:" section on your main site https://kano.is/index.php when DE/SG nodes tests will be finished?

I want to switch to DE node, but only after I am sure about stability.

Thx for your work.

[yslyung]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Hi Kano,

SOS.

Pools are showing UP.

But no hashes reported at worker's page.

Email notification for low hash rates are coming in furiously.

The thing is my miners are NOT failing over.

I am tempted to reboot the all the miners....

same issue, rebooted then ok, miners did not failover.

fixed now.

if sg dc server give prob, we send cit to go dc n smack that server !

[zahzin]

I registered in( de.kano.is) miner, he is closer to me but for some reason he flew back and when it began to fall into place in the miner and the rate did not rise, though the second prescribed kano.is, what is the reason that the rate has not risen and fallen when he moved to de ?(
I am living in Ukraine)

Hmm weird, as I am connecting from Finland, and started using DE server since I had way much better ping there, but my hashrate was way down compared to using the main USA server which had 100ms worse ping for me compared to DE server..

For some reason I get much better hashrate using the main server so gonna use that for now..

Edit: Hmm even the main server gives slightly lower hashrate than it used to, no idea why, even though its better than DE.

Have to try mine a bit on solo pool to see if its miner related or not..

[-ck]

Hmm weird, as I am connecting from Finland, and started using DE server since I had way much better ping there, but my hashrate was way down compared to using the main USA server which had 100ms worse ping for me compared to DE server..

For some reason I get much better hashrate using the main server so gonna use that for now..

Not sure how the node choice can affect hashrate of all things (i.e. it shouldn't have any bearing at all)... Are you looking at the "share rate" instead of the "hash rate" for your workers? The former will vary wildly, especially immediately after a network block change and doesn't mean your actual hashrate is higher or lower.

[kano]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Hi Kano,

SOS.

Pools are showing UP.

But no hashes reported at worker's page.

Email notification for low hash rates are coming in furiously.

The thing is my miners are NOT failing over.

I am tempted to reboot the all the miners....

UPDATE:
1. rebooting seems to be working.
2. reverting to kano usa for the time being
3. total hash affected about 30+

TO INVESTIGATED:
4. miners are hashing but nothing appears on workers page.
5. pool failover did not trigger

I am not near my rigs now, so I will use kano usa temporarily until i get back home.

Yeah as I said to ryen123, I'd need an mtr output to see what's up.
The SG node is on Linode and Linode have had a lot of DDoS trouble in the recent weeks.
That could be related, but again nothing went wrong for most of the miners.

If the node is dead and everyone is down then yep that means it certainly the server.
A partial outage will of course mean it's the network 'somewhere'

But in both of the other cases, it just started working again 45 minutes later for no reason, so yeah it was most likely their network.

[gupik65]

So it is better to choose the server which is close

[citronick]

Yeah had (exactly) the same problem with someone else also.
I'm wondering if there was a network issue in SG somewhere?
(that fixed itself)

SG hash rate stayed up about 87TH but that meant of course there was a drop out of about 30TH (you and the other person)
I'm always connected (from Aus) and there was no drop out from here either.

I guess we'll have to see if it happens again, and make sure you run an mtr/traceroute

Hi Kano,

SOS.

Pools are showing UP.

But no hashes reported at worker's page.

Email notification for low hash rates are coming in furiously.

The thing is my miners are NOT failing over.

I am tempted to reboot the all the miners....

same issue, rebooted then ok, miners did not failover.

fixed now.

if sg dc server give prob, we send cit to go dc n smack that server !

yeah, I am only 3-5ms away from the exchange, I will jog there and give it a good kick  

[ryen123]

yeah, I am only 3-5ms away from the exchange, I will jog there and give it a good kick  

Buy the server a packet of kopi-o. It might be feeling tired, need a different type of kick.

[zahzin]

Hmm weird, as I am connecting from Finland, and started using DE server since I had way much better ping there, but my hashrate was way down compared to using the main USA server which had 100ms worse ping for me compared to DE server..

For some reason I get much better hashrate using the main server so gonna use that for now..

Not sure how the node choice can affect hashrate of all things (i.e. it shouldn't have any bearing at all)... Are you looking at the "share rate" instead of the "hash rate" for your workers? The former will vary wildly, especially immediately after a network block change and doesn't mean your actual hashrate is higher or lower.

Hmm seems it may be the miner (S2) fault as for some reason when I have Kano DE as primary and Kano USA as secondary, it sometimes hops to the USA server for a second and the S2 does not like that and I start getting more HW errors when it does that until I reboot it.. Also tried removing the secondary option which helped a bit, but still I see I am getting better hashrate on the Solo DE pool compared to what the hashrate was on either the main USA kano server or the new DE kano server.. Weird.. Might be just me though..

[kano]

Hash rate varies.

Look at your Workers->Shift Graph.

That varies up and down all the time.

If you are seeing some hash rate that seems low, then post a Workers->Shift Graph
And make sure it doesn't look like most of them, full of up and down blue lines

Any outage will of course affect the shift when you had the outage.
That will be obvious by a shift that's low and then it goes back up.

[zahzin]

Will test a bit longer and report back when I have something more substantial

[gupik65]

Make to consistently work to do(de.kano.is)and then falls off