SETI@home - cannot start, cannot stop

keifir

Hi,

i've been running seti for past couple of weeks on my machine. Yesterday I noticed that it was no longer running (i use msetimon to check on it).
I tried to restart the service, but no luck there:

tomk · Posted: Thu Dec 04, 2003 8:12 pm Post subject:

Don't have seti installed here but some init scripts have a zap option which can fix things when this happens. try:

db_404 · Guru Joined: 05 Dec 2002 Posts: 336

If the process dies it can leave a lock file (I think lockfile.sah) in the setiathome directory, try removing/renaming that and re-running. Failing that remove/rename all the .sah files - that will force it back to a clean state (but will lose any data that it had already processed).

keifir · Posted: Thu Dec 04, 2003 10:13 pm Post subject:

Thanks guys!

It's all good now:

Lillstrumpa · Posted: Tue Feb 17, 2004 2:20 pm Post subject:

Get the same error and it works with "zap" but if I try to stop it later it again say:

tomk · Posted: Tue Feb 17, 2004 2:26 pm Post subject:

The zap option will force it's state to stopped, you have to start it again afterwards.
_________________
Search | Read | Answer | Report | Strip

Lillstrumpa · Posted: Tue Feb 17, 2004 2:48 pm Post subject:

Forgot to mention that, it is started before I try to stop it.

orionrobots · Posted: Sat Feb 28, 2004 1:06 am Post subject:

Thanks guys. The zap thing helped me out.
Does that work with any init.d script?

For the Lillstrumpa:
When you start setiathome, is it listed when you run top or "ps -ef | grep setiathome" ?
If not-you may want to modify the scripts so its output is dumped to a logfile instead of /dev/null or run it manually (/opt/setiathome/setiathome) to see if there are any problems.

It may be that it is failing to start properly..
_________________
Danny Staple, curator of http://orionrobots.co.uk
Adopt an unanswered post initiative https://forums.gentoo.org/search.php?search_id=unanswered

ketjow · Posted: Thu Apr 01, 2004 5:28 pm Post subject:

I've got the same problem. seti just don't start! I checked in the init.d/setiathome file and foud out it needs a file called setiwrapper to launch seti. Unfortunatelly it isn't there in /opt/setiathome, so the process doesn't start, and when you want to stop it, you get an error because there is no running seti-process..
what's this setiwrapper thing?

ketjow · Posted: Thu Apr 01, 2004 5:50 pm Post subject:

ok, found an alternative init.d script:
https://bugs.gentoo.org/show_bug.cgi?id=40120
this should work fine, because it doesn't require setiwrapper