[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[Meatball]

Main reason I decided to pool was so I could not worry about my primary bitcoind machine going down and everything stop working

[innervisi0nn]

Main reason I decided to pool was so I could not worry about my primary bitcoind machine going down and everything stop working

Once you download the blocks, if you have downtime, it just picksup where you left off right?

[dacoinminster]

I'll be soloing today. Finally have my 2nd setup to bring me to 1.3 ghash/s. Enough for solo, bigger rewards.
With that much power that you mentioned, why pool? (unless you like daily payouts)

Variance can absolutely KILL you if you get unlucky. The blocks I've found for the pool are only worth 86% of the bitcoins I've been paid by the pool. It seems I got lucky (although I might have gotten lucky mining solo too). I just don't have the stomach to mine for days on end never knowing when I might find a block. One really long unlucky streak will sour you to mining solo.

Also, it's really nice to be able to remotely monitor all your miners with my greasemonkey script (don't forget to donate if it makes your life easier)  

[Meatball]

Yeah, but then I'd have these machines running idle for a while.  Of course, I've already 'found' 2 blocks for the pool, so while it's likely I wouldn't have found those anyways, I get this nagging feeling I could be seeing 100 BTC in my wallet.

No worries, don't want to derail the thread too far off topic.  I'll give solo'ing a whirl for a week and see how it goes

[dclinton]

Trying to join the mining pool but having problems. I've set up my account on mining.bitcoin.cz, added a worker for my machine and am running DiabloMiner connecting to http://mining.bitcoin.cz:8332 with the user and password for the worker. However, I keep getting the error message "ERROR: Can't connect to Bitcoin: Bitcoin returned unparsable JSON" from DiabloMiner.

If I inspect the http response from mining.bitcoin.cz it always contains '{"error": {"message": "Error during login, new database lookup in 119 seconds", "code": -129}, "id": "1", "result": null}'

The "seconds" count will tick down on each request, but when it reaches 0 it just starts again at 180 seconds or so.

Can anyone advise on what the problem might be?

I'm running on OS X 10.6.7

Thanks.
Doug

[dishwara]

I am getting more stales in slush pool, than in other pools.

slush:807 accepted, 47 stale
deep:2941 accepted, 18 stale
bitcoinpool:1586 accepted, 40 stale.

[datguywhowanders]

I could definitely be wrong, but I believe that makes a good argument for long polling.

[MiningBuddy]

Long polling upgrade is long overdue in my opinion and very much needed.
I have 35ms ping to servers and this is an average day:
[6003 Accepted] [442 Rejected]
[3373 Accepted] [230 Rejected]
[3352 Accepted] [252 Rejected]
[3290 Accepted] [241 Rejected]
[3411 Accepted] [224 Rejected]

[wuffer]

I got an email that 0.55 bitcoin was transfered to my wallet from http://mining.bitcoin.cz/ , that was 2 days ago and it hasent showed up yet??

[yuancraft]

hi why i see so much

warning: job finished, miner is idle
problems communicating with bitcoin rpc

and i in vietnam
python OpenCL bitcoin miner

i didn't see this before

[MiningBuddy]

I see alot of the same as yuancraft recently (past 4 days).
Only for a few second outage, but every second not mined is no btc earned! 

[Jack of Diamonds]

Same problem as above. Server issues roughly every few minutes since the last couple of days.

Doesn't happen on other pools. Also recieving 'problems with bitcoin rpc' about 20 times per hour, hash calculation will drop to zero and then pick up again.

[ranwanimator]

Same problem as above. Server issues roughly every few minutes since the last couple of days.

Doesn't happen on other pools. Also recieving 'problems with bitcoin rpc' about 20 times per hour, hash calculation will drop to zero and then pick up again.

Ditto.

Plus, I'm wondering if these connection problems are seen by the server as disconnects and are negatively affecting our share rates for the new "anti-cheat" payout calculations.

[slush]

Hi, I'm solving this issues on load balancer, should be better in few hours.

[no_alone]

Me also...
Maybe this is way last block took 3:05 hours

[slush]

Maybe this is way last block took 3:05 hours

No, shares are still counting. It may of course affect total pool hashrate, but not shares per round ratio....

[slush]

Pool will be down for ~15 minutes, I need to upgrade load balancer. Second load balancer will be in failover setup soon, which will prevent such outages in the future. I'm sorry for troubles...

Update: Talking with Linode support, we reached some soft limits on network layer. I'm negotiating rising of those limits, which should fix packetloss and timeouts. Stay tuned...

[pokermon919]

Glad you're on top of it, I was about to jump ship if this went on for another day.

[MiningBuddy]

Update: Talking with Linode support, we reached some soft limits on network layer. I'm negotiating rising of those limits, which should fix packetloss and timeouts. Stay tuned...

Good to hear Slush, we love you 

[datguywhowanders]

I know you've got a lot on your plate, Slush, but any word on long polling? I remember seeing a post from you a while back that you were making preparations for it.

I don't know enough about it, but might that no help alleviate some issues on your end by increasing pool efficiency?