After yet more extensive debugging and fine tuning potential issues that were leading to hangs/lockups or crashes I finally found an issue that client instances could be in the process of being dropped and received messages from them would be processed ever so slightly after the drop, triggering... well, stuff. Anyway it's fixed and finally exhibiting stability in our real world pool usage and I've tagged a new milestone M10 to indicate its suitability for use.

Indeed, however we're mostly hovering at 100TH: The average time to generate a block at 100000000.0 Mhps, given difficulty of 41272873894.7, is 2 weeks, 6 days, 12 hours, 24 minutes, and 43 seconds

Recognised problem fixed in git. Try latest git.

Slowly chipping away at the bugs as they show up, found and fixed another that is worthy of a restart so there'll be yet another short bounce.

...complete

Does the tube not work directly on the pool any more? I thought I sorted that.


Anyone mining here is first mate. I have lots of first mates.

She bounces automatically when there's a problem first mate. It appears she bounced yet again.

Read the readme directly instead of from the bitbucket page which doesn't handle the line breaks properly. Those are separate commands.

Like Eleuthria, I'm not saying this is what happened here but it's worth noting that many scams used an alleged hack as en excuse for why they couldn't pay their users as well.

Reality check: You're on a forum for a cryptocurrency, i.e. money.

Good idea in principle but then big users will just register many smaller accounts. Ultimately we want to attract more hashrate with this competition too so we do want to attract big hashers.

I tried.


The pool won't even register a hashrate with that hardware.

This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=924354.0
Dupe thread

You are trying to mine for gold with a toothpick. Mining with a graphics card will cost you $1000 in electricity and then earn you 1 cent over a month which the pool will refuse to ever pay you as well. You cannot meaningfully mine bitcoin with any computer hardware you buy at a normal computer store - you must buy dedicated ASIC bitcoin mining hardware, the slowest of the current meaningful hardware today is 3000 times faster than what you are using.

Yep, she's restarted again.

Maybe but that faulty address is still trying to authorise. Perhaps you need to restart your miners for the configuration change to take.

That may be, but with the default bitcoind rules that transaction will probably not go through any pool unless you push it to a service that accepts non-standard transactions.

Probably because you're trying to pay dust payments as well.

Heh.

Things are looking much better now after a pretty major overhaul. All we need now is a block.

Thanks guys for your support, now if only we could find a block to ease at least some of the pain 

I understand your frustration but don't think we're sitting idle. Both of us have had very little sleep in a week and if you check the ckpool software repository you'll see there is massive activity there to try and get the much needed stability we all want. I've even dropped out of IRC to avoid the distraction it is having on me debugging this. This is the cost of adding features to a very complicated piece of software. Yes the software could be made simpler but the idea is to end up with software that can scale to any size. When it's not unstable, the performance of ckpool should be unparalleled in terms of the number of clients it can service without delay for the minimum amount of resources possible.

I'm very sorry to everyone that there has been downtime.