[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 106.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: gusti on November 01, 2011, 11:26:07 AM

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

All are failing on pit.deepbit.net??

I thought your original message said that only one machine out of your farm was having problems and the rest were OK?
Confused,
Sam

gusti

legendary

Activity: 1099

Merit: 1000

Quote from: os2sam on November 01, 2011, 11:19:10 AM

Quote from: gusti on November 01, 2011, 11:15:51 AM

Quote from: sadpandatech on November 01, 2011, 11:08:17 AM

Quote from: gusti on November 01, 2011, 10:35:02 AM

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms

while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.

Hmm, I don't see how it could be a filtering problem on their side. Deepbit is going to see all of your traffic coming from your router as the one public IP. It is up to your router to route the traffic back to the correct box. I would think it is a filtering problem on your firewall/router. Unless, of course, each of your mining box's have a public IP, which would be undesirable. Then it could still be a firewall rule on that box.
Just rambling thoughts,
Sam

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: gusti on November 01, 2011, 11:15:51 AM

Quote from: sadpandatech on November 01, 2011, 11:08:17 AM

Quote from: gusti on November 01, 2011, 10:35:02 AM

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms

while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.

Hmm, I don't see how it could be a filtering problem on their side. Deepbit is going to see all of your traffic coming from your router as the one public IP. It is up to your router to route the traffic back to the correct box. I would think it is a filtering problem on your firewall/router. Unless, of course, each of your mining box's have a public IP, which would be undesirable. Then it could still be a firewall rule on that box.
Just rambling thoughts,
Sam

gusti

legendary

Activity: 1099

Merit: 1000

Quote from: sadpandatech on November 01, 2011, 11:08:17 AM

Quote from: gusti on November 01, 2011, 10:35:02 AM

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms

while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.

sadpandatech

hero member

Activity: 504

Merit: 500

Quote from: gusti on November 01, 2011, 10:35:02 AM

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms

while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

gusti

legendary

Activity: 1099

Merit: 1000

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms

while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

Quote from: gusti on November 01, 2011, 09:20:31 AM

I'm experiencing > 50% packet loss to pit.deepbit.net from only one of my servers.
Other servers are OK, any clue ?

Holy fuck.
Im doing just fine, I've got GUIminer set to Deepbit. So it kinda auto picks

gusti

legendary

Activity: 1099

Merit: 1000

I'm experiencing > 50% packet loss to pit.deepbit.net from only one of my servers.
Other servers are OK, any clue ?

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

Quote from: [Tycho] on October 30, 2011, 06:51:02 PM

Quote from: DeathAndTaxes on October 30, 2011, 03:53:40 PM

Deepbit uses a rolling 15min IIRC for speed calculation so just because it showed 2200 a day ago and now doesn't mean it was constantly 2200 over last 24 hours.

Averaging window is user-adjustable, it can be longer or shorter than 15 min.

Quote from: DeathAndTaxes on October 30, 2011, 06:45:05 PM

Wait 1,666,814 shares in 24 hours? Sure about that? That is like 80GH/s.

This number shown on stats page is average pool's shares per block during last 24 hours, not total shares (it's explained there).

Quote from: Fiyasko on October 30, 2011, 02:32:00 PM

So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

This measurement includes your personal luck, some part of pool's luck and a little bit of global network luck. It should not be used for precise calculations.

If you want it to be closer to reality, increase your averaging window to 40 or 60 minutes.

Totally fixed by slapping the "measuring device" to average at 60mins.
Thanks tycho!
(lol @00m blocks where i get .4 from them)

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: DeathAndTaxes on October 30, 2011, 03:53:40 PM

Deepbit uses a rolling 15min IIRC for speed calculation so just because it showed 2200 a day ago and now doesn't mean it was constantly 2200 over last 24 hours.

Averaging window is user-adjustable, it can be longer or shorter than 15 min.

Quote from: DeathAndTaxes on October 30, 2011, 06:45:05 PM

Wait 1,666,814 shares in 24 hours? Sure about that? That is like 80GH/s.

This number shown on stats page is average pool's shares per block during last 24 hours, not total shares (it's explained there).

Quote from: Fiyasko on October 30, 2011, 02:32:00 PM

So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

This measurement includes your personal luck, some part of pool's luck and a little bit of global network luck. It should not be used for precise calculations.

If you want it to be closer to reality, increase your averaging window to 40 or 60 minutes.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: Fiyasko on October 30, 2011, 06:39:39 PM

I have one rig running at 1108mh/s (1x6990 and 1x5830)
Another with dual 6870's running at 614mh/s
Another with another 6990 running at 828mh/s
and my brothers comp running at 198mh/s with his 5770

"Average in last 24 hours: 1666814"

Wait 1,666,814 shares in 24 hours? Sure about that? That is like 80GH/s.

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

I have one rig running at 1108mh/s (1x6990 and 1x5830)
Another with dual 6870's running at 614mh/s
Another with another 6990 running at 828mh/s
and my brothers comp running at 198mh/s with his 5770

"Average in last 24 hours: 1666814"

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: Fiyasko on October 30, 2011, 02:32:00 PM

Is anyone else's MH/s speed being Misread? I have 24/7 miners going, I've altered nothing,
By math, Im doing 2600mh/s
By Deepbit Readings, Im doing 2700mh/s
About 40hrs ago i started to be being read from deepbit as only doing 2200mhash/s
.....
So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

By math? What does your miner say.

How many shares have you submitted in last 24 hours?

Deepbit (and any pool) hashing speed indicator is based on shares (the only thing deepbit or any pool can see).

BTW: Deepbit uses a rolling 15min IIRC for speed calculation so just because it showed 2200 a day ago and now doesn't mean it was constantly 2200 over last 24 hours.

Fiyasko

legendary

Activity: 1428

Merit: 1001

Okey Dokey Lokey

Is anyone else's MH/s speed being Misread? I have 24/7 miners going, I've altered nothing,
By math, Im doing 2600mh/s
By Deepbit Readings, Im doing 2700mh/s
About 40hrs ago i started to be being read from deepbit as only doing 2200mhash/s
.....
So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

cablepair

hero member

Activity: 896

Merit: 1000

Buy this account on March-2019. New Owner here!!

cool and if your ever bored and want to mirror more stuff from the official wiki feel free to start some more pages on that wiki - back months ago when the wiki was down for a couple of days I put that up to serve as a mirror for times like that

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: cablepair on October 29, 2011, 05:46:41 AM

I think the wiki is getting DDoSd or something, its crazy slow for me

any case heres a mirror:

http://btcnetwork.com/wiki/index.php?title=BitCoin_Mining_Hardware_CPU/GPU_Comparison

Thanks, I've got it bookmarked.
Sam

cablepair

hero member

Activity: 896

Merit: 1000

Buy this account on March-2019. New Owner here!!

Quote from: os2sam on October 27, 2011, 05:30:39 PM

Quote from: btc_artist on October 27, 2011, 04:58:58 PM

Quote from: eleuthria on October 27, 2011, 04:17:13 PM

However, I will say that there is absolutely no reason anybody should be CPU mining at this time. Even with free electricity, you will wear out your components faster, especially on a laptop. You're essentially trading months/years of use of your laptop for pennies.

Fair observation. At this point I'm only mining to learn how to do it. I'll have to get a GPU or three if I decide to get serious about this.

Quote from: os2sam on October 27, 2011, 04:22:27 PM

Pretty much, except for really long blocks, hence the reason to use small PPS pool.

Thanks. I will look for a small pool to play around in.

Have fun but don't splash around too much. I would suggest a PPS pool until you get your AMD GPU's.

I was trying to get you the links to the Hardware Comparison and Mining Rig's but the site seems to be down or gone. Here are the links in case someone else knows where they are now.

https://en.bitcoin.it/wiki/Mining_hardware_comparison
https://en.bitcoin.it/wiki/Mining_rig

Sam

I think the wiki is getting DDoSd or something, its crazy slow for me

any case heres a mirror:

http://btcnetwork.com/wiki/index.php?title=BitCoin_Mining_Hardware_CPU/GPU_Comparison

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: soptik on October 28, 2011, 01:15:32 PM

I have the same problem - transaction is in payment history, but it still isn't in blockchain (searched after 1 hour). Was the deepbit payout system changed to send transaction not imediately but after some time?
EDIT: Trasaction finally arrived - after some 70 minutes.

Nothing was changed. Sometimes we have a long round and sometimes there are too many transactions to include.
It's normal. You just need to wait until it gets confirmed if you see the transaction in your payments history.

[Tycho]

hero member

Activity: 742

Merit: 500

Quote from: btc_artist on October 27, 2011, 04:11:55 PM

So what you're saying is even if I *do* solve one or two shares an hour, they will be stale/worthless, since the block will already have been solved? Makes sense.

Not worthless if your miner supports long polling. But not really profitable.
The average time to generate a share at 435 Khps is 2 hours, 44 minutes, and 33 seconds

Crypt_Current

hero member

Activity: 686

Merit: 500

Shame on everything; regret nothing.

Any plans to start merged mining?

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