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

[kano]

...
Just look at the Workers->Workers page when you first start mining.
It updates immediately whenever you send a share.
You can see the share count going up, ignore the hash rate on the right when you first start until you've mined for at least 10 minutes, but look at the "Share Rate" to see if those shares are counting.

Thanks! I’ll switch over. Can you tell me what a normal share rate range is for a single S9?

Well it doesn't matter when you first connect.

It takes a few hours for a miner to show a close approximation of their hash rate in the "Hash Rate" field.

The point of the "Share Rate" field is to get immediate feedback that the miner is working ok and submitting shares, and to show what that is when converted to a "Share Rate", but it also fluctuates a lot.

You really have to just let it go for a few hours and see what the "Hash Rate" settles down to.

[Vertflyer]

...
Just look at the Workers->Workers page when you first start mining.
It updates immediately whenever you send a share.
You can see the share count going up, ignore the hash rate on the right when you first start until you've mined for at least 10 minutes, but look at the "Share Rate" to see if those shares are counting.

Thanks! I’ll switch over. Can you tell me what a normal share rate range is for a single S9?

Well it doesn't matter when you first connect.

It takes a few hours for a miner to show a close approximation of their hash rate in the "Hash Rate" field.

The point of the "Share Rate" field is to get immediate feedback that the miner is working ok and submitting shares, and to show what that is when converted to a "Share Rate", but it also fluctuates a lot.

You really have to just let it go for a few hours and see what the "Hash Rate" settles down to.

Sounds good. I’m back in.

[kano]

There will be a DB restart in about 30 minutes, around 12:30 UTC
It will actually be when the zekken shift completes and is processed - which will be about then.

No mining will be affected at all.

The web site and API will reply with lotsa zeros and '?' marks during a DB restart, for about 10 minutes.

This is a minor update to try and deal with the timeouts that occur every once in a while - and I'll now mention the actual cause since I've implemented a way to deal with them
The rewards and payouts pages go back to when the pool started for some miners.
The data back then gets swapped out of ram and sometimes when a long term miner checks their rewards and payouts, it takes too long to swap back into ram and times out on the web page.
I think the actual cause is if two different people do it at the same time - which would also explain why it's not very common.
This change helps stop that data from ever swapping out, since the DB now runs with a RES footprint smaller than bitcoin and a VIRT size smaller than ckpool, it's OK to stop that data from being swapped out.

I'll post again once the DB restart has completed.

KanoDB restart complete.
Was from 12:31 to 12:37 UTC
Mine on

[kano]

Been having more network problems on and off with the Silicon Valley half of stratum.kano.is
As long as your 2nd pool listed on your miner is some other node (e.g. nya.kano.is) your mining should be unaffected.
The network issues are very random so you may not be affected by them, but if you do failover, that's why.

Finally got a response about this - it would seem there was a low level DDoS going on that was causing intermittent problems but not on going problems.
It's supposedly been resolved now, and I've had no alerts for over an hour now also.

[-EOS-]

This is why I mine here...  Kano is always keeping us notified and informed!!!

Thanks for all of your work Kano

[Waztim]

...
Just look at the Workers->Workers page when you first start mining.
It updates immediately whenever you send a share.
You can see the share count going up, ignore the hash rate on the right when you first start until you've mined for at least 10 minutes, but look at the "Share Rate" to see if those shares are counting.

Thanks! I’ll switch over. Can you tell me what a normal share rate range is for a single S9?

Well it doesn't matter when you first connect.

It takes a few hours for a miner to show a close approximation of their hash rate in the "Hash Rate" field.

The point of the "Share Rate" field is to get immediate feedback that the miner is working ok and submitting shares, and to show what that is when converted to a "Share Rate", but it also fluctuates a lot.

You really have to just let it go for a few hours and see what the "Hash Rate" settles down to.

Sounds good. I’m back in.

Welcome to the best little pool mining Bitcoin. Your hash rate is appreciated here.

[jjaskolski]

I read somewhere in a forum that, if my Miner is offline when a block is found (or, is it when the reward is distributed?), I will not share in the block reward. 

Is that correct?

I understand that when a block is found, the block reward is shared among the last N shares that miners sent to the pool, up to when the block was found.


But what if, during the shift in which the block was found, I was absent from the pool? (however, I was present for all previous shifts back out over 5Nd).


Put another way: Is it OK for me to take my miner offline for an hour?  Or, could doing so cost me if a block is found during that hour?

[nazzer]

I read somewhere in a forum that, if my Miner is offline when a block is found (or, is it when the reward is distributed?), I will not share in the block reward. 

Is that correct?

I understand that when a block is found, the block reward is shared among the last N shares that miners sent to the pool, up to when the block was found.


But what if, during the shift in which the block was found, I was absent from the pool? (however, I was present for all previous shifts back out over 5Nd).


Put another way: Is it OK for me to take my miner offline for an hour?  Or, could doing so cost me if a block is found during that hour?

You get rewarded for all shares in the last 5Nd that you submitted, even if you were offline when block is found (see workers shift graph to see)

[2tights]

I read somewhere in a forum that, if my Miner is offline when a block is found (or, is it when the reward is distributed?), I will not share in the block reward. 

Is that correct?

I understand that when a block is found, the block reward is shared among the last N shares that miners sent to the pool, up to when the block was found.


But what if, during the shift in which the block was found, I was absent from the pool? (however, I was present for all previous shifts back out over 5Nd).


Put another way: Is it OK for me to take my miner offline for an hour?  Or, could doing so cost me if a block is found during that hour?

You get rewarded for all shares in the last 5Nd that you submitted, even if you were offline when block is found (see workers shift graph to see)

+1

[Waztim]

Here Kitty, Kitty, Kitty.... Here Kitty, Kitty Kitty..... bring that block on over here. Mine On!!

[Minty_Andy]

Yeeeah, soo, im gonna have to have you guys go ahead and find some blocks. Mmkay?

Oh, and yea... going to have to have you come in on Sunday and find some more blocks. Mmkay?

That would be great.

[2tights]

Yeeeah, soo, im gonna have to have you guys go ahead and find some blocks. Mmkay?

Oh, and yea... going to have to have you come in on Sunday and find some more blocks. Mmkay?

That would be great.

I'm in my alchemy lab trying to perfect my luck potions. Will update on results.

[brad2388]

Looks like another attack on the site again.

[rifleman74]

Looks like another attack on the site again.

Attack on the site, but miners are running on a different server. 

[brad2388]

Looks like another attack on the site again.

Attack on the site, but miners are running on a different server. 

Good!

[brad2388]

Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?

[Make-A-Buck]

There will be a DB restart in about 30 minutes, around 12:30 UTC
It will actually be when the zekken shift completes and is processed - which will be about then.

No mining will be affected at all.

The web site and API will reply with lotsa zeros and '?' marks during a DB restart, for about 10 minutes.

This is a minor update to try and deal with the timeouts that occur every once in a while - and I'll now mention the actual cause since I've implemented a way to deal with them
The rewards and payouts pages go back to when the pool started for some miners.
The data back then gets swapped out of ram and sometimes when a long term miner checks their rewards and payouts, it takes too long to swap back into ram and times out on the web page.
I think the actual cause is if two different people do it at the same time - which would also explain why it's not very common.
This change helps stop that data from ever swapping out, since the DB now runs with a RES footprint smaller than bitcoin and a VIRT size smaller than ckpool, it's OK to stop that data from being swapped out.

I'll post again once the DB restart has completed.

KanoDB restart complete.
Was from 12:31 to 12:37 UTC
Mine on

Yep, saw that 30 min ago... came here to see what was going on. Thanks for explaining!

www2.netdoor.com/~wblaster/CKPool_WebUI-Down_Dec15-2017.jpg
www2.netdoor.com/~wblaster/CKPool_WebUI-Down_Dec15-2017b.jpg

[rifleman74]

Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?

Just one s9?  Yeah you're over 1/2 way there.  The red graph gets confusing with a smaller  pool, it was much easier for a rookie to understand when this pool was hitting 5 blocks in 5 days.   When the next block hits, the stuff to the right of the red area will be in red, and the left side of the current red area will be white (and out of the 5nd).   How much is not in the red will be determined when we find that next block.


MINE ON

[Dr0n3]

This is voodoo - had a couple S9's with same problem. One board (always chain 6) either dead or missing chips on reboot.


This works for me - not sure why?


Turn off all power for a few mins

Reboot with no internet connection

Let it cycle for about 30 mins - it will start up and shut down repeatedly.

Connect internet.

Magic - it runs for about 2 weeks above 13.5TH/s.  

Sometimes repeat a couple of times till you get the correct performance - be patient - wait at least 24 hrs till you decide.  
If GH/S(ideal) for chain 6 (or any chain) is in the 2k range - repeat immediately.  All 3 chains should be above 4k.

Then eventually (after about 2 weeks with 100 x HW errors of the other 2 chains) chain 6 board goes down over a couple of hours in GH/S(ideal) to the 2k region.

Just repeat and it recovers - all good for another couple of weeks.

I'd be very interested to know if it works for you - and if anyone might have an idea why?


NEVER return your miner to Bitmain China (via Hong Kong) on warranty - they take over a month and send somebody else faulty shit miner back - dirty full of mosquitos from Taiwan, not fixed and with same chain 6 problem.  Its just a Swaparoo (an Aussie term that CAN mean just keep moving things around, look busy and trying to help - but don't do anything useful).  Support goes DEAD eventually if you keep complaining that your WARRANTY replacement has the same problem you started with.

Cheers - usukan

Giving this a shot now on my 14TH/s version. It's had 1 board (chain 6) acting up over the past few days....sometimes it comes online and only detects 12 asic chips and reads a temperature of 15*, sometimes it detects all the asics but outputs 0 hashing power, then sometimes the hashing power output for the whole device shows 0 when in reality it's cranking out the normal amount.

When it does work it seems to only work for a day or two until some of the hashing power starts dropping off, yet the miner status page shows it as hashing at full speed. Usually a reboot or a shutdown temporarily fixes the issue, but this last time it was giving me issues several reboots didn't remedy the problem...the board would come online with all 63 asics detected, but no hash power.

So I'm attempting your fix right now. Shut the unit down through command line then killed the breaker to it, let it sit momentarily while disconnecting the network cable, flipped the breaker back on and am letting it try to connect/reboot itself with no connection. Will be plugging in the network cable shortly and hoping for the best! Will update with my outcome!

[brad2388]

Under my shift worker tab. The 5nd is in the red but im past that on the bar graph.
Over on the right i have a number of 6.97 i believe. Is that my current hash rate? So that means im half way to the 5nd?

Just one s9?  Yeah you're over 1/2 way there.  The red graph gets confusing with a smaller  pool, it was much easier for a rookie to understand when this pool was hitting 5 blocks in 5 days.   When the next block hits, the stuff to the right of the red area will be in red, and the left side of the current red area will be white (and out of the 5nd).   How much is not in the red will be determined when we find that next block.


MINE ON

Yes just one s9.

Thanks for the help on it!

Its slowly coming up