[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[tubexc]

This pool has been reported as a sick pool at least in Europe

[1713954786]

1713954786

[1713954786]

1713954786

[1713954786]

1713954786

[-ck]

This pool has been reported as a sick pool at least in Europe

Pool's purring along fine. Only thing is I've blocked a few IP addresses for having bad usernames and trying to log in hundreds of times per minute.

[mylesrom]

Whats up with the reported workers?  My stats show I have 38, I only actually have 2 miners.   Pool stats show over 86 thousand.

[-ck]

Whats up with the reported workers?  My stats show I have 38, I only actually have 2 miners.   Pool stats show over 86 thousand.

That's what we in the industry call a "bug" that needs fixing. It's only cosmetic luckily but I don't have a proper fix for it yet and it will require another restart. I've been trying to do restarts only if there is a real world improvement.

[ZedZedNova]

Whats up with the reported workers?  My stats show I have 38, I only actually have 2 miners.   Pool stats show over 86 thousand.

That's what we in the industry call a "bug" that needs fixing. It's only cosmetic luckily but I don't have a proper fix for it yet and it will require another restart. I've been trying to do restarts only if there is a real world improvement.

huh, at micro$oft they call it a feature and charge extra for it.

[trebligoncemore]

How to see when it was the last pool block ?

In blockchain.info...

[-ck]

Whats up with the reported workers?  My stats show I have 38, I only actually have 2 miners.   Pool stats show over 86 thousand.

That's what we in the industry call a "bug" that needs fixing. It's only cosmetic luckily but I don't have a proper fix for it yet and it will require another restart. I've been trying to do restarts only if there is a real world improvement.

I'll be restarting again in the next hour to fix this and other minor issues still annoying me. Downtime as always should be minimal to unnoticeable.

Restarts complete. All seems fine. Come on block...

[CryptoBuddha]

GL to me and everyone here! Friday lottery time has come again!  Actually Saturday already)))    And congrats to the recent block finders!
As far as I understand, there's no more such thing as the test pool and everybody is voting for segwit and I can come back to .de node as before, right?

[-ck]

GL to me and everyone here! Friday lottery time has come again!  Actually Saturday already)))    And congrats to the recent block finders!
As far as I understand, there's no more such thing as the test pool and everybody is voting for segwit and I can come back to .de node as before, right?

Yes that's right. Both pools are now signalling segwit and there is no test pool, though I left the 13333 port open so that people don't need to change their mining settings if they had changed it.

All the pool code updates have gone smoothly and they're purring nicely. The changes were to decrease overhead in the code even further and make the two pools give each other more information, mainly to be able to submit blocks at both locations faster than ever for more rapid block propagation. People interested can observe all the code changes in the ckpool git. While the solo code is unique compared to what's in the public git, the recent improvements are common to both. All the planned improvements are complete and there are no more pending updates in the near future.

All there is now is to go back to finding blocks.

[mylesrom]

Mainpool is showing dead again....   de pool is up

[Maicol792]

de.ckpool.org is up.... but solo.ckpool.org for me is down and for rent on miningringrentals sha256 I have problem whit my rent don't connect

[o_solo_miner]

maybe a short outtake of dns, from germany both pools are ok

[-ck]

de.ckpool.org is up.... but solo.ckpool.org for me is down and for rent on miningringrentals sha256 I have problem whit my rent don't connect

No sign that there is anything wrong with the pool at the moment. It appears there may have been a connectivity issue for half an hour there. On the other hand, as the solo website says, for incompatible rental services that don't support redirection, use port 3334.

[HagssFIN]

I'm pointing 500Th/s at the DE pool for ~6 hours 

[HagssFIN]

http://de.ckpool.org/users/1GTUJJLRsDREgPB6rUikHoNCRN2wEF4b9u
http://solo.ckpool.org/users/1GTUJJLRsDREgPB6rUikHoNCRN2wEF4b9u

I'm seeing zero stats  
I have used the 3333 port previously with Nicehash rentals without any problems.

[CryptoBuddha]

Can confirm - connected to .de node since yesterday, just woke up and all units show pool alive, no failovers BUT I see zero at my stats page

Yesterday the stats page showed correct numbers

[CryptoBuddha]

UPD: when I switch to the main node, I see correct stats again. So I assume that smth is wrong with user stats for the .de node and it happened no more than 18 hours ago.

UPD: now I'm sure about that. I switched a single unit to the main node, and the rest are connected to the .de node. Guess what? I see correct stats only for 1 unit, but all of them are showing pool alive and working.

[Eagleone]

Yea at 1:16AM pacific time I had to get out of bed because the S7-LN started beeping.

In 12 months of mining I have never needed a failover pool but it's set up now.

20TH that's somewhere else probably beeped for a half hour or so (never set it up) and then reconnected when possible.

If an ant miner beeps in a garage and no one hears it did it actually beep?
...

[-ck]

Turns out it was a brain fart on my part that stopped de talking to the main pool for an extended period. It's back now and is catching up so for a brief period is showing a ridiculous hashrate over >200PH. Blink and you'll miss it though once it catches up. Everything should be back to normal shortly. Sorry.

[-ck]

Code:

[2017-01-10 12:25:04.395] Possible block solve diff 509051567661.353394 !
[2017-01-10 12:25:05.066] BLOCK ACCEPTED!            

                                                                                           
Block by 1NrV55iVXdsDwoQYLnZK7DQMbhEmFDZyeV with 760TH after 223.8% diff

https://www.blocktrail.com/BTC/block/00000000000000000228ee7b45948a123bdd647ab64c627808f604226670a7c5

A block found on the de pool. Solved and submitted fine but then it killed the de pool after it was submitted so the main pool didn't register that a block was found but it's there nonetheless.

I'll be rolling back some changes to make sure it doesn't explode again till I fix the issue.