Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Pools
Re: [25+PH] Kano CKPool kano.is 0.9% PPLNS US,DE,SG,JP,NL,NYA
by
Make-A-Buck
on 01/02/2017, 09:29:40 UTC
Quote from: dance191 on February 01, 2017, 08:32:32 AM
Quote from: Make-A-Buck on February 01, 2017, 08:01:58 AM
Quote from: Make-A-Buck on February 01, 2017, 07:48:53 AM
Quote from: kano on February 01, 2017, 03:53:34 AM
Quote from: dance191 on February 01, 2017, 02:21:53 AM
Is anyone else now having problems with the API?  

curl -v https://kano.is/ now gives me this:
...
Check your DNS is pointing to the new web server.
If the DNS is wrong then you'd expect that error.

curl -v https://kano.is/ "works for me" Smiley

There was an SSL problem for a short while back when I moved the web server, but that was fixed back then also.
https://bitcointalk.org/index.php?topic=789369.msg17682243#msg17682243

Web is unrelated to the last back end server change, coz the web server was moved before that (see link above) - about 8.5 hours before the main server move.
The Android CKPool app just alerted me that my miner hash rate is 0 (Zero)
Logged onto kano.is and it also says 0.
Going to remote access my miner & see if it is running correctly at the colo.
OK... b4 I could even log in remotely, first kano.is says my hash rate is now returning to normal.
Currently 6.7 (My normal is about 8.1) then about 1-2min after that the Android app started to report my hash rate coming back up as well.
Anyone else have a 'bump' in the road for Feb 1st?

Everything has been smooth from what I'm looking at.  Mine checks every 60 seconds.  It will alert me if there is even a small drop in my hashrate and I didn't get any alerts (it is really sensitive).  Maybe a brief net/power outage at your colo?
That's the one thing that I can't rule out is a brief internet outage. However, the strange part is that I was able to remotely get to my miner, so either the outage was very brief, or something else went wrong for a min or two. My miner shows uptime of over 18 days, and it appears to have used BOTH fail-over mining pools configs... (usually the fail-overs never get used - there was a mining pool outage that was announced within the last day or so)

Pool             URL        User       Status Diff GetWorks Priority Accepted Diff1# DiffA# DiffR# DiffS# Rejected Discarded Stale LSDiff LSTime      
0 stratum+tcp://nya.kano.is:3333 wblaster.antMiner_R4_mab Alive 6K 56,735 0 501,783 0 3,010,686,156 10,826,988 0 1,817 866,461 282 6,000 0:00:00
1 stratum+tcp://stratum.kano.is:3333 wblaster.antMiner_R4_mab Alive 6K 1,668 1 236 0 1,262,028 279,072 0 136 457 79 6,000 1:20:38
2 stratum+tcp://stratum81.kano.is:81 wblaster.antMiner_R4_mab Alive 6K 27,080 2 217 0 1,124,340 98,496 0 48 373 263 6,000 14:18:49
total                                              85,483            502,236   0   3,013,072,524 11,204,556 0 2,001 867,291 624
HW     13663                                                                   0     0.0005%

Must have been a wrinkle for a min or two somewhere.