Something Screwy With OK's Proxy ?

[Darkone]

Guys,

Is somethign screwed with OKs proxy ? It seems that the queue that was The_One's queue, is no longer his queue, and all the machines here in the office have been crunching away as the user Dazmite (who is part of TA so its not all bad...).
It seems that the SQ at OKs end has become screwed, when our SQ here in the office (which is behind a lot of security, so theres no way he would have been able to connect to our internal SQ) connected to OK's proxy to get more WUs, its passed down Dazmites user_info.sah file and that has propogated to all the machines here in the office...

I seem to remember reading a post the other day regarding someone who had a shortcut in IE set to their queue on OKs proxy and now it displayed someones elses info...????????

Does anyone else have any problems like this.. As a check, anyone using OK's proxy might want to check their .sah files to make sure theyre still crunching in their names......

Regards...

D1...

PS: I'm in NO WAY accusing Dazmite of doing anything wrong.. I'm sure he hasn't, so please, no one take it out on him.. i'm sure its a SQ problem..... And as for OK.. well we always appreciate all his efforts! Keep banging away at it dude... it'll come right soon!

 

[micron]

I think that happened to others as well. It didn't happen to me, but I have quite a few missing WUs.

 

[Engineer]

Bump for good info!

Thanks Darkone......the Queue has had it's share of problems this week

 

[Poof]

Believe you me, I have Setiqueue on my 2K AS and I know what OK is going through. I had to reinstall last week and finally found that my problem was a bad stick of RAM (which was duly replaced). Until then, the server was BSODing and rebooting continually, causing alot of file fragmentation and eventually file corruption.

With all the people who flush through OK's queue, any type of file corruption could mean probs like you're seeing. The same thing happens with large RC5/OGR pproxies and their logs (been there, done that... ).

 

[GunDog]

<< I think that happened to others as well. It didn't happen to me, but I have quite a few missing WUs. >>



I also have a few WU's missing in action.
I dont really care about the WU's for myself, but I'm missing about 15-16 WU's that would be counting towards the race. Every WU is needed, didn't start running Seti again until I heard about this race.. Trying to do my part for the team. (even though I'm a relative noob).

Force

 

[The_One]

maybe its a flawed idea then? unless you have a extreamly robust and very powerfull box with enough storage, and an Inet connection that copes with the conections. pity

 

[mboy]

I am missing somewhere in the 15 wu neighborhood as well. I had one comp going to the ta.seti proxy, but just changed it to go no proxy. The other is still pointed towards OK's, but will change that tonite as well.

 

[Darkone]

thanks for the posts guys.. I dont want this thread to be another one of missing WU posts... there is one already for that.... just adding some information for people...

 

[Darkone]

bump (one and only time) for the yanks who are just waking up and haven't checked their .sah files!

 

[Shuxclams]

<< Believe you me, I have Setiqueue on my 2K AS and I know what OK is going through. I had to reinstall last week and finally found that my problem was a bad stick of RAM (which was duly replaced). Until then, the server was BSODing and rebooting continually, causing alot of file fragmentation and eventually file corruption. >>



I have had some similiar problems, I changed out the memory as well, but guess what..... you guessed it, I have had intermittent problems with BSODS on an otherwise superstable dually / W2K Server. I have "seemingly" cut down on that issue by NOT being connected all the time. Seems that when the Q is connected to berkeley it is suseptible to crashes(?). I don't know what exactly that means, but I was wondering how many of us have had this issue?










SHUX

 

[Russ]

I guess I've been pretty lucky so far. Mine's been up for 76 days without a glitch. Of course, now that I've said that, it will probably crash.

Russ, NCNE

 

[Engineer]

<< I guess I've been pretty lucky so far. Mine's been up for 76 days without a glitch. Of course, now that I've said that, it will probably crash.

Russ, NCNE >>



You do seem to have the nack for it! :Q

and bump too!

 

[Poof]

I guess I've been pretty lucky so far. Mine's been up for 76 days without a glitch. Of course, now that I've said that, it will probably crash.

Previous to the RAM stick going bad, I had an unbelievable 300+ day uptime with 2K AS. :Q

But having hardware problem like bad RAM (which is often tricky to diagnose), sucks.

 

[Sukhoi]

I just checked every user_info.sah on my C433 and P133, and they're all fine. I'll check my P166 MMX a bit later, but I expect it to be fine too.

 

[Fardringle]

I'm missing quite a few WU's as well. I'll check all my clients to be sure they are still cracking for me. Thanks for the info, DarkOne!

 

[Baldy18]

I have these new clients in my stats that I don't recognise please check and see if they are yours.

cd4309-a.sxflls1.sd.home.com <------Looks like this one is from Sioux Falls, South Dakota
a0hc44bwy57ah.bc.hsia.telus.net
ool-43522476.dyn.optonline.net
212.250.100.124