Pages:
Author

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

legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490

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.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
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
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Yes, but we also have 10's of thousands of miners working fine here Smiley
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.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
Yes, but we also have 10's of thousands of miners working fine here Smiley
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?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4

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 Smiley
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"
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490

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.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
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://bitcointalksearch.org/topic/m.47878272

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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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://bitcointalksearch.org/topic/m.47878272
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.
The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.

since reconnecting today, they have disconnected from the pool twice - for about 8-9 mins and then reconnected.
There have been no disconnects on the nodes since the datacentre power problem was fixed about 14 hours ago.

The problem will probably be at your end - you'll have to check what's up with your internet connection or ISP.

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.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.
The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.

since reconnecting today, they have disconnected from the pool twice - for about 8-9 mins and then reconnected.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.
The failover in the early cgminer code never worked properly coz it was never tested properly (or at all?) by the coder.
They can switch to pool3 and never switch back under various circumstances.

Most of the bmminer code is of course early cgminer code.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
I have been able to set up 5 of my miners back to Kano - will be watching to see if they stay pointed here or redirect again.
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
I saw mine had failed over to a solo pool for a while and then came back. All while I was sleeping!
Mine ON!
legendary
Activity: 1568
Merit: 2037
That was the first time I was home and looking at my miners during network issues.

Panicked like a rookie because I just moved my 741's inside, and have been testing their stability while heating the basement. I assumed I had some random temperature spike, but after 10 minutes of staring after the reboot I checked the support channels. Good old facepalm.

I did catch it and reset before I wound up going solo.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.
There were problems on and off from 04:15:42 UTC until 08:48 UTC
All OK since then.

I have Kano set up as primary pool but it is reading dead so all my kano miners are switching over to slush - I will try a hard reset on them when I get back to the house.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.
There were problems on and off from 04:15:42 UTC until 08:48 UTC
All OK since then.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
I have not been able to connect for a while - I have kano pools set up as primary but they attempt to connect and then disconnect and go to secondary pools.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Well it's back up yet again since 08:48:31 UTC ... but still no notification from the provider stating they've completed working on the power problem.
... and now stated that it's resolved.
OK time to send them some abuse Sad
member
Activity: 118
Merit: 14
Up and working again in Central Ohio.
Pages:
Jump to: