KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1258.

philipma1957

legendary

Activity: 4382

Merit: 9330

'The right to privacy matters'

Quote from: fusion0389 on August 30, 2016, 08:36:03 AM

Quote from: kano on August 30, 2016, 03:21:39 AM

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

CryptoBuddha

full member

Activity: 233

Merit: 100

reality is what you think it is

Quote from: fusion0389 on August 30, 2016, 08:36:03 AM

Quote from: kano on August 30, 2016, 03:21:39 AM

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.

fusion0389

sr. member

Activity: 324

Merit: 250

Quote from: kano on August 30, 2016, 03:21:39 AM

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.

thedreamer

legendary

Activity: 1694

Merit: 1002

Go Big or Go Home.....

Quote from: clgrissom3 on August 29, 2016, 06:32:55 PM

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). Cheesy

AriesIV10

legendary

Activity: 1260

Merit: 1006

Mine for a Bit

Block for TCSDR1

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

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.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

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

sorry2xs

legendary

Activity: 924

Merit: 1000

Dark Passenger Bitcoin miner 2013,Bitcoin node

Quote from: firetreeactual on August 29, 2016, 09:31:51 PM

Way to go, kid. Cool

Quote from: firetreeactual on August 29, 2016, 09:31:51 PM

Way to go, kid. Cool

just sent you a pm

Thisiserik

newbie

Activity: 22

Merit: 0

Quote from: kano on August 29, 2016, 09:24:21 PM

Quote from: kano on August 29, 2016, 09:07:56 PM

Quote from: kano on August 29, 2016, 07:45:14 PM

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.

firetreeactual

legendary

Activity: 952

Merit: 1003

Way to go, kid. Cool

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: kano on August 29, 2016, 09:07:56 PM

Quote from: kano on August 29, 2016, 07:45:14 PM

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.

Thisiserik

newbie

Activity: 22

Merit: 0

Quote from: firetreeactual on August 29, 2016, 09:15:11 PM

Quote from: fvineyard on August 29, 2016, 09:13:09 PM

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.

firetreeactual

legendary

Activity: 952

Merit: 1003

Quote from: fvineyard on August 29, 2016, 09:13:09 PM

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.

fvineyard

member

Activity: 136

Merit: 11

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

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

Thisiserik

newbie

Activity: 22

Merit: 0

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

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: kano on August 29, 2016, 07:45:14 PM

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 ...

firetreeactual

legendary

Activity: 952

Merit: 1003

Quote from: kano on August 29, 2016, 07:21:08 PM

Quote from: PPKi on August 29, 2016, 10:52:07 AM

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

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

Quote

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

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

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.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: PPKi on August 29, 2016, 10:52:07 AM

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

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

Quote

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

)

clgrissom3

legendary

Activity: 1736

Merit: 1032

Carl, aka Sonny :)

Quote from: sorry2xs on August 29, 2016, 03:42:18 PM

Quote from: bctmke on August 29, 2016, 10:52:35 AM

Quote from: citronick on August 29, 2016, 10:46:10 AM

Quote from: bctmke on August 29, 2016, 10:29:24 AM

Quote from: clgrissom3 on August 29, 2016, 08:52:23 AM

Two wake-up blocks this morning! Cheesy

Ugg, the Diff just changed to 221G... Sad

Edit: I was waiting until the R4 became available about 5 minutes ago...and holy crap! 8.6TH for $1395 USD! Angry

I'm putting my KeepKey back in the safe...

Yeah at that point you might as well add 200 bucks and get the 12TH + from the S9

At that price, R4 is just another expensive miner at 1.4k - the S9 12.93TH dropping to 1.6k is a "better bargain" - the miner is going to be at my ISP anyways and who cares about the noise.... but I want to wait for the A7 for bit more before pulling trigger for more S9s.

The A7 (or whatever they end up calling it) is more intriguing to me than anything BM puts out. So I'm still chugging away with just a few A6s.

R4 at this price point are going to selling as fast as rat poison at a rodent convention

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.

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