Sick SETI Cruncher - Help Troubleshoot Please

[xhale]

I have a Gateway 6500 w/1Gig of RAM, running SETI Driver and I have SETIQueue on another box. It is having problems uploading WUs, they seem to be falling in a black hole. It will crunch upload (nada) and download another WU, start crunching another WU one but nothing ever shows in the log. I have downloaded CLI and seti driver again but still no WUs completed. Any and all suggestions are welcome. TIA

xhale

PS
Captains of Crunch need all WUs we can get! We are free falling fast

 

[Smoke]

It is having problems uploading WUs

Which computer is having the problem, (1) the client w/SetiDriver or (2) the computer with the SetiQueue?

Check the "user_info.sah" file with notepad and verify it has your seti email address therein.

Look at the "Log_xxxx-xx-xx.txt" in your SetiQueue Folder and see what it says about the WUs that were uploaded and downloaded.

Report back what you find.

Are you running SETI on the SetiQueue machine? You didn't say. Is you are, what are you using to run the CLI Client on that machine.

 

[xhale]

Smokeball,

Thanks for your quick response.

Which computer is having the problem, (1) the client w/SetiDriver or (2) the computer with the SetiQueue?
- the client w/SetiDriver

Check the "user_info.sah" file with notepad and verify it has your seti email address therein.
- email address isn't but name is, all my machines are like this but this one is the only one having problems.

Look at the "Log_xxxx-xx-xx.txt" in your SetiQueue Folder and see what it says about the WUs that were uploaded and downloaded.
- Nothing in the log for this client.

Are you running SETI on the SetiQueue machine? You didn't say. Is you are, what are you using to run the CLI Client on that machine.
- Yes. SetiDriver

Looks like it is stuck on the same WU, crunching it over and over and over. But not !00% sure yet.

 

[Smoke]

Looks like it is stuck on the same WU, crunching it over and over and over. But not !00% sure yet.

Ah Ha, OK ... we could look for the culprit and delete it but why waste the time. Delete the entire contents of the Seti@Home folder on the client computer except for SetiDriver and the CLI Client.

Then start over with the normal installation routine of SetiDriver. That is going to be the quickest way to get rolling again. Bandwidth at Berk has climbed to almost 30 Mbits/sec so you'll be able to be passed through your SetiQueue to Berk for that first WU.

That ought to do it.

 

[xhale]

OK, will give it a try but I have already done this once. Will report back in the morning.

 

[Smoke]

OK, will give it a try but I have already done this once. Will report back in the morning.

Well, with that statement I'm not so dern sure we have figured this out. Hmm, you are sure the client is contacting the SetiQueue computer? How is your LAN setup? Router or what? Do you have a static IP Address? If you have a dynamic IP Address, are you using a dynamic to static service?

What is the HOST/PORT of the SetiDriver that is running on the SetiQueue machine?

 

[Eponymous]

Is Seti Driver talking to your Queue or directly with Berkeley?

If it is talking to Berkeley then you wouldn't see anything in the Seti Queue.

 

[Smoke]

I'm afraid he's off deleting the contents of his Seti@Home folder right now. I just checked his SetiQueue and he has 12 Clients :Q but he's only averaging 13.3 WUs a day? That doesn't sound just right.

He may have gone to bed ... said he'd check back in the morning.

 

[xhale]

Smokeball, Yes, I am sure it is talking to my SETIQueue computer. Router to cablemodem all machines are on the same segment using DHCP. I am not using a dynamic to static services. SETIQueue, 192.168.123.184:5001.

Eponymous, correct all my non-remote machines are pointing to my SETIQueue computer.

History: This machine was working fine for a month or so. I noticed the problem once I set up my SETIQueue. It started with every other WU missing or stuck, then 1 WU a day (previous 3 or 4), then none. Sunday I created a new folder and downloaded CLI & SETI Driver but the problem didn't go away just got worse.

 

[Smoke]

Have you tried to let the problem computer bypass the Q and just go directly to Berk? Just to see if it working.

I noticed the problem once I set up my SETIQueue

Is that IP Address (192.168.123.184:5001) your internal LAN address of the SetiQueue machine? Must be because I couldn't ping it.

Are any of your clients outside of your LAN?

 

[xhale]

Have you tried to let the problem computer bypass the Q and just go directly to Berk? Just to see if it working.
- No, but I did uncheck Auto Transmit and Ready to Transmit stays 0.

Is that IP Address (192.168.123.184:5001) your internal LAN address of the SetiQueue machine? Must be because I couldn't ping it.
- Yes, internal LAN addy.

Are any of your clients outside of your LAN?
- No.

 

[Smoke]

No, but I did uncheck Auto Transmit and Ready to Transmit stays 0

How long has it been working on the current WU? What percent done? What is the CPU of this machine? Memory?

Maybe you ought to chuck the whole Seti@Home folder. Get a new SetiDriver.exe and a new CLI Client and start over ... going directly to Berk. Don't use AUTO TRANSMIT so you can watch your numbers at Berk when you do click TRANSMIT.

We have got to be sure this machine is working before we troubleshoot the SeitQueue connection. And it sounds like the other clients are working through the Q with no problem. Right? If that's so, then the Q is all right.

Let's go with a completely new SetiDriver install ... direct to Berk. And see if that works.

 

[xhale]

How long has it been working on the current WU? What percent done? What is the CPU of this machine? Memory?
- 15 minutes or so. 3.5%. PIII 933MHZ, 1GB

Maybe you ought to chuck the whole Seti@Home folder. Get a new SetiDriver.exe and a new CLI Client and start over ... going directly to Berk. Don't use AUTO TRANSMIT so you can watch your numbers at Berk when you do click TRANSMIT.
- OK, per your instructions I nuked everything but SetiDriver.exe and CLI. I downloaded both to a new folder Sunday and started over.

We have got to be sure this machine is working before we troubleshoot the SeitQueue connection. And it sounds like the other clients are working through the Q with no problem. Right? If that's so, then the Q is all right.
- Yes all others appear to be working fine throught the Q.

Let's go with a completely new SetiDriver install ... direct to Berk. And see if that works.
- OK, starting over again!

FYI: It will take this machine 6-7 hours to crunch a WU and the first one will go fine but the following ones have been the problem.

 

[Smoke]

Set it up and let's see what it has done tomorrow. Remember, don't use Auto Transmit. You will want to monitor your uploads to Berk.

Let's give it a day of working that way then we can try the Q.

 

[xhale]

It's stuck on the first WU. :disgust:

 

[Smoke]

Well, at least we know it has nothing to do with your SetiQueue ... don't we?

So let's examine this computer.

Is it running just fine beyond SETI?
Identify CPU?
Identify OS?
Identify Memory?
Check the temps of the CPU while you are at it.

 

[xhale]

Is it running just fine beyond SETI? yes
Identify CPU? Intel PIII 933 (Gateway 6400)
Identify OS? Windows XP Pro
Identify Memory? 2ea 512MB 133MHz SDRAM Reg ECC
Check the temps of the CPU while you are at it. Haven't opened it but will later and report temp.

 

[Smoke]

Haven't opened it but will later and report temp.

Use Mother Board Monitor ... nothing to open. Of course you could just enter SETUP and the bios should show you your temps (though at idle and not running SETI) MotherBoard Monitor Link

Let's get some "real" help in here. I'll be back. /terminator voice/

 

[xhale]

CPU temp is 40C (SETUP/bios)

 

[Smoke]

I've got my "chief trouble shooter" on the way.

He has to wake up first. :Q

 

[Crazee]

Are you doing any overclocking on this machine? I know most of the time when weird situations like this happen then the machine is overclocked too much.

Do you have any other machines there with similar configurations that you could swap some parts out with (Processor, memory and power supply in particular)?

 

[xhale]

No overclocking. Yes, I have two Gateway 6400s.

 

[Wiz]

Good morning, how can I be of assistance?

With sticky issues like this one I like to simplify, reduce the elements down to the essesntial.
If things essentially work then we can start adding in the accessories.
What I suggest is ditching seti driver (my very favorite seti add on) and see if things go right merely with seti cli.
You can point seti cli to your Q (don't remember the command line - somebody help with that)
You can look in the state.sah file to see the amount done, the percent progress is in there right after "prog=".
So if it says prog=0.30 then you are 30% done.

Before you go there, have you checked for hibernation? Have you installed MBM to find your cpu temp while crunching seti?
It is possible your cpu is overheating and dropping to 50% power (they can do that). Do you have any power saving features turned on in BIOS? In XP there are also power saving features, are they off (except monitor)?

 

[micron]

<< You can point seti cli to your Q (don't remember the command line - somebody help with that) >>

Execute the SETI cli with -proxy 192.168.123.184:5001 (e.g. seti.exe -proxy 192.168.123.184:5001).

 

[Wiz]

yeah, that's it. Just got my coffee. Thanks Micron

I wanna know the cpu temp while crunching.

Also in task manager what is the percent cpu usage for seti cli?