Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 222. (Read 1601343 times)
May 31, 2011, 02:08:28 PM
I found the cause of this problem, working on it.
May 31, 2011, 02:00:02 PM
We have a connection problem now. Checking it...
this is why deep is my main pool, he is always here to update us when shit breaks and doesnt leave us hanging!
May 31, 2011, 01:54:18 PM
We have a connection problem now. Checking it...
May 31, 2011, 01:52:09 PM
May 31, 2011, 01:51:48 PM
Tycho you messing with the server or we having another DDoS im getting time outs the website and the miner cant get to it ether
May 31, 2011, 01:51:14 PM
Down?
May 31, 2011, 01:23:13 PM
This bug is fixed. Restart those miners again please.
Awesome, works great now thanks! May 31, 2011, 12:54:17 PM
Is it possible to add reward per minute or per hour measure to statistics table?
Reward per minute will vary wildly if you are using Proportional mode because it's different for each block.Will average value per day enough or you want it to be more detailed ? I can add "average BTC per previous 2 hours", for example.
As you are fighting those DDOS attacks my request is extremely unnecessary at the moment.
Thanks for your concern
. May 31, 2011, 12:21:53 PM
Looks like it is all good now. They were only running 130 hashes then crashing, now they seem okay. Thanks! Keep up the good work.
May 31, 2011, 11:37:41 AM
Since the DDOS, the miners I have running on a LinuxCoin distro (using phoenix), randomly stop/disconnect, no error messages nothing. There was no issues before the DDOS, and subsequent fix(es). Is there something I need to change on my end to fix this? This kills almost a 1Gh/s for me at a time and I need to find a fix.
PM me your login name, i'll check if something is in my logs about this.Also, restart your phoenixes if you didn't in the last couple of hours.
May 31, 2011, 11:33:16 AM
Go tycho go!
please only put the fee back up to 2% XD
please only put the fee back up to 2% XD
May 31, 2011, 11:28:28 AM
Tycho,
I have been following this thread pretty closely since I thought about mining and there was never a choice to be made when I had to choose a pool. You have a great system, you handle things quickly and in a fair manner (I remember reading about the 150 BTC you refunded).
Since the DDOS, the miners I have running on a LinuxCoin distro (using phoenix), randomly stop/disconnect, no error messages nothing. There was no issues before the DDOS, and subsequent fix(es). Is there something I need to change on my end to fix this? This kills almost a 1Gh/s for me at a time and I need to find a fix.
Thanks
I have been following this thread pretty closely since I thought about mining and there was never a choice to be made when I had to choose a pool. You have a great system, you handle things quickly and in a fair manner (I remember reading about the 150 BTC you refunded).
Since the DDOS, the miners I have running on a LinuxCoin distro (using phoenix), randomly stop/disconnect, no error messages nothing. There was no issues before the DDOS, and subsequent fix(es). Is there something I need to change on my end to fix this? This kills almost a 1Gh/s for me at a time and I need to find a fix.
Thanks
May 31, 2011, 10:47:03 AM
For me at least, this is not occurring once per five minutes - it's occurring continuously on the machine's I've restarted today. Those still running from before yesterday are fine.
I should add that I'm using poclbm, and getting the same error reported above (Long poll exception...No JSON object could be decoded), on every work unit, on each machine which has been restarted today. May 31, 2011, 10:08:53 AM
When will the zero fees will finish?
May 31, 2011, 10:06:28 AM
Getting this message too :
"31/05/2011 17:02:59, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded
31/05/2011 17:03:14, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded
31/05/2011 17:03:34, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded"
"31/05/2011 17:02:59, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded
31/05/2011 17:03:14, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded
31/05/2011 17:03:34, long poll exception:
Traceback (most recent call last):
File "BitcoinMiner.pyo", line 259, in longPollThread
File "BitcoinMiner.pyo", line 234, in request
File "json\__init__.pyo", line 307, in loads
File "json\decoder.pyo", line 319, in decode
File "json\decoder.pyo", line 338, in raw_decode
ValueError: No JSON object could be decoded"
May 31, 2011, 09:56:34 AM
For me at least, this is not occurring once per five minutes - it's occurring continuously on the machine's I've restarted today. Those still running from before yesterday are fine.
I should add that I'm using poclbm, and getting the same error reported above (Long poll exception...No JSON object could be decoded), on every work unit, on each machine which has been restarted today.
May 31, 2011, 08:54:48 AM
What the heck is going on?
Currently there is a little problem with DiabloMiner, it triggers the DDoS protection. Will be fixed when i'll change the protection type.Code:
times (20)
[5/31/11 1:27:38 AM] Block 8159 found on Cayman (#3)
[5/31/11 1:27:39 AM] ERROR: Can't connect to Bitcoin: Server redirected too many
times (20)
[5/31/11 1:27:38 AM] Block 8159 found on Cayman (#3)
[5/31/11 1:27:39 AM] ERROR: Can't connect to Bitcoin: Server redirected too many
times (20)
Other miners will work.
May 31, 2011, 08:38:25 AM
"long poll exception" is expected to happen today and is not harmful.
Currently long poll connection is broken every 5 minutes, this causes miner to show the error.
It won't affect your mining, you just may get a little bit more stales.
For me at least, this is not occurring once per five minutes - it's occurring continuously on the machine's I've restarted today. Those still running from before yesterday are fine. Currently long poll connection is broken every 5 minutes, this causes miner to show the error.
It won't affect your mining, you just may get a little bit more stales.
May 31, 2011, 08:21:19 AM
"long poll exception" is expected to happen today and is not harmful.
Currently long poll connection is broken every 5 minutes, this causes miner to show the error.
It won't affect your mining, you just may get a little bit more stales.
Currently long poll connection is broken every 5 minutes, this causes miner to show the error.
It won't affect your mining, you just may get a little bit more stales.
May 31, 2011, 08:08:49 AM
Is the pool still under attack? I'm using the latest guiminer and am still getting the following errors:
long poll exception
Problems communicating with bitcoin RPC
Might be you. I'm still getting shares through. long poll exception
Problems communicating with bitcoin RPC
Jump to: