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

[kano]

For those of you with various stats apps and web sites ...

I'm gonna do a ckdb restart in about 40 minutes - after the next shift gets summarised.

No miners will be afffected as usual.

Web page stats will be unavailable for as long as it takes to restart (10-20min)

Seems like I'll have to spend some time searching for more memory leaks again, ckdb is still building up too much ram, but now it's obviously a lot smaller - it's taken 5 days to get near problematic and that's also been mostly the top of the great growth we've been having.

If you have an app or a web site, this will be a good time to test see how you handle the restart.

I'll pm zach and vh also.

[wikkidtt]

What mod did you do?  That's some very nice coins for S3+.  All mine are S3+ plus I'm seeing them selling on Ebay for $120 shipped now.

Wifi antenna. Thermal paste mod and some coding mods so they all ran at or above 500gh at stock 250mhz. At 300mhz was getting 580gh

Regular s3+ sell on Amazon for $160 plus $10.99 shipping. Friend has sold 6 of his so far. after there fee's you get $169.14

On modded I was making $196.74 ea after fee's

[ZACHM]

I'll pm zach and vh also.

Thanks!

http://ckpoolmonitor.zachmonroe.com should not have any problems with a restart. I believe the reason the android app has a problem is that it does not keep the old information in memory so when the pool info comes back live again it thinks there is a new block. Since I am storing the info into my own database my site compares the newest block to the previous to determine if it really is a new block or just the same one again. So noone should see a incorrect "Block Found" notification. 

[nhando]

What mod did you do?  That's some very nice coins for S3+.  All mine are S3+ plus I'm seeing them selling on Ebay for $120 shipped now.

Wifi antenna. Thermal paste mod and some coding mods so they all ran at or above 500gh at stock 250mhz. At 300mhz was getting 580gh

Regular s3+ sell on Amazon for $160 plus $10.99 shipping. Friend has sold 6 of his so far. after there fee's you get $169.14

On modded I was making $196.74 ea after fee's

Those are some nice numbers!  I'm barely getting 450GH on 225MHZ....  300MHZ?  What firmware you on?  Mine are all max at 250MHZ

[-ck]

SG and DE node users.

I've tracked down the bug in the node code that caused people to hash into thin air without failing over and have implemented a workaround for it to prevent the cause from happening. In addition I've implemented a change to make it more robust in ckpool itself at disconnecting clients connected to the node but that would warrant a ckpool restart at the main pool which isn't justified at this stage.

Apologies for the lost time when hashing on the SG node. Please give it another go and watch carefully for any issues. Thanks for your patience!

[wikkidtt]

What mod did you do?  That's some very nice coins for S3+.  All mine are S3+ plus I'm seeing them selling on Ebay for $120 shipped now.

Wifi antenna. Thermal paste mod and some coding mods so they all ran at or above 500gh at stock 250mhz. At 300mhz was getting 580gh

Regular s3+ sell on Amazon for $160 plus $10.99 shipping. Friend has sold 6 of his so far. after there fee's you get $169.14

On modded I was making $196.74 ea after fee's

Those are some nice numbers!  I'm barely getting 450GH on 225MHZ....  300MHZ?  What firmware you on?  Mine are all max at 250MHZ

Kano's firmware. Redoing thermal paste and applying it correctly helps a lot. Also used good diamond paste.

[vh]

I'll pm zach and vh also.

thanks.   no worries here.   it's a good way to test resiliency.   
can't request these on demand for obvious reasons, so using it as opportunities.

[kano]

Should be within the next 5/10 minutes - just gotta wait for that random shift summary event

[PPOC]

Payout 392129 sent
fcea54009a18b3e4aa5d318705ab109a201d77655612d33d4a4c144b4db2b769
and confirmed

--

10.3PH................WOWOWOWOWWOWO, must be my new S7  that put us over the top.    YUP!

You said that and it dropped to 8.2ph

That's common, it's a failover from somewhere I know where, while they restart/update their ckpool code.
It got over 12PH the other day but yeah it drops all out again soon enough.

Kano, Changed my payout address about 12 hours ago, got email about the change but this payout was sent to old address. Is that because use use the address at time of block hit or at time of payment made?

[kano]

...
Kano, Changed my payout address about 12 hours ago, got email about the change but this payout was sent to old address. Is that because use use the address at time of block hit or at time of payment made?

Payout is sent to the address at the exact time the block is found.

[PPOC]

...
Kano, Changed my payout address about 12 hours ago, got email about the change but this payout was sent to old address. Is that because use use the address at time of block hit or at time of payment made?

Payout is sent to the address at the exact time the block is found.

Ok, great thanks. So next block we find will use the new address. Thanks for the quick reply!

[kano]

Should be within the next 5/10 minutes - just gotta wait for that random shift summary event

Restart complete in record time this time

Code:

[2016-01-08 13:38:30.433+11] Listener received terminate message, terminating ckdb
...
[2016-01-08 13:45:04.037+11] reload queue completed 0m 8.808s

6.5 minutes

[vh]

malform json handled, empty json values handled.   gtg for future repeats.

[bctmke]

SG and DE node users.

I've tracked down the bug in the node code that caused people to hash into thin air without failing over and have implemented a workaround for it to prevent the cause from happening. In addition I've implemented a change to make it more robust in ckpool itself at disconnecting clients connected to the node but that would warrant a ckpool restart at the main pool which isn't justified at this stage.

Apologies for the lost time when hashing on the SG node. Please give it another go and watch carefully for any issues. Thanks for your patience!

Awesome ck thanks for the update!

[hawkfish007]

Time to hit a block before the last one matures, eating grilled chicken tacos!

[VRobb]

Sorry, my fault, didn't finish my teriyaki chicken from lunch today.  Just did now, a block is sure to crack any minute now... 

[e46btc]

Sorry, my fault, didn't finish my teriyaki chicken from lunch today.  Just did now, a block is sure to crack any minute now... 

Ought!  I believe this is exactly the reason.  Please control yourself next time!

[ryen123]

SG and DE node users.

I've tracked down the bug in the node code that caused people to hash into thin air without failing over and have implemented a workaround for it to prevent the cause from happening. In addition I've implemented a change to make it more robust in ckpool itself at disconnecting clients connected to the node but that would warrant a ckpool restart at the main pool which isn't justified at this stage.

Apologies for the lost time when hashing on the SG node. Please give it another go and watch carefully for any issues. Thanks for your patience!

Ok just reconnected to SG node. Let's see if it runs smoothly.

[ZACHM]

Am I submitting shares in the future? -1s

One of my S3's died, need to troubleshoot.... 

[talks_cheep]

How many blocks per day on average are we supposed find on kano pool?