Topic: [UNRESPONSIVE POOL OPERATOR] 50BTC.com - page 69. (Read 257839 times)
my workers are marked offline after about 3-4mins no matter what i set the keepalive value to
Been down for half an hour now saying "back in a few seconds". Care to put something more accurate?
Also confirm shares are being counted would be good.
Also confirm shares are being counted would be good.
This....
Only got two GPUs working - the API reports active_workers 0, hash_rate is reported as anything from 50 - 700, sometimes number of shares changes, total_shares increases though I'm not sure if all shares are counted.
Also confirmed_reward increases (I believe I've seen it at least two times decreasing a tiny bit) though not quite as fast as I'd like it to...
Been down for half an hour now saying "back in a few seconds". Care to put something more accurate?
Also confirm shares are being counted would be good.
Also confirm shares are being counted would be good.
Would be nice if they had an irc channel or something for real time pool status.
Yes, the share counters look to be 5 minutes + behind.. My shares are increasing, but from shares I did 5 minutes ago or more, as far as I can tell. Not too worried about it atm.
Anyone seeing MH/s go down atm? It also shows my miners as not active.... yet computer is mining...
I added support today to keep track of your 50BTC wallet balances to CryptFolio. This helps you keep track of mining pool balances over time, and generates reports (such as your overall USD net worth).
Turns out I'm just a massively impatient moron, all fine now
How long did it take you from paying out to actually seeing the transaction on the blockchain? 50btc is showing me a txid that doesn't exist...
40-80 minutes, can't be exactly sure, the transaction ID they gave me didn't seem to work for me either, I can't load the site to double check right now, but I use blockchain as one of my wallets and yeah they told me about the transaction eventually, it states it took 38 minutes to confirm
Turns out I'm just a massively impatient moron, all fine now
How long did it take you from paying out to actually seeing the transaction on the blockchain? 50btc is showing me a txid that doesn't exist...
Seemed like a hourish last time i did a payout. Best not to worry watch a tv show and come back.
Turns out I'm just a massively impatient moron, all fine now
How long did it take you from paying out to actually seeing the transaction on the blockchain? 50btc is showing me a txid that doesn't exist...
Turns out I'm just a massively impatient moron, all fine now
No, I'm using stratum on 3333 - though it is with slush's stratum proxy (asicminer blades, can't do stratum) but that shouldn't matter. 50BTC still just sees stratum at the end of the day.
The share queueing seems to come and go, there's periods where every single block backups, then other times it's good going for hours. It just feels a bit like there's a database waiting to do inserts while it processes shares or something. Note I see this on any block on the network though, not just 50BTC blocks.
Packetloss seems to have cleared up now at least.
The share queueing seems to come and go, there's periods where every single block backups, then other times it's good going for hours. It just feels a bit like there's a database waiting to do inserts while it processes shares or something. Note I see this on any block on the network though, not just 50BTC blocks.
Packetloss seems to have cleared up now at least.
Anyone else seeing 40% packetloss to 50BTC at the moment?
Also seems to be load issues at every new block on the network - my shares queue for anything up to a minute, and if there's a couple of blocks in succession I can lose a good few minutes of hashing because they all end up rejected. It leads to a very visible dip in my worker hashrate graph
Also seems to be load issues at every new block on the network - my shares queue for anything up to a minute, and if there's a couple of blocks in succession I can lose a good few minutes of hashing because they all end up rejected. It leads to a very visible dip in my worker hashrate graph
Are you using the getwork/longpolling port 8332? I had this same problem but switched to stratum (3333) and have subsequently had no issues.
Anyone else seeing 40% packetloss to 50BTC at the moment?
Also seems to be load issues at every new block on the network - my shares queue for anything up to a minute, and if there's a couple of blocks in succession I can lose a good few minutes of hashing because they all end up rejected. It leads to a very visible dip in my worker hashrate graph
Also seems to be load issues at every new block on the network - my shares queue for anything up to a minute, and if there's a couple of blocks in succession I can lose a good few minutes of hashing because they all end up rejected. It leads to a very visible dip in my worker hashrate graph
The site speed for my Avalon is not correct like it has been in the past. My 24 hour average is dropping even though my miner is chugging along normally. Fix it please.
Not sure if this would help exactly, but maybe as a test switch from getwork 8332 to stratum 3333 and see how it goes.
Didn't even know that was an option. I will try that. Thanks
It's been a few hours and none of the 4 miners have had any communications problems with the stratum pool. Thanks for the advice.
Not sure if this would help exactly, but maybe as a test switch from getwork 8332 to stratum 3333 and see how it goes.
Didn't even know that was an option. I will try that. Thanks
Watching them, them seem to happen more often than not near/around a new block detected. Are the pool servers getting overwhelmed with work requests?
(this is a slow miner, but it shows the example)
[2013-05-06 12:48:33] Accepted ec784c92 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:49:07] LONGPOLL from pool 0 detected new block
[2013-05-06 12:49:18] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:49:18] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:49:28] Accepted 14747813 Diff 12/1 GPU 0 pool 1
[2013-05-06 12:49:49] Accepted e2fd1414 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:50:04] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:50:04] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:50:30] Accepted 03499f41 Diff 77/1 GPU 0 pool 0
[2013-05-06 12:50:39] Accepted e43ee9a8 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:50:41] Accepted 2ae564a9 Diff 5/1 GPU 0 pool 0
(this is a slow miner, but it shows the example)
[2013-05-06 12:48:33] Accepted ec784c92 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:49:07] LONGPOLL from pool 0 detected new block
[2013-05-06 12:49:18] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:49:18] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:49:28] Accepted 14747813 Diff 12/1 GPU 0 pool 1
[2013-05-06 12:49:49] Accepted e2fd1414 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:50:04] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:50:04] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:50:30] Accepted 03499f41 Diff 77/1 GPU 0 pool 0
[2013-05-06 12:50:39] Accepted e43ee9a8 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:50:41] Accepted 2ae564a9 Diff 5/1 GPU 0 pool 0
Not sure if this would help exactly, but maybe as a test switch from getwork 8332 to stratum 3333 and see how it goes.
Watching them, them seem to happen more often than not near/around a new block detected. Are the pool servers getting overwhelmed with work requests?
(this is a slow miner, but it shows the example)
[2013-05-06 12:48:33] Accepted ec784c92 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:49:07] LONGPOLL from pool 0 detected new block
[2013-05-06 12:49:18] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:49:18] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:49:28] Accepted 14747813 Diff 12/1 GPU 0 pool 1
[2013-05-06 12:49:49] Accepted e2fd1414 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:50:04] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:50:04] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:50:30] Accepted 03499f41 Diff 77/1 GPU 0 pool 0
[2013-05-06 12:50:39] Accepted e43ee9a8 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:50:41] Accepted 2ae564a9 Diff 5/1 GPU 0 pool 0
(this is a slow miner, but it shows the example)
[2013-05-06 12:48:33] Accepted ec784c92 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:49:07] LONGPOLL from pool 0 detected new block
[2013-05-06 12:49:18] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:49:18] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:49:28] Accepted 14747813 Diff 12/1 GPU 0 pool 1
[2013-05-06 12:49:49] Accepted e2fd1414 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:50:04] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:50:04] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:50:30] Accepted 03499f41 Diff 77/1 GPU 0 pool 0
[2013-05-06 12:50:39] Accepted e43ee9a8 Diff 1/1 GPU 0 pool 0
[2013-05-06 12:50:41] Accepted 2ae564a9 Diff 5/1 GPU 0 pool 0
This has been happening a lot to me recently:
[2013-05-06 12:30:02] Accepted 46d12787 Diff 3/1 GPU 0 pool 0
[2013-05-06 12:30:05] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:30:05] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:30:20] Accepted 34957ca4 Diff 4/1 GPU 0 pool 1
[2013-05-06 12:30:25] Accepted f6233d52 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:28] Accepted 398a11d3 Diff 4/1 GPU 0 pool 1
[2013-05-06 12:30:44] Accepted bf6d1a6e Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:46] Accepted aff54d77 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:55] Accepted ae11e4ba Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:57] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:30:57] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:31:00] Accepted ad03956f Diff 1/1 GPU 0 pool 0
[2013-05-06 12:31:01] Accepted 5029ed46 Diff 3/1 GPU 0 pool 0
I have 4 miners on 4 different computers, and they each experience this. The times above are in US/Central. (most recent failure on a 680 mhash miner)
I only do about 2GH/s combined, and I reset my stats on BTC guild last night about 12 hours ago, and since then, I've failed over to them enough to submit 895 shares.
I saw a post a few days back on the previous page as well on this same topic.
[2013-05-06 12:30:02] Accepted 46d12787 Diff 3/1 GPU 0 pool 0
[2013-05-06 12:30:05] Pool 0 http://pool.50btc.com:8332 not responding!
[2013-05-06 12:30:05] Switching to pool 1 http://stratum.btcguild.com:3333
[2013-05-06 12:30:20] Accepted 34957ca4 Diff 4/1 GPU 0 pool 1
[2013-05-06 12:30:25] Accepted f6233d52 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:28] Accepted 398a11d3 Diff 4/1 GPU 0 pool 1
[2013-05-06 12:30:44] Accepted bf6d1a6e Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:46] Accepted aff54d77 Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:55] Accepted ae11e4ba Diff 1/1 GPU 0 pool 1
[2013-05-06 12:30:57] Pool 0 http://pool.50btc.com:8332 alive
[2013-05-06 12:30:57] Switching to pool 0 http://pool.50btc.com:8332
[2013-05-06 12:31:00] Accepted ad03956f Diff 1/1 GPU 0 pool 0
[2013-05-06 12:31:01] Accepted 5029ed46 Diff 3/1 GPU 0 pool 0
I have 4 miners on 4 different computers, and they each experience this. The times above are in US/Central. (most recent failure on a 680 mhash miner)
I only do about 2GH/s combined, and I reset my stats on BTC guild last night about 12 hours ago, and since then, I've failed over to them enough to submit 895 shares.
I saw a post a few days back on the previous page as well on this same topic.
Jump to: