URGENT: The following people are doing invalid OGR stubs!

[bphantom]

This is the list of email addresses that are using client version 8007 and are processing invalid OGR stubs (Submitted through Mika's PProxy)!!! Please update or disable OGR on these machines ASAP! This is a thread spawned off from BoberFett's thread: http://forums.anandtech.com/messageview.cfm?catid=39&threadid=198445

New clients are located at: http://www.distributed.net/download/clients.html

Domain names have been abbreviated:

alan@mai*
ctll@net*
david_moore@cab*
ddutcher@sym*
DegenerationX@__hot*
DegenerationX__@hot*
deharris@col*
dragonw@gte*
edurant@eng*
Engineer@wil*
Greg_Jordan@msn*
jarendt@min*
jeffli@med*
jimduncan@hom*
kkelson@mic*
lkrieg@min*
mail.mail.002@mai*
manderso@sha*
marti@myf*
mindless_@yah*
mmflash@hom*
moonshadow97@mai*
morten@mai*
obrienjd@big*
outfits@net*
rbruce@tri*
robert_b@min*
sigurd.borge@c2i*
socrplyr@neo*
srathbun@hom*
thecool1@hom*
thejoker@xmis*
thomas.lan*
tmr@xmi*
tontod@hot*

Brad..

 

[ViRGE]

I'll try to get Mika and the BB's to upgrade their pproxies ASAP.

 

[RaySun2Be]

Ack! I'm on the list.

Unfortunately, I can't get to it until tomorrow for the home herd, and Monday for the work herd 'cause I'm out of town.

 

[ViRGE]

Don't worry about it Ray, if we can get Mika and the BBs to upgrade before then, your cows will be fine on their own.

 

[Outfits]

So I've been cracking invaild stubs for the last day ? That sucks,what a waste. Changed my config back to RC5 only. Thanks for the info.

 

[BoberFett]

My pproxy has been updated to 318

 

[imported_CyberWire]

my pproxy is updated to 318 also

 

[Jator]

Ditto!!!

 

[HeavyIron]

Pproxy updated to 318, and all but two clients are running the newest version, 8010.

I have two clients that are unreachable, (one is in Mexico!), and they are running client v2.8009-460.ctr-0060723.
Is that version current enough to flush acceptable blocks? It's a 8009-460, but I got it on 6/10/2000.
They are undoubtedly flushing OGR units, nothing I can do to change it. They flush to Mika's anyways so his updated pproxy will switch 'em back to RC5 if they're too old.

 

[ViRGE]

The 460's are vaild HeavyIron, so you'll be fine.

 

[mindless]

OK Ive been a bit busy the past week or so and havent kept up on stats and whatnot for RC5, and Im on the list for old clients. I have no problem with being on the list as its a computer that sits about 15 feet from where Im typing and will take me 2 seconds to fix.

But what I dont understand is WTF is OGR? and what happened to RC5? Am I still cracking for RC5?

Sorry for all the questions, I just walked in from work and now Im confused as to what is going on.

 

[ViRGE]

OGR is Dnet's secondary project(check their website for what its about). The old clients used to do it, but due to an obscure bug, it was temporarily canceled. Over time, Dnet has released new clients that are fixed, and they relauched it ~24hrs ago. However, the "start" sign is generic, which ment all the old clients started back up when they saw it(as it has a higher contest priority than RC5). But due it the bug, they don't count. Dnet has released new pproxy software that'll tell the old clients that the contest is "closed", so they won't start on it, but until we've installed that software, the clients need to manually be set to not crack OGR by adding "=0) to the end of "OGR" in the contest priority list. This'll make sure the client(and any future clients using that INI file) will not do OGR, and instead do RC5(which is the only other active contest). So in short, no, at the moment, you're not doing RC5. But as long as you adjust your client as reccomended above, you'll be back to RC5(which is still alive and kicking).

 

[mindless]

Thanks Virge, I had just assumed the Phf had cut back a little on me yesterday, time to go change my settings to get back into rc5, Im going to find that darned key

 

[Dantoo]

Virge

Help me get this straight. All my clients were installed in the last couple of months. I just can't get at all the machines face to face to check version number. I've avoided putting the latest version (462?) on most of them because when Mika's pproxy is down it reverts to flushing to dnet after about 3 tries, despite my attempts to stop it.

I've been on the phone to the machine owners trying to get OGR under control. It's going to be days before this is finished, at best. I now see that even the OGR blocks they're doing are duds.

Are you saying here that I can stop worrying now because you can trick them into shutting down ORG by remote?

 

[BoberFett]

Dantoo

Once everyone on the team who provides proxy services updates their software, the problem will straighten itself out and your cows that can't do OGR will revert back to RC5.

 

[Xtremist]

Okay, I have no idea if I'm doing it right anymore or not. I just updated to the newest client though. But it says something about RC5 AND OGR... So which am I doing? I guess I could wait for a batch to get done, but I don't wanna I'm thinking RC5, but I'm not sure... And if so, you can take the mmflash off that list Cheers!

[Jul 15 02:29:23 UTC] Automatic processor detection found 1 processor.
[Jul 15 02:32:39 UTC] Connected to mika.dhs.org:2064...
[Jul 15 02:32:39 UTC] The perproxy says: "Team AnandTech pProxy!"
[Jul 15 02:32:40 UTC] Retrieved RC5 work unit 24 of 24 (100.00% transferred)
[Jul 15 02:32:50 UTC] Retrieved OGR work unit 24 of 24 (100.00% transferred)
[Jul 15 02:32:50 UTC] Automatic processor type detection found
an AMD K7-2 processor.
[Jul 15 02:32:50 UTC] RC5: using core #6 (RG/HB ath).
[Jul 15 02:32:50 UTC] Loaded RC5 5*2^28 packet BA7C7B24:60000000
[Jul 15 02:32:50 UTC] 3 RC5 packets (19 work units) remain in (memory-in)
[Jul 15 02:32:50 UTC] 0 RC5 packets (0 work units) are in (memory-out)
[Jul 15 02:32:50 UTC] 1 cruncher has been started.
.....10%.....20%.

 

[JonB]

Xtremist, your text clearly shows "[Jul 15 02:32:50 UTC] Loaded RC5 5*2^28 packet BA7C7B24:60000000"

you are running RC5. Crack on!

 

[Hector13]

<<
Xtremist, your text clearly shows &quot;[Jul 15 02:32:50 UTC] Loaded RC5 5*2^28 packet BA7C7B24:60000000&quot;

you are running RC5. Crack on!
>>



Doesnt the fact that his client retrieved OGR blocks mean that it will start crunching OCR when he is out of RC5 blocks and then return to RC5 after a flush?

If you havent already, I think you need to add the following line to your INI file:

project-priority=RC5,OGR=0,DES=0,CSC=0

 

[Xtremist]

I'll go ahead and add that into the config, thanx

 

[Dantoo]

Thanks BoberFett.

I'm trying to stay relaxed

I'll monitor the OGR stats and see if they level out for me. I do really want to keep all my effort on RC5 til it and /. are licked. After that, I think I'd like to help to boost the SETI guys up to the top. I know I have at least two 500Mhz+ machines out of control at the moment and the owners not contactable for days yet.

You know, distributed computing is always interesting. Crack-racks, Phantom Flushers, Big Bad Borg, crazy out of control clients - exciting yes, but everything seems so awfully agonisingly alliterative!

 

[SocrPlyr]

ok guys i think i got mine fixed
cept for the clients i can't see so i should have no prob for a while anyways (all the blocks were coming from my house and it was my second computer so it is fixed)

josh

 

[ViRGE]

Dantoo, 1 thing you need to know is that only pre-460 clients will stop on their own. If you have any 460 clients, those will crack OGR(and RC5 after it finishes its OGR supply) unless OGR is manually disabled.

 

[ZapZilla]

What a mess! I won't be able to get to 'em before next friday. I've got some very old Mac clients in my herd.

 

[NOX]

Hmm...I just noticed that I'm cracking OGR packets also? Damn, this is getting nuts!

 

[NOX]

Ok...I think I fixed it, it's reporting RC5 now, and not OCR.