Author

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

newbie
Activity: 5
Merit: 0
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.
member
Activity: 61
Merit: 10
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 Huh?(
I am living in Ukraine)
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
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.

sr. member
Activity: 292
Merit: 250
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.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
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....

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
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
sr. member
Activity: 292
Merit: 250
@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.
newbie
Activity: 45
Merit: 0
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/
sr. member
Activity: 292
Merit: 250
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
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Getting lots of such frequent messages from cgminer while connected to SG node.

"Accepted untracked stratum share from pool 0"

"Lost x shares due to no stratum share response from pool 0"
Before the problems I mentioned or after?

https://bitcointalksearch.org/topic/m.13462455

I'm seeing these messages now (ongoing). Full of such messages.

Edit: Restarted my miner. Seeing SG node dead. Mining on main node.
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?
sr. member
Activity: 292
Merit: 250
Getting lots of such frequent messages from cgminer while connected to SG node.

"Accepted untracked stratum share from pool 0"

"Lost x shares due to no stratum share response from pool 0"
Before the problems I mentioned or after?

https://bitcointalksearch.org/topic/m.13462455

I'm seeing these messages now (ongoing). Full of such messages.

Edit: Restarted my miner. Seeing SG node dead. Mining on main node.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Getting lots of such frequent messages from cgminer while connected to SG node.

"Accepted untracked stratum share from pool 0"

"Lost x shares due to no stratum share response from pool 0"
Before the problems I mentioned or after?

https://bitcointalksearch.org/topic/m.13462455
sr. member
Activity: 292
Merit: 250
Getting lots of such frequent messages from cgminer while connected to SG node.

"Accepted untracked stratum share from pool 0"

"Lost x shares due to no stratum share response from pool 0"
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
SG had a dip, now seem to be up again.

have not set to main as failover, will do later, tied up atm. thx for looking into it. FIX FIX FIX.

btw where the block ? me hungry
Yeah any outage will be very short - less than a minute.

I just managed to have it happen on the DE node also, that one was 32 seconds.
It's memory related so takes quite a while before the problem can cause a failure so don't expect it happening often (or again even) until it's fixed.

--

Payout 391877 sent
58068c471f825ed7edfa03ecaa6e4f1eab8abb7b8728b5692b035630f9e4e2a0
and confirmed

--

Edit: SG and DE fix in place and all swapped over smoothly.
You should rarely see a failover on the SG or DE nodes when ckpool restarts cleanly.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
SG had a dip, now seem to be up again.

have not set to main as failover, will do later, tied up atm. thx for looking into it. FIX FIX FIX.

btw where the block ? me hungry
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
You have to also remember your hash rate is cyclic and is never a fixed rate.  It's pretty difficult to take a snapshot set of numbers and say it should be a certain way.  That's why the hash rate chart is always something like this...

https://i.imgur.com/UqluWlO.jpg

Excepting that the line shown as "average" is not the average of that cyclic rate, the average should be about through the middle of the cycles.  Or is that median value?  Mode, mean, median, average... statistics are not my strong suit.
Coz he didn't show the left of the graph that is below the line.

Here's the code Cheesy
https://bitbucket.org/ckolivas/ckpool/src/1c2376ce40661950b125dc031795b760945dfe16/pool/inc.php?at=master&fileviewer=file-view-default#inc.php-32
(you'll find that in the web page when you view the graph)
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Having instability on the SG node at the moment.
Hopefully everyone using it has their failover set to the main node.
-ck is looking into a fix for the problems.

We'll have the Tube proxies up and running on the DE and SG nodes once this is sorted out, also.
legendary
Activity: 1274
Merit: 1000
You have to also remember your hash rate is cyclic and is never a fixed rate.  It's pretty difficult to take a snapshot set of numbers and say it should be a certain way.  That's why the hash rate chart is always something like this...



Excepting that the line shown as "average" is not the average of that cyclic rate, the average should be about through the middle of the cycles.  Or is that median value?  Mode, mean, median, average... statistics are not my strong suit.
hero member
Activity: 575
Merit: 500
has this pool ever had back to back in its history  Smiley
That's the 4th time.

Code:
417 391920 25.22205742 2016-01-05 20:36:31+00 +36 Confirms 1,312,920,015 1.264% 0.013 1
416 391919 25.24137507 2016-01-05 20:26:11+00 +37 Confirms 46,387,923,153 44.655% 0.360 2

373 386503 25.06369915 2015-12-03 08:47:23+00 Matured 164,438,893 0.226% 0.002 45
372 386502 25.29834705 2015-12-03 08:45:32+00 Matured 55,359,736,580 76.124% 0.533 46

195 348800 25.06881192 2015-03-23 05:23:47+00 Matured 418,861,892 0.897% 0.009 223
194 348799 25.04422785 2015-03-23 05:11:45+00 Matured 102,227,698,277 218.821% 0.888 224

118 340929 25.22390379 2015-01-29 01:00:36+00 Matured 2,148,002,491 5.204% 0.051 300
117 340928 25.03951343 2015-01-29 00:24:46+00 Matured 97,668,003,042 236.640% 0.906 301

Still no '3' in a row Cheesy

I'm predicting that when we get to 15-20 TH, we will hit 3 in a row within 30 days.
sr. member
Activity: 294
Merit: 250
Aww Kano beat me to it!!
Jump to: