Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 143. (Read 1601330 times)

It seems to be returning to normal now

Assume DDoS.

Cheers,
Kermee

The hashrate in my sig should be 2400+..... this is annoying.

agreed something is definitely not right. I'm down about 4g/hash sec right now and I'm getting those same messages across all my miners in the farm. DDoS?


as I wrote this I came back to edit 20 seconds later I'm down another 2g hash :(something is def crapping out.

its getting worse...  my miners are disconnecting very frequently now

Getting 5 times the amount of stale shares the last day or two, compared with the last week!!!

Mostly "Warmning: work queue empty, miner is idle"

and

"MSG: Deepbit is temporarily unavilable"

Get these messages once a minute.

Please advise.

same here ,  hiccups every so often


Jen

I think I'm getting them too.

2011-07-21 22:54:14: Listener for "xrcode_GPU2": 21/07/2011 22:54:14, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:54:18: Listener for "xrcode_GPU2": 21/07/2011 22:54:18, warning: job finished, miner is idle
2011-07-21 22:54:31: Listener for "xrcode_GPU2": 21/07/2011 22:54:31, long poll: new block 00000004ebd6466f
2011-07-21 22:54:31: Listener for "xrcode_GPU1": 21/07/2011 22:54:31, long poll: new block 00000004ebd6466f
2011-07-21 22:54:32: Listener for "xrcode_GPU2": 21/07/2011 22:54:32, Using new LP URL /listenChannel
2011-07-21 22:54:32: Listener for "xrcode_GPU2": 21/07/2011 22:54:32, LP connected to pit.deepbit.net:8332
2011-07-21 22:54:47: Listener for "xrcode_GPU1": 21/07/2011 22:54:47, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:55:18: Listener for "xrcode_GPU1": 21/07/2011 22:55:18, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:55:39: Listener for "xrcode_GPU2": 21/07/2011 22:55:39, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:56:40: Listener for "xrcode_GPU2": 21/07/2011 22:56:40, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:56:45: Listener for "xrcode_GPU1": 21/07/2011 22:56:45, warning: job finished, miner is idle
2011-07-21 22:57:09: Listener for "xrcode_GPU2": 21/07/2011 22:57:09, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:57:14: Listener for "xrcode_GPU2": 21/07/2011 22:57:14, Problems communicating with bitcoin RPC 1 2
2011-07-21 22:57:42: Listener for "xrcode_GPU1": 21/07/2011 22:57:42, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:58:38: Listener for "xrcode_GPU1": 21/07/2011 22:58:38, java.util.concurrent.TimeoutException: Timed out(1000) waiting for operation
2011-07-21 22:58:40: Listener for "xrcode_GPU2": 21/07/2011 22:58:40, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:58:55: Listener for "xrcode_GPU2": 21/07/2011 22:58:55, java.util.concurrent.TimeoutException: Timed out(1000) waiting for operation
2011-07-21 22:58:59: Listener for "xrcode_GPU1": 21/07/2011 22:58:59, Problems communicating with bitcoin RPC 0 2
2011-07-21 22:59:04: Listener for "xrcode_GPU2": 21/07/2011 22:59:04, Problems communicating with bitcoin RPC 0 2
2011-07-21 23:00:26: Listener for "xrcode_GPU1": 21/07/2011 23:00:26, Problems communicating with bitcoin RPC 0 2
2011-07-21 23:00:37: Listener for "xrcode_GPU1": 21/07/2011 23:00:37, Problems communicating with bitcoin RPC 0 2
2011-07-21 23:03:11: Listener for "xrcode_GPU2": 21/07/2011 23:03:11, warning: job finished, miner is idle
2011-07-21 23:03:15: Listener for "xrcode_GPU2": 21/07/2011 23:03:15, Problems communicating with bitcoin RPC 0 2
2011-07-21 23:04:27: Listener for "xrcode_GPU1": 21/07/2011 23:04:27, Problems communicating with bitcoin RPC 0 2
2011-07-21 23:06:33: Listener for "xrcode_GPU1": 21/07/2011 23:06:33, Problems communicating with bitcoin RPC 0 2

Anyone else getting weird connection problems for the past 30 min? Seems to keep on chugging but every few minutes it has a lil hiccup. Just fyi, no big deal in terms of work loss. Anyone else having similar issues or should I take a look at my own net connection?

Status: 12 confirmations
Date: 7/21/2011 20:02
From: unknown
To: 1HzSDnSwPbBxZBmUr38tB59jymqN44e7Kf (yours, label: Deepbit)
Credit: 1.08872547
Net amount: +1.08872547




Tested full precision payments out of curiosity, 100% working no problem! If there was a problem it appears that Tycho has fixed it.

Could be two things...

#1. The 2 workers are accidentally logging in as another worker(s).
#2. You have the 'idle timeout' set lower than when shares are actually being submitted. (i.e. 'Idle Timeout' set to 1 minute; your worker is submitting shares every 3-4 minutes.)

Cheers,
Kermee

2 of my workers have been in red for the past couple days but my Mhash/s has been the same.

Thanks for your report, now I see it in my log file.

I'll post an additional notice when this issue will be fixed.

I've had issues where I cut and pasted my full decimal bitcents and it only did it down to 2 decimals, then later I tried it the exact same way and it did it to 8 decimals...  There's definately something awry there where it only kicks out payments to 2 decimals vs. the full amount you put in...

PM Sent

PM me your login name.

I just added some checking code to debug this.

Fixed.

it was yesterday, and i put 0.01802166 in the payout box, but it did not work

Just out of curiosity, it's been way over 24h since the difficulty adjustment, why are there still no "deviation from the expected average" stats show at the top of the stats page?

Is your balance greater than 0.01 BTC or not ?
The payment can't be less than 0.01 BTC

I just checked it myself and ensured that full precision payments are working fine.