how stable is SetiSpy v3.0.3?

[TuffGuy]

the old version used to lockup my computer every few days. does anybody know if the bug has been fixed?

 

[Viztech]

I've been using it for several days without trouble locking up.

viz

 

[JWMiddleton]

Hey TuffGuy! I am currious how you know SetiSpy was at fault. Are you using it to control the cli or just for info? I've got it on 12 boxes running 24/7 and some have run for many weeks without interruption. I have a combo of versions 3.0.1 and 3.0.2. I also put 3.0.3 on one machine last week. In all cases I run SetiSpy with SetiDriver. On three machines I include SetiQ with that mix.

 

[TuffGuy]

JWMiddleton - because when i turned off SetiSpy my boxes stopped locking up. when i had SetiSpy running, my boxes would lock up every 3 days or sooner. i turned it off about 2 weeks ago and they haven't locked up since.

[edit]

i'm using it to log the times/angles/spikes/gaussians/triplets/pulses of each workunit.

[/edit]

 

[JWMiddleton]

TuffGuy: I assumed that would be your response. But, you didn't state what programs were running with SetiSpy. How do you control the cli? SetiQ, SetiDriver, both or others?? Just looking for something different from my config. Is this only on one machine? What OS do you run? I have it on systems that run 98, 98SE and ME.

 

[TuffGuy]

setup:

WinMe, setiq, seti@home gui, (+/-)setispy - all on 24/7

computer 1) p3-700@1050, asus cusl2
computer 2) tbird-700@1236, abit kt7

 

[blade47]

I'm running winMe, midpoint proxy server, vnc, setiQ, SetiDriver, s@h cli & SetiSpy all on the same machine with no problems. It's been down once in the last month & that was due to a power outage. Maybe SetiSpy is having trouble with the gui client.

 

[ElFenix]

i'm running win2k, s@h, and setispy on the pro and the only time its been off in 6 months was a power outage.

 

[JWMiddleton]

blade_47 beat me to it. The only thing different in your s/w configuration is the GUI. As an experiment you might try the cli for a few days to see if the SetiSpy problem goes away. I would also suggest upgrading to the latest version of SetiSpy.

Good luck with it!

 

[Assimilator1]

I have problems with SETI spy too.
WHat happens for me is that if I have SETIspy on (v3.0.3) spying on my main PC (Win 95c ,CLIv3.0) ,if I leave it running longer than a few mins it refuses to shutdown hitting the X & it also then takes up nearly all the cpu time! (about 95%) ,I have to kill it using Taskinfo 2000.
I've NEVER had the problem spying on SETI clients on the network even though I'm still running SETIspy on my main PC!
Any ideas?

 

[Fardringle]

Try disabling the 'keep client alive' function. It may be trying to restart the client every few minutes, even when the client doesn't want to be restarted, and the conflict is stealing all of the CPU cycles..?

I've never heard of this happening, and don't have the problem on any of my systems, but it's the only thing that comes to mind, and would be quite easy to try...

 

[networkman]

I've been using SetiSpy with a number of different of OS's and machines, but all with the CLI.. I've not had any lockups of any kind.

 

[Assimilator1]

FD

I guess you were talking to me? ,I checked that it's already disabled.
Any other ideas?

 

[roelof]

Assimilator1,

Try clearing all the checkmarks on the Setup Update screen. It sounds like SETI Spy is looking for a internet connection and cannot find one.

 

[Assimilator1]

Wow! ,an answer from the man himself! ,I feel honoured

I'll let you know(here) if it fixes it ,so far so good