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

[kano]

Why Kano pool stop working with NiceHash?  https://www.nicehash.com/

5 days ago everything were ok, but now NH pool verificator saying:

Pool host: stratum.kano.is
Pool port: 3333
Pool user: worker.NH01
Pool pass: 123
Algorithm: SHA256

Resolving pool host stratum.kano.is... OK
Establishing connection with proxy... OK
Establishing connection with pool 104.194.28.194:3333... Error: Read timed out

They must be using the IP address that has very bad luck.

I treat miners and rental sites differently.
A miner is effectively responsible for all their hardware.
So luck statistics have to show clearly that they are doing something wrong before I'll put a hold on their payouts.

A rental site doesn't really give a damn since they get paid no matter what is supplied by the source.
In fact *Hash has recently pointed out they make even more from withholders since they keep any BTC the withholder has in balance and the pool/target they were mining to will never find out from *Hash and of course never be refunded anything.
Since *Hash has a larger hash rate, withholders are able to easily hide their withholding within that larger hash rate.
Thus I'm more than willing to block an IP address that shows the early stages of bad luck - especially since no one (but me) actually loses out from me blocking an IP address, it just means an increase in variance (and less fees for me )

[kano]

I'll be doing a CKDB restart in 2 shifts from now.
That will roughly be at 01:45 UTC (about an hour from now)
No miners will be affected.

I'm adding changes to reduce the amount of RAM required during a CKDB restart so I can do the luck report change I mentioned before.
It would effectively mean running CKDB twice on the server, once as normal and a second time for the duration of generating the luck report, so I need to get the memory footprint on the main CKDB down more, to be able to do that, with recent changes.

[firetreeactual]

Why Kano pool stop working with NiceHash?  https://www.nicehash.com/

5 days ago everything were ok, but now NH pool verificator saying:

Pool host: stratum.kano.is
Pool port: 3333
Pool user: worker.NH01
Pool pass: 123
Algorithm: SHA256

Resolving pool host stratum.kano.is... OK
Establishing connection with proxy... OK
Establishing connection with pool 104.194.28.194:3333... Error: Read timed out

They must be using the IP address that has very bad luck.

I treat miners and rental sites differently.
A miner is effectively responsible for all their hardware.
So luck statistics have to show clearly that they are doing something wrong before I'll put a hold on their payouts.

A rental site doesn't really give a damn since they get paid no matter what is supplied by the source.
In fact *Hash has recently pointed out they make even more from withholders since they keep any BTC the withholder has in balance and the pool/target they were mining to will never find out from *Hash and of course never be refunded anything.
Since *Hash has a larger hash rate, withholders are able to easily hide their withholding within that larger hash rate.
Thus I'm more than willing to block an IP address that shows the early stages of bad luck - especially since no one (but me) actually loses out from me blocking an IP address, it just means an increase in variance (and less fees for me )

Seriously...nice work.

[kano]

I'll be doing a CKDB restart in 2 shifts from now.
That will roughly be at 01:45 UTC (about an hour from now)
No miners will be affected.

I'm adding changes to reduce the amount of RAM required during a CKDB restart so I can do the luck report change I mentioned before.
It would effectively mean running CKDB twice on the server, once as normal and a second time for the duration of generating the luck report, so I need to get the memory footprint on the main CKDB down more, to be able to do that, with recent changes.

Restart completed.
Mining is unaffected, API access is OK, but web logins are currently not working.
I'm working on sorting out the web login problem ...

[Thisiserik]

@Kano, I can't sign in to the main sight.

[fvineyard]

Same for me. Cannot login. Must not be fully back up yet.

Edit: Of course I guess I could have read Kano's posting

[firetreeactual]

Same for me. Cannot login. Must not be fully back up yet.

Edit: Of course I guess I could have read Kano's posting

Well...me, too...but I can't login either. Just added an A6 and can't find out if it's connecting. It'll be OK.

[Thisiserik]

Same for me. Cannot login. Must not be fully back up yet.

Edit: Of course I guess I could have read Kano's posting

Well...me, too...but I can't login either. Just added an A6 and can't find out if it's connecting. It'll be OK.

What post, please? School started this week and I have been off the boards.

[kano]

I'll be doing a CKDB restart in 2 shifts from now.
That will roughly be at 01:45 UTC (about an hour from now)
No miners will be affected.

I'm adding changes to reduce the amount of RAM required during a CKDB restart so I can do the luck report change I mentioned before.
It would effectively mean running CKDB twice on the server, once as normal and a second time for the duration of generating the luck report, so I need to get the memory footprint on the main CKDB down more, to be able to do that, with recent changes.

Restart completed.
Mining is unaffected, API access is OK, but web logins are currently not working.
I'm working on sorting out the web login problem ...

Will require another CKBD restart.
Nothing major, but the web password hash (only) that is being passed to CKDB is being truncated due to the last change.
I've patched CKDB on the server to fix it and will restart CKDB (in about 1 minute ...)
I'll code a better fix for it later, but this one is OK and gets logins working again.

The previous restart drastically reduced restart memory usage, so that was good at least

CKDB restart in 1 minute.

[firetreeactual]

Way to go, kid. 

[Thisiserik]

I'll be doing a CKDB restart in 2 shifts from now.
That will roughly be at 01:45 UTC (about an hour from now)
No miners will be affected.

I'm adding changes to reduce the amount of RAM required during a CKDB restart so I can do the luck report change I mentioned before.
It would effectively mean running CKDB twice on the server, once as normal and a second time for the duration of generating the luck report, so I need to get the memory footprint on the main CKDB down more, to be able to do that, with recent changes.

Restart completed.
Mining is unaffected, API access is OK, but web logins are currently not working.
I'm working on sorting out the web login problem ...

Will require another CKBD restart.
Nothing major, but the web password hash (only) that is being passed to CKDB is being truncated due to the last change.
I've patched CKDB on the server to fix it and will restart CKDB (in about 1 minute ...)
I'll code a better fix for it later, but this one is OK and gets logins working again.

The previous restart drastically reduced restart memory usage, so that was good at least

CKDB restart in 1 minute.

Cool , thank you for all you do @Kano.

[sorry2xs]

Way to go, kid. 

Way to go, kid. 

just sent you a pm

[kano]

2nd restart completed ok now also, and web logins working (as anyone trying will have found out now)

The main point of the change was a memory reduction during the CKDB restart and that was a major success coz it used about 14GB less ram the first time, and about 13GB less the 2nd time (due to having to slightly increase the number that caused both the drop in ram and the password problem)

First restart was: 2016-08-30 01:51:04 to 02:01:18 (UTC)
Second restart was 2016-08-30 02:25:48 to 2016-08-30 12:39:27 (UTC)
Both restarts had to reload from the same point back in time, so the 2nd one was longer processing an extra ~38minutes of data.

No miners were affected

[kano]

If anyone has noticed any disconnects over the last hour or so, it seems there's some mineor internet problems around the pacific.
I've not noticed the pool hash rate change any more than usual, but a linode monitoring node keeps complaining about node and pool connections.
Very few miners should be affected, however, and they should just be reconnecting pretty much as soon as it happens.

[AriesIV10]

Block for TCSDR1

[thedreamer]

I love what you said but they are selling...apparently a lot of rats can't tell rat poison from month-old cheese!  For once I would love to see all miners band together and show biteme who really has control...it's the person who holds the money!  I think we tend to forget that little tidbit.

Unfortunately most people have no scruples and brownnose the company that they THINK will make money for them, even though that company has already calculated that they will more than likely never Profit, if ever ROI. Also said company doesn't give a sht about running a good business with business ethics, which is pretty much how most CHinese co's are run (speaking from experience, so don't hate). 

[fusion0389]

If anyone has noticed any disconnects over the last hour or so, it seems there's some mineor internet problems around the pacific.
I've not noticed the pool hash rate change any more than usual, but a linode monitoring node keeps complaining about node and pool connections.
Very few miners should be affected, however, and they should just be reconnecting pretty much as soon as it happens.

Would this have anything to do with all my S9's going offline? I got out of bed an hour ago and noticed that all my S9's had little xxxxxxx all the way across on all hash boards. I rebooted them all and they're back up, could it be pool connection related somehow? None of my S7-LN were affected.

[CryptoBuddha]

If anyone has noticed any disconnects over the last hour or so, it seems there's some mineor internet problems around the pacific.
I've not noticed the pool hash rate change any more than usual, but a linode monitoring node keeps complaining about node and pool connections.
Very few miners should be affected, however, and they should just be reconnecting pretty much as soon as it happens.

Would this have anything to do with all my S9's going offline? I got out of bed an hour ago and noticed that all my S9's had little xxxxxxx all the way across on all hash boards. I rebooted them all and they're back up, could it be pool connection related somehow? None of my S7-LN were affected.

I don't think xxxxx boards have anything to do with the pool. If there was a major disconnect to the pool, then ALL of your miners would be affected, not only s9's. Besides, your s9's would be mining at your backup pool. But I've read here and in some other threads that s9's do have some internal issues. I have only s7's so can't really say what could be the cause in your case.

[philipma1957]

If anyone has noticed any disconnects over the last hour or so, it seems there's some mineor internet problems around the pacific.
I've not noticed the pool hash rate change any more than usual, but a linode monitoring node keeps complaining about node and pool connections.
Very few miners should be affected, however, and they should just be reconnecting pretty much as soon as it happens.

Would this have anything to do with all my S9's going offline? I got out of bed an hour ago and noticed that all my S9's had little xxxxxxx all the way across on all hash boards. I rebooted them all and they're back up, could it be pool connection related somehow? None of my S7-LN were affected.

yeah  that more then likely means you are overheating or short power psu wise.

So what freq are you rated?  550 575 600?

What freq are you running? 525 550 575?

What are your temps?  60-90 / 65-95 / 70-100 / 75-105

try to lower the freq by 25  and get temps to 60-90 or 65-95

what psu's do you use?  the bitmaintech psu suffers a big drop off when it gets warm:

 50c it can give 133 amps  = 1596 watts   this is good for the s-9 at   freq   550
 55c it can give 117 amps  = 1404 watts   this is okay for the s-9 at   freq   550
 60c it can give 107 amps  = 1284 watts   this is short for the  s-9 at freq   550

So  maybe a clock to 506- 525  vs a clock to 550 would fix you issues


APW3-12-1600-B2

[VivaLaGuN]

where can i see my actual balance?