Something up with d-net & submitted blocks?

[GeoffS]

Read further down for Friday update! Something is still fishy!

Since Oct 26 06:28:47 UTC, I have been sending blocks to "Team AnandTech pProxy!", however I have not been receiving any blocks (and therefore munching on random blocks). I have 0 packets in my buff-in, but when I try to update the buffers, I get "Input buffers are full (or project has closed)" Anyone know what's up? Is the project finished (doubtful!).

Thanks!

 

[TwoFace]

GeoffS:

It probably has something to do with this: Key server outage? thread...

With love and respect your fellow TA member

Two-Face

 

[GeoffS]

Thanks....we posted at almost the same time

 

[TwoFace]

NP

/me likes having nothing to do at work... just waiting for an email

Two-Face

 

[jinsonxu]

Sigh, the Dnet stats are down too, so boring.

Oh my, i just checked Dnet's stats, there appears to be something wrong, it's only recording 1/3 of the blocks that was sent for my team yesterday! Unless Mika didn't send the blocks in time, then there's something weird here.

 

[jinsonxu]

To add to it, look at TA's stats! I can't believe it

AnandTech completed 978,441 blocks yesterday at a sustained rate of 3,039,910 Kkeys/second!
AnandTech is ranked #4 for yesterday!
The odds are 1 in 42 that this team will find the key before anyone else does.

 

[GeoffS]

Ouch!

 

[jinsonxu]

there's something horrible happening at Dnet's stats!

Either that or there's a serious blockage at Mika's!!!!

Eg. Yesterday was my team's best day, our stats at Mika's were 600 blocks more than the day before.
BUT dnet only recorded 1/3 of the blocks~!!
Don't tell me we're unlucky enough to get so many randoms?

 

[JHutch]

Just wait until the stats run tomorrow. The blocks got stuck in Mika's. When they all flush tomorrow, we should have one hell of a day!

JHutch

 

[GeoffS]

... hope they don't get reassigned But I don't know what the threashold for reassignment is.

 

[Engineer]

GeoffS,

D.net re-assigns blocks after 90 days...Might be a good day tomorrow

 

[jinsonxu]

Think we can make 2.5 million tomorrow?

 

[GeoffS]

I noted that last weekend, when my network changed and my small herd munched on random blocks for two days, dnet only recognized about 2/3 of the blocks that I send through Mika. That indicated to me that there must have been some duplication somewhere... maybe within my herd?

 

[SSP]

I guess 1.8M blocks for tomorrow. Any more guesses?

 

[Engineer]

I go with 2.15 million

 

[jinsonxu]

UhOh, there's eithe rsomething wrong again or my team was unlucky enough to be cracking randoms for 2 days in a row.

The dnet stats again reported my output as 1/3 of what i had uploaded to Mika's! grr

 

[GeoffS]

wtf??? Wed I sent up 3884 blocks, Thu 4035. dNet says only about 1k and 1.6k. What's going on? I had NO randoms yesterday on any of my herd! What's going on???

 

[GeoffS]

double #@$(*&#$ post

 

[PeterN]

I think we are experiencing problems with both Mika's and DNet proxies.

Let's wait for a few days and see if the disappeared blocks will emerge from the depth of cyberspace. If they ar send in, history has taught that eventually they will show up, as long as they aren't randoms.

Peter

 

[GeoffS]

Guess I'm not the only one

 

[dkappos]

I am about 60% down at DNet

 

[Moose]

Please hold on a bit. we have one proxy that is backed up 3million blocks currently. Its not been flushing back properly since the 25th.

This will take awhile to get flushed. Please hang in there...

just a reminder for people not to hard code to one proxy.

moose

 

[Engine]

Yep.. we should've checked the proxy status at dnet:

proxy1.madsn.wi.us bob 5.3m 321 1.4h 1371.66 3602353/2883341

 

[GeoffS]

moose: I am not clear on the comment about hardcoding to a particular proxy. As far as I can tell, I don't have any reference to the proxy in Madison anywhere in my configuration... some clarification would be appreciated.

Thanks!

 

[JHutch]

You may not, but a proxy somewhere upstream may have. It looks like Mika's got "stuck" on that proxy a couple days ago. This can happen when a DNS server doesn't update pointers properly. I've also see a PC get "stuck" on the idea that a specific IP was the only IP for a particular domain name and the only way to get it updating correctly was to reboot.

So, in this case, I doubt it was anything anybody did wrong. Just a very bad luck combo of Mika's proxy getting "stuck" on a proxy that got severely constipated....

JHutch

PS I still think the DPC are somehow directly responsible! It's a conspiracy, d@mn it!