Author

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

newbie
Activity: 65
Merit: 0
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://bitcointalksearch.org/topic/m.17682243

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.
sr. member
Activity: 261
Merit: 250
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://bitcointalksearch.org/topic/m.17682243

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! Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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://bitcointalksearch.org/topic/m.17682243

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.
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
So is the iPhone app which also uses the API.
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
The Android kano ckpool app is reporting back correctly, and that uses the API.  No difference seen here.
sr. member
Activity: 261
Merit: 250
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.
full member
Activity: 165
Merit: 100
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!
legendary
Activity: 952
Merit: 1003
...
... 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 Smiley
Yup...don'tcha just hate it when that happens?  Kiss
legendary
Activity: 2772
Merit: 3284
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.
sr. member
Activity: 277
Merit: 250
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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
... 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 Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
ALERT!!!

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

For mining and the web access, nothing will change.
That's already been moved to 2 new servers that currently point at the old server.

However, the back end server will move to a new one and during that move, no mining will be available.
Again, it should take about 5 minutes, though possibly more if unexpected problems occur.
I'm already running the new pool server, but I'll of course need to update it to match the current pool data, and that's where the 5 minutes comes in.

I'll post again after it's done.
A quick note, web still isn't working, I'm working on fixing that.

Mining is 100% ok.

Pool outage ended up being 22 minutes, not 5 minutes Sad
I've rolled back ckpool to the August version I was running on the old server.

I ran the current git with a small hash rate for an hour on the new server and all was OK.
As soon as I enabled everyone's access it crashed and burned, so I went back a couple of versions twice, then gave up and went back to the old August version.
Everything was happy with that Smiley

... back to sorting out the web problem.
full member
Activity: 201
Merit: 100
full member
Activity: 201
Merit: 100
And slush hash rate went up 16ph. I got so much beeping going on I thought my server battery backups were offline. Guess I should setup some backup pools for my other gear
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Awe, KWorkers and KShift Graph is not showing up now when I log in.  I was going to check the hashrate of the new A741  Grin
Added to the bottom of my server move todo list ... minor change to add it back to the new web server Smiley
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Awe, KWorkers and KShift Graph is not showing up now when I log in.  I was going to check the hashrate of the new A741  Grin
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
ALERT!!!

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

For mining and the web access, nothing will change.
That's already been moved to 2 new servers that currently point at the old server.

However, the back end server will move to a new one and during that move, no mining will be available.
Again, it should take about 5 minutes, though possibly more if unexpected problems occur.
I'm already running the new pool server, but I'll of course need to update it to match the current pool data, and that's where the 5 minutes comes in.

I'll post again after it's done.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hi!

I'm giving this pool a try, seems pretty transparent and nice so far.

One quick question, using the same address as anoymous (user name) and as registered user (payment) could generate problems?

Cheers!!
Both payments will of course go to the same address, and be joined into one payment, but the user will only be able to see the user mining on the web site, since they are, in all respects, two separate accounts.
newbie
Activity: 11
Merit: 0
Hi!

I'm giving this pool a try, seems pretty transparent and nice so far.

One quick question, using the same address as anoymous (user name) and as registered user (payment) could generate problems?

Cheers!!
full member
Activity: 211
Merit: 100
Jump to: