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

[MoparMiningLLC]

as I am typing this now, my miners are disconnecting/reconnecting. when they disconnect they roll over to slush after a few mins they come back to kano.

[1714046756]

1714046756

[1714046756]

1714046756

[kano]

as I am typing this now, my miners are disconnecting/reconnecting. when they disconnect they roll over to slush after a few mins they come back to kano.

I'm not referring to people disconnecting - I don't control your miners or your internet - I'm referring to the nodes disconnecting from the main pool server which causes a failover to everyone on the node.
The nodes have all been operating fine for the last 14 hours.

Read this:
https://bitcointalk.org/index.php?topic=789369.msg47878272#msg47878272

[MoparMiningLLC]

as I am typing this now, my miners are disconnecting/reconnecting. when they disconnect they roll over to slush after a few mins they come back to kano.

I'm not referring to people disconnecting - I don't control your miners or your internet - I'm referring to the nodes disconnecting from the main pool server which causes a failover to everyone on the node.
The nodes have all been operating fine for the last 14 hours.

Read this:
https://bitcointalk.org/index.php?topic=789369.msg47878272#msg47878272

i understand that and that is why i did not type my post as a reply or a quote to yours. i was just mentioning that they keep failing over. the miners themselves are not losing any hashing time, they just wont stay connected to kano. I prefer to keep them here though so I am trying to figure out why they keep switching off and then coming right back after a few minutes.

[MoparMiningLLC]

One thing you can try is using port 80 instead of port 3333 in your connection.
Most ISPs wont mess with port 80 since it's used for web browsing.
Also try port 443 since that's the SSL web browsing port that most all web sites use now
(most web browsers are starting to treat port 80 connections as inferior to 443 no matter what the web site is)
And of course you can try port 81 or port 8080 in your connection.

i can try changing the ports but the isp is not blocking mining as the miners just kick over to another pool - either slush or antpool. as a note, I also have sets of miners connected to both slush and ant, neither of those sets are disconnecting/reconnecting to pools. so far the issue holds only to the 5 I have here at kano. all the miners are variations of s9/s9i/s9j running the lpm firmware.

[kano]

One thing you can try is using port 80 instead of port 3333 in your connection.
Most ISPs wont mess with port 80 since it's used for web browsing.
Also try port 443 since that's the SSL web browsing port that most all web sites use now
(most web browsers are starting to treat port 80 connections as inferior to 443 no matter what the web site is)
And of course you can try port 81 or port 8080 in your connection.

i can try changing the ports but the isp is not blocking mining as the miners just kick over to another pool - either slush or antpool. as a note, I also have sets of miners connected to both slush and ant, neither of those sets are disconnecting/reconnecting to pools. so far the issue holds only to the 5 I have here at kano. all the miners are variations of s9/s9i/s9j running the lpm firmware.

Yes, but we also have 10's of thousands of miners working fine here
The point about trying the above options is to see if that resolves the network connection problem from you to the node.
Also, what exact pool node settings are you using
i.e. for the main node it's "stratum+tcp://stratum.kano.is:3333"

[MoparMiningLLC]

Yes, but we also have 10's of thousands of miners working fine here
The point about trying the above options is to see if that resolves the network connection problem from you to the node.
Also, what exact pool node settings are you using
i.e. for the main node it's "stratum+tcp://stratum.kano.is:3333"

understood - trust me, I am not complaining,  just trying to figure it out too. I switched to port 80 on all 5 kano miners.

i was using stratum+tcp://nya.kano.is:3333 and now using stratum+tcp://nya.kano.is:80

do you recommend that i go to the main node?

[kano]

Yes, but we also have 10's of thousands of miners working fine here
The point about trying the above options is to see if that resolves the network connection problem from you to the node.
Also, what exact pool node settings are you using
i.e. for the main node it's "stratum+tcp://stratum.kano.is:3333"

understood - trust me, I am not complaining,  just trying to figure it out too. I switched to port 80 on all 5 kano miners.

i was using stratum+tcp://nya.kano.is:3333 and now using stratum+tcp://nya.kano.is:80

do you recommend that i go to the main node?

Well you can ping them both directly to see which is closest - if they're similar then the main node will be a shorter path for work updates from the pool since it's closer to the work source.

Otherwise use the one with the lowest ping.
Nya also has a lower work load, even though they're the same power nodes, so if Nya is closer, it's better to use.

[MoparMiningLLC]

I have switched the port to 80 and will continue to watch them. as a note it is in awesome miner that I am seeing the disconnections/re-connections

in the miners web interface i see only that the shares increase on either secondary or third pool that I have set up - it sometimes skips the second and goes to the third.

then a few mins later awesome miner shows them back on kano pool

[MoparMiningLLC]

Well you can ping them both directly to see which is closest - if they're similar then the main node will be a shorter path for work updates from the pool since it's closer to the work source.

Otherwise use the one with the lowest ping.
Nya also has a lower work load, even though they're the same power nodes, so if Nya is closer, it's better to use.

how do I ping the nodes? that is one thing I have never bothered to try so I am ignorant on how it is done.

edit - nvm I read the first page again, and it explains it.

[kano]

Well you can ping them both directly to see which is closest - if they're similar then the main node will be a shorter path for work updates from the pool since it's closer to the work source.

Otherwise use the one with the lowest ping.
Nya also has a lower work load, even though they're the same power nodes, so if Nya is closer, it's better to use.

how do I ping the nodes? that is one thing I have never bothered to try so I am ignorant on how it is done.

Well you can actually ping them from in the S9 web interface - but I'm not sure which tab it is.

As for from a windows PC, in the search bottom left, search for cmd and it will find 'command prompt' which you can use to start one where you can type commands.
In there type 'ping nya.kano.is' or 'ping stratum.kano.is'
then it reports some stats at the bottom after pinging 4 times (by default)

[MoparMiningLLC]

Well you can actually ping them from in the S9 web interface - but I'm not sure which tab it is.

As for from a windows PC, in the search bottom left, search for cmd and it will find 'command prompt' which you can use to start one where you can type commands.
In there type 'ping nya.kano.is' or 'ping stratum.kano.is'
then it reports some stats at the bottom after pinging 4 times (by default)

yea - after I posted it, I was like hmmm kano probably explains this at the start, I went to page one and there it was

so my results are:

Code:

C:\Users\ADMIN>ping stratum.kano.is

Pinging stratum.kano.is [168.235.105.129] with 32 bytes of data:
Reply from 168.235.105.129: bytes=32 time=78ms TTL=54
Reply from 168.235.105.129: bytes=32 time=81ms TTL=54
Reply from 168.235.105.129: bytes=32 time=79ms TTL=54
Reply from 168.235.105.129: bytes=32 time=78ms TTL=54

Ping statistics for 168.235.105.129:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 81ms, Average = 79ms

C:\Users\ADMIN>ping nya.kano.is

Pinging ny1.kano.is [168.235.90.188] with 32 bytes of data:
Reply from 168.235.90.188: bytes=32 time=40ms TTL=54
Reply from 168.235.90.188: bytes=32 time=39ms TTL=54
Reply from 168.235.90.188: bytes=32 time=39ms TTL=54
Reply from 168.235.90.188: bytes=32 time=41ms TTL=54

Ping statistics for 168.235.90.188:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 41ms, Average = 39ms

looks like nya.kano.is is the best for me based on the ping - now my question is this, is this a good ping as it relates to mining?

[kano]

Well a ping under 100ms is fine.
Over 200ms is getting in the too far away arena.
Over 300ms is a problem.

[MoparMiningLLC]

Well a ping under 100ms is fine.
Over 200ms is getting in the too far away arena.
Over 300ms is a problem.

well ping is not the issue. My overall internet should not be an issue either - speedtest.net:

 PING ms
17
 DOWNLOAD Mbps
122.78
 UPLOAD Mbps
159.13

really hope its not a hardware issue, this only started today so hopefully it will end and will be a non-issue soon.

[kano]

Block! by heatguy
Welcom to the Acclaim board!

[MoparMiningLLC]

woohoo! another block for November!

[clgrissom3]

Block! by heatguy
Welcom to the Acclaim board!

Yay Block!  This is our 1st of BLOCK WEDNESDAY!

[kano]

Anyone wondering, we just had an outage on stratum.kano.is for half an hour from 04:24:27 UTC
All OK again now finally.

The cause was apparently a DDoS attack so it was null routed 3 times, for a total of half an hour.
I'm following up to verify if their DDoS rules are too strict for a node or if it really was a DDoS attack.

[MoparMiningLLC]

curious - could these type of attacks cause the issue I was having?

[kano]

curious - could these type of attacks cause the issue I was having?

No - the node went down - that's why the pool hash rate dropped 60PHs for almost 30 minutes.

[MoparMiningLLC]

curious - could these type of attacks cause the issue I was having?

No

darn, I want to find the cause lol sigh miner #5 just disconnected/reconnected while i was typing this. It only lasted a few seconds though so it didnt even trigger the disconnection notice from awesome miner. I will try another port tomorrow. until then I hope we find another block!