Why does SETI mysteriously close ?

[Doomer]

I didn't know there was more than one way to set up Seti Spy. I just run it from the same folder the CL is in.

 

[Spacehead]

Originally posted by: Doomer
I didn't know there was more than one way to set up Seti Spy. I just run it from the same folder the CL is in.

Yes, go to the Client page & click on the "configure" button. There are setting on there to keep the client from going idle, etc.

 

[Doomer]

Cool. Thanks Spacehead. Guess I should have snooped around a little. Makes me wonder why Seti Spy has the ability to keep the client alive. What would kill it ?

 

[Assimilator1]

Users!

Re v3.08 problem ,its differnet to Doomers problem ,they were getting an error message & it wasn't shutting off

 

[Spacehead]

SETI Spy is a great program.
Something alot of people overlook is if you right click on the icon in the taskbar a menu will come up. Go to "Tooltip Text" & 7 options will come up. These are the options for the little info balloon that comes up when you hold your mouse pointer over the Spy icon.

If you want to save your best gaussian graphs it will do that too. (Setup page>logging)
If it's estimated times are off, you can calibrate them. (setup page>client>calibrate)
etc.

It really pays to look over the Spy website.

 

[Doomer]

Well, some time last night it died again. I had Seti Spy set to keep client alive and restart client when idle but it didn't stop it from dieing and staying dead. Guess I'll just have to live with it.

I started it back up normally this morning. There were no error messages and nothing in the event viewer. This was the Win2k box.

 

[Assimilator1]

Wierd ,can't think of anything else

Anyone else?

 

[Blooz1]

Doomer, I've been watching this thread closely since one of my systems (nForce 8RDA+) was having the exact same issue! I tried everything with no results.....

A day or so ago, while it was "down" I did some regular maintenance, including a defrag. Since then, everything has mysteriously been working fine again! I don't knoow if that has anything to do with it, but it's worth a shot..if nothing else happens, your HD will be happy!

 

[Doomer]

I defragged both of these boxes last weekend using DK 7.0. I should be ok as far as that goes. I try to keep up on the maintenance, AV scan, Spyware scan, defrag, etc.

I also noticed that every so often the client will slow to a crawl. If I close it then open it again the text will scroll like a snail and won't advance in any reasonable time. I reboot and it's back to normal. This doesn't happen very often so it's no big deal but I can't help but wonder if these two issues are somehow related. Maybe I need an exorcist.

I have the following running on both of these boxes. Maybe one of these is causing the problems :

PC-cillin 2002
Proximitron
Asus Probe

 

[Blooz1]

Well, just to let ya know, I also run PC-cillin....on both of my machines. I'm only having the issue on the 8RDA+, though.

 

[Swanny]

Just checking in here. I also have the same problem. The rig is the one here.

I have the client running in a command line window minimized in the task bar. Sometimes it just dissappears. I have noticed on my SETI Q that right before it dies it downloads a bunch of WUs. Usually from 6 to 8 WUs. When I start it back up again it downloads a fresh WU to process and I have to delete all the other ones it grabbed from the Q.

 

[Assimilator1]

Stranger & stranger!

Swanny
Which rig in that list?

 

[Doomer]

Nice to know I'm not alone. Misery loves company.

 

[adlep]

It is solved...
Sometimes, when the CLI client can not connect with the central server, it will just close....
It happens to me all the time.

 

[Swanny]

Originally posted by: Assimilator1
Stranger & stranger!

Swanny
Which rig in that list?

Sorry, I thought I linked directly. It's my server rig.

 

[Swanny]

Originally posted by: adlep
It is solved...
Sometimes, when the CLI client can not connect with the central server, it will just close....
It happens to me all the time.

I don't think that's my problem. My SETI Q in on the machine in question and the address the client is pointing to is the 127.0.0.1 internal loopback IP address. Also, that doesn't explain why it downloads a bunch of WUs before it kills itself.

 

[Assimilator1]

Originally posted by: adlep
It is solved...
Sometimes, when the CLI client can not connect with the central server, it will just close....
It happens to me all the time.

Not saying your wrong ,but where/how did you find that out?.Not heard of that before