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

The DE server is currently 155TH and until I hear problems from anyone regarding that one, all seems OK with it.
(Same with DE, I'm always connected and a USB miner submitting shares)

Many miners from Ukraine and Russia are experiencing the loss of a server,Off. , what is the reason?

Confirmed, DE server works perfect. Changed all except 1 miner from the main to the DE server yesterday, no issues, same hashrate.

It (currently) shows the last block, just no others.

The last block is, of course, the right hand edge of the red area.

OK, well it seems that a few (not all) people are having trouble with the SG server.
Again it's almost certainly some network issue in singapore since there's still 90TH of miners on there submitting shares
(and I'm always connected and submitting shares and not having drop outs either)

If you are having any trouble with the SG server, then for now I'll say you will need to point to the main node or DE.
Preferably the main node to see if the problems reappear or not.

I'm not gonna stop the SG node right now since, as I said, there's 90TH of miners, and they appear to be working OK.

Also the mtr needs to be run at the exact time you are having connections problems.

--

The DE server is currently 155TH and until I hear problems from anyone regarding that one, all seems OK with it.
(Same with DE, I'm always connected and a USB miner submitting shares)

I'm basically just letting the SG server go as it pleases and as long as the DE server is OK we can be pretty sure the SG problems aren't the node, but the network.

The Worker Shift Graph is awesome.  I wished I knew more about it before.  I'm glad I saw the example above before which shows that timeline exist not just the default of A-Z at the bottom.  I didn't even know Timeline was available so when I first saw this graph, I didn't think it was that helpful.  After I saw the example above with timeline, I started playing around with it and this helps give a much better view of my workers 5ND status and the dips and all that affects my 5ND status.  Definitely much easier to understand from a historic basis then just the normal Workers status.  If would be even more awesome if we can have a Giant DOT on the time where a BLOCK is found so we can match it to our reward status average for that point in time. 

@Kano I'm starting to get these issues again from SG node.

"Accepted untracked stratum share from pool 0"
"Lost x shares due to no stratum share response from pool 0"

Current traceroute snapshot.

The screen-grab as follows - hope it helps in your trouble shooting




X1 is a rental.

11.5 th spike early this morning
Looking for that sequential 3 block hit

that's what happened to my rigs today - dropped for about an hour before I saw the email and phone alerts.
Failover did not kick in because the miners are still able to ping sg.kano but it seems the node is not sending the hashes back to kano@US

the traceroute as follows:

traceroute to sg.kano.is (139.162.5.112), 64 hops max, 52 byte packets
 1  192.168.1.254 (192.168.1.254)  0.889 ms  0.419 ms  0.603 ms
 2  bb116-15-160-254.singnet.com.sg (116.15.160.254)  3.125 ms  2.538 ms  1.730 ms
 3  202.166.126.218 (202.166.126.218)  4.167 ms  2.103 ms  2.051 ms
 4  202.166.126.217 (202.166.126.217)  1.963 ms  2.013 ms  1.930 ms
 5  ae8-0.qt-cr03.singnet.com.sg (202.166.121.101)  2.195 ms  2.011 ms  1.992 ms
 6  ae12-0.qt-er05.singnet.com.sg (202.166.120.221)  2.111 ms  2.237 ms  2.076 ms
 7  202.166.126.114 (202.166.126.114)  2.188 ms  2.228 ms  2.483 ms
 8  ge-8-2-0.cityhall.singnet.com.sg (165.21.12.79)  2.706 ms  2.593 ms  2.686 ms
 9  ip-202-147-32-126.asianetcom.net (202.147.32.126)  2.886 ms  2.817 ms  2.993 ms
10  te0-0-2-0.wr1.sin0.asianetcom.net (61.14.157.109)  6.540 ms  5.261 ms  3.562 ms
11  xe-0-1-1.gw1.sin2.pacnet.net (202.147.52.64)  3.911 ms  3.789 ms  3.623 ms
12  gw2.sin1.sg.linode.com (61.14.147.179)  4.161 ms  3.960 ms
    gw1.sin1.sg.linode.com (61.14.147.177)  37.366 ms
13  139.162.0.2 (139.162.0.2)  38.929 ms
    139.162.0.6 (139.162.0.6)  36.217 ms
    139.162.0.2 (139.162.0.2)  38.780 ms
14  sg.kano.is (139.162.5.112)  3.890 ms  3.706 ms  3.977 ms

**************

traceroute to stratum.kano.is (104.194.28.194), 64 hops max, 52 byte packets
 1  192.168.1.254 (192.168.1.254)  0.850 ms  0.462 ms  0.571 ms
 2  bb116-15-160-254.singnet.com.sg (116.15.160.254)  2.392 ms  3.199 ms  2.719 ms
 3  202.166.126.218 (202.166.126.218)  3.962 ms  2.249 ms  2.409 ms
 4  202.166.126.217 (202.166.126.217)  1.960 ms  1.771 ms  2.010 ms
 5  ae8-0.qt-cr03.singnet.com.sg (202.166.121.101)  2.301 ms  1.868 ms  1.760 ms
 6  ae6-0.singha.singnet.com.sg (202.166.120.186)  2.412 ms  2.643 ms  2.424 ms
 7  ae5-0.beck.singnet.com.sg (202.166.126.41)  2.631 ms  2.395 ms  2.320 ms
 8  203.208.174.57 (203.208.174.57)  2.257 ms  2.299 ms  2.322 ms
 9  203.208.171.242 (203.208.171.242)  37.038 ms
    203.208.151.234 (203.208.151.234)  2.503 ms
    203.208.152.106 (203.208.152.106)  2.711 ms
10  203.208.183.46 (203.208.183.46)  191.466 ms
    203.208.182.130 (203.208.182.130)  196.311 ms
    203.208.182.122 (203.208.182.122)  182.413 ms
11  203.208.172.242 (203.208.172.242)  183.375 ms
    203.208.172.246 (203.208.172.246)  185.579 ms
    203.208.172.242 (203.208.172.242)  186.567 ms
12  30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20)  178.776 ms  182.436 ms  195.184 ms
13  10ge4-1.core1.sjc2.he.net (72.52.92.70)  177.419 ms  184.386 ms  192.777 ms
14  10ge13-3.core1.lax2.he.net (184.105.213.5)  223.580 ms  243.606 ms
    100ge13-2.core1.lax1.he.net (184.105.223.250)  193.237 ms
15  100ge11-1.core1.lax2.he.net (72.52.92.122)  201.643 ms  198.710 ms  188.158 ms
16  216.218.200.10 (216.218.200.10)  220.361 ms  222.776 ms  224.785 ms
17  192.228.109.50 (192.228.109.50)  209.702 ms
    64.62.249.90 (64.62.249.90)  210.546 ms  208.894 ms
18  192.228.109.50 (192.228.109.50)  204.860 ms  214.114 ms  200.690 ms
19  * * *
20  * * *
21  * * *
22  * * *

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

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

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.

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

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

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

So it is better to choose the server which is close

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.

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

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 !