• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hold on to your blocks!

C

crYnOid

Senior member
As you can see the proxys are backing up again. Hold on to your blocks, otherwise they will be going to the "US" proxys which are having the problems.
 
Hasn't mika's(teamanadtech.com) been directed towards the main keyserver so we won't be affected?

😎 😎
 
But if alot of us are flushing through the Baby bovine proxies, wouldn't it make sense for them to not flush through dnet until things settle down? Unless you want us locally to just hold onto our own blocks so as to not overload the round-robin....

Just curious what everyone thinks... 🙁
 
All of the baby bovines (mine included) flush through Mika. So, where ever Mika flushes, so do we, by association.
 
I don't understand what the two numbers mean in the buffers column. Can someone please tell me?🙂
 
The first number is the number that they have to distribute. The second number is the amount that have been flushed to them. When that second number starts to grow, it usually indicates a problem with the proxy server flushing to the main server.

I am not entirely sure which ones that Mika flushes through, but, it is just a matter of time before the blocks will be flushed and counted in the stats.

I don't know how much that helps, but, it's all I got 🙂

 
The first number is the number of blocks available for you to fetch from, the second number is the blocks that have been flushed to the proxy and have not been flushed to the Dnet server where they are logged and the data is dumped to the stat server--hence the "constipation" factor.

EDIT: 😱 gotta be quick around here--shouldn't have checked the buffer status before replying....
 
Humm, only 20K per proxy in a few proxies or so. I wouldn't get to worried guys, Dnet's probably just taking the MK down for maintainence.
 
Backlog is now close to 4M in total, with two major constipations:
proxy2.red.wa.us davehart 3.9m 321 1.1mo 23020.64 983696/2019743
proxy1.mtnview.ca.us peter 3.0m 318 5.7d 21141.81 511013/1255873

and one building up:
proxy1.madsn.wi.us bob 22s 321 1.5w 18049.24 6001299/287348
 
Moose spoke of a "network bandwith problem" the other day when the proxies backed up. It took two days to clear up. My guess is that DNet is at the limit of what the KeyServer can handle. Either because of bandwith or because of processor/IO limitations. Now before anyone says, but they've handled more RC5 keys/day in the past, those were days without large amounts of OGR. The other factor might be the size of the buffers. The "handshaking" for a small buffer is the same as for a large buffer. Check your DNETC.INI file for preferred blocksize. It should be 33 if at all possible, and your block requests a multiple of 32.
 
Well guys I am no big gun but I am going to hold all mine until things get setteled. I am getting my blocks from D Net and flushing through the baby's. Hate to see anyone loose any blocks especially me. 🙂
Bleep
 
dbalker is up but they all seems backup again. I guess a lot of blocks were submitted all over the world last night.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top