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

[DarkStar_]

Are there really about 40K in transactions unconfirmed in the mempool, or did I see that wrong?

It might be worth suspending the pool payouts for a short time just to pick up the extra transaction fees that are out there when we find our next couple blocks. I mean, in the long run, it would put extra coin in our pocket. Just a thought.

The last Kano payout has this [url-https://www.blocktrail.com/BTC/tx/0401d87e9741a02c2158f9b992e42239eb3aa9c660765be5e6ff4c0ed55baa8b]tx[/url], which has a size 25kb. Assuming 100 satoshis/byte paid in fees for each transaction, it would add only 0.025BTC extra payment, which becomes very small when split. I don't think it's really worth it to do that.

[firetreeactual]

...
... back to sorting out the web problem.

That didn't exist ...
Seems my underhanded techniques to get around DNS problems (if they ever occur) at home caused me grief and thus when I thought there where web problems, it's actually been OK.

Mine and web on

Yup...don'tcha just hate it when that happens? 

[PantminerS7]

ALERT!!!

The 5 minute mining outage is planned for 18:30 UTC - in 35 minutes.

snip

snip

Man that woke me up. Gotta stop sleeping in the middle of the day.

Sweet to see that green in the end of the tunnel at least!

Mine on!

[dance191]

Is anyone else now having problems with the API?  


curl -v https://kano.is/ now gives me this:
* SSLv3, TLS handshake, Client hello (1):
* error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
* Closing connection 0
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol


So, I give openssl a try, openssl s_client -debug -connect kano.is:443 now gives me this:
140249749202592:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:177:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 295 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE


Everything was working fine until the changes about 8 hours or so ago.

[VRobb]

The Android kano ckpool app is reporting back correctly, and that uses the API.  No difference seen here.

[clgrissom3]

So is the iPhone app which also uses the API.

[kano]

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"

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.

[dance191]

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"

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.

Thanks for the info guys.  I didn't realize the server IP address changed twice.  I updated it once, then didn't check that the IP address had changed again.  Kano, you were 100% correct as DNS was not pointing to what the current server is.  Thanks again!

[Make-A-Buck]

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"

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.

[Make-A-Buck]

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"

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?

[dance191]

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"

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?

[kano]

Block! by sapperlot with an S9v1

Edit2: first block found on the new server

Edit: well that shows January over and done with

Code:

2017 Jan  22.65 PHs  40  41.37  103.43%  105.58%  96.68%  101.16%

Although the luck was a little low, 96.68%, the Txn fees put the average reward over 100% PPS with 101.16%

[Make-A-Buck]

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"

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.

[IntroVert]

Kano, was payout for block 450816 ever sent out? Don't see it in my wallet and the blockchain. Might have matured while you were moving servers.

[kano]

Kano, was payout for block 450816 ever sent out? Don't see it in my wallet and the blockchain. Might have matured while you were moving servers.

Ah your right - oops - it was of course dropped out of the work since I changed bitcoinds from the old to the new server, while it was still waiting to be confirmed, and we are now mining to a new bitcoind (on the new server)

OK pushed it back into the work now - it will be confirmed with the next block.
I'll blame the fact I've been awake now for most of the last 40 hours

[IntroVert]

Thanks man, your hard work is really appreciated.

[bit2255]

Thanks man, your hard work is really appreciated.

ABSOLUTELY !!!

might not mean as much from a small home miner newbie, but again... THANKS !!!

[VRobb]

In the iPhone app, I input my username and api key; however, under the workers tab, it still says no workers?

Support thread here: https://bitcointalk.org/index.php?topic=1344360.0

[NomadGroup]

Kano, was payout for block 450816 ever sent out? Don't see it in my wallet and the blockchain. Might have matured while you were moving servers.

Ah your right - oops - it was of course dropped out of the work since I changed bitcoinds from the old to the new server, while it was still waiting to be confirmed, and we are now mining to a new bitcoind (on the new server)

OK pushed it back into the work now - it will be confirmed with the next block.
I'll blame the fact I've been awake now for most of the last 40 hours

Yeah thanks a lot Kano!!!!  And try to get some sleep!

[kano]

In the iPhone app, I input my username and api key; however, under the workers tab, it still says no workers?

Should be fixed now.