Why does SETI mysteriously close ?

[Doomer]

I'm running command line SETI on a Win2k box and a WinXP box. On both of them SETI will sometimes mysteriously close for no apparent reason. Pisses me off cause I loose crunch time.

Anybody know why this happens and how to avoid it ? No other problems at all with either of these systems.

 

[gistech1978]

i have no idea.
i crunched for seti for years and never had anything happen like that.
setispy used to crash on xp before the update, but seti driver never did.

 

[Assimilator1]

You got me there!

< v3.03 CLi & Win2k ,no problems

Not running a borderline overclock are you?

 

[Hallis]

*shrugs* virus?

 

[Spacehead]

Are you using any add-ons to control the client or is it running by itself?


Weird problem, never heard of that before

 

[lane42]

On both of them SETI will sometimes mysteriously close for no apparent reason

I get that to, but it usually turns out to be the wife or kids that are the culprits

 

[Robor]

Have you tried installing it as a service and set it to restart the service if it faults? All of my boxes run SETI as a service. Regular users can't kill the service either. ;-)

 

[Hallis]

Originally posted by: Robor
Have you tried installing it as a service and set it to restart the service if it faults? All of my boxes run SETI as a service. Regular users can't kill the service either. ;-)

*nods* most dont know how to kill a service anyway or even know what a task manager is for that matter. And its totally stealth so they dont know its running. Good to do at work *wink wink* although i wouldnt do a thing like that

 

[Doomer]

Thanks.

Don't think it's a virus. Been using Norton AV forever and always keep the virus sigs up to date.

Just running the plain old CL client and Seti Spy. Seti Spy never crashes or closes. Just displays idle when the CL Client closes. It seems to happen mostly when it cannot connect to the SETI server but has also happened in the middle of crunching a WU so I'm really at a loss here. I don't have any other strange problems with these systems. Neither one is overclocked and both are running on the cool side.

System 1: Asus A7N8X Deluxe with an AMD Althon XP 2400+

System 2: Asus A7N266-VM with a XP 1700+

Both systems are Nforce. Maybe it's an Nforce issue ???

 

[Spacehead]

Originally posted by: Doomer

Just running the plain old CL client and Seti Spy. Seti Spy never crashes or closes. Just displays idle when the CL Client closes. It seems to happen mostly when it cannot connect to the SETI server but has also happened in the middle of crunching a WU so I'm really at a loss here.

Well, the client would go idle if it can't connect to the server to get a new WU. Ever thought of using a caching program?

Do you have SETI Spy set to keep the client from going idle? Go to the "Client" page & click on "Configure" & fill in the nessessary(spel?) fields & boxes. Check the SETI Spy site for all kinds of info on setting it up.

SETI Spy
SETI Driver- easy to setup cache program & works well with Spy.

 

[Assimilator1]

Doomer
I use an Nfrc2 mbrd too

 

[JWMiddleton]

Originally posted by: Doomer


Just running the plain old CL client and Seti Spy. Seti Spy never crashes or closes. Just displays idle when the CL Client closes. It seems to happen mostly when it cannot connect to the SETI server but has also happened in the middle of crunching a WU so I'm really at a loss here. I don't have any other strange problems with these systems. Neither one is overclocked and both are running on the cool side.

I suggest you use, or try SetiDriver. For one it will cache multiple WU, so you will not have a problem when S@H is down and you can't get WUs. You can still use SetiSpy to keep track of progress. Just remove the cli stuff from SetiSpy.

I pumped a ton of WUs through SetiDriver and never had the problem you described.

Good luck!

 

[Doomer]

The problem is the client closing, not that it's not conecting to the server. And of course Seti Spy would be idle if the client isn't running.

Once again, the problem is the client closing all on it's own.

It just did it again about 5 mins. ago. I was watching when it did it. I did not have my hands on the mouse or the keyboard and there was nothing else running. It just disappeared. I restarted it and now it's crunching away normally. I dunno what it is. Guess I'll just have to live with it.

 

[Soggysocks]

Have you checked the system log in the event viewer on both of your systems?

It will give you info as to why seti is stopped.

 

[Assimilator1]

Doomer
Don't give up yet ,I'm sure someone will have an answer!

Btw when you saw it close was their any error message in SETI?

 

[JWMiddleton]

I have had other programs, such as games do that, but never SETI. As a test on one of your systems I would download a new copy of the cli and SetiSpy to see if that helps.

Also, SetiSpy has a "Keep Alive" option; are you using that? It is on the Client>Configure screen. Even with that I'd still recommend you use SetiDriver to control the cli AND cache WUs.

 

[przero]

Did it stop crunching or did the icon disappear out of the tray? Next time check in Task Manager and see.

 

[JWMiddleton]

Originally posted by: przero
Did it stop crunching or did the icon disappear out of the tray? Next time check in Task Manager and see.

He indicated that SetiSpy went idle which means that it ain't crunchin'!

 

[przero]

Robor - How do you set it as a service?

 

[Doomer]

There's nothing in event viewer pertaining to seti.

 

[Ken g6]

Seti Driver, mentioned above, ought to restart SETI when it dies, so you might try that.

Which version of the command-line client are you running, 3.03 or 3.08 (or both like I'm doing)?

 

[Doomer]

I'm running 3.08. I'll give seti driver a try. Thanks.

Maybe it's like my DSL service. I had a problem with it disconnecting every time the phone rang. I raised a big enough stink with bellsouth that they replaced my crappy actel modem with a Westel that automatically reconnects when the connection drops and does NAT to boot.

 

[lane42]

Hope you get it sorted out Doomer........

 

[Assimilator1]

v3.08............................ wasn't there something in the main SETI@Home forum about a problem with v3.08?? hmmm.......... let me look...........

 

[Spacehead]

Originally posted by: Assimilator1
v3.08............................ wasn't there something in the main SETI@Home forum about a problem with v3.08?? hmmm.......... let me look...........

Alot of people have had problems with the GUI v3.08 & WinXP. Maybe that's what you were thinking?




Doomer,
You never did say how you had SETI Spy set up. ???