I repeatedly get "Task exited with zero status but no 'finished' file." The next line says "If this happens you may need to reset the project." Followed by Resched. CPU: appl. exited. Restarting ___ using SETI....

I have reset the project and nothing has changed.

After going away for a month and receiving "the email" when I got back, I'd started this machine up again. Since I'd had some errors before I left, I deleted BOINC and downloaded the software again. I attached to SETI@HOME on 10/19/06 and have not succeeded in returning any results since then.

I am running BOINC Manager 5.4.9 on a 400 MHz Power PC G3 under OS 10.3.9.

Any help would be much appreciated. I'm pretty frustrated. Kit

I attached to SETI@HOME on 10/19/06 and have not succeeded in returning any results since then.

I am running BOINC Manager 5.4.9 on a 400 MHz Power PC G3 under OS 10.3.9.

Any help would be much appreciated. I'm pretty frustrated. Kit

The processing of the SETI Enhanced took longer than the classic WUs.
Could you please look into the BOINC manager, in the tasks sections, there will be your downloaed WUs listed. Also, here you should see one WU in the state "running and the progress in percent, the CPU runtime and the estimated runtime.

---

The processing of the SETI Enhanced took longer than the classic WUs.
Could you please look into the BOINC manager, in the tasks sections, there will be your downloaed WUs listed. Also, here you should see one WU in the state "running and the progress in percent, the CPU runtime and the estimated runtime.

Thanks very much for your response. There's only one line currently under Tasks:
SETI@home / setiathome_enhanced 5.13 / 14my03aa.14896.9682.329810.3.159_2 / 00:27... / 4.3...% / 11:24... / Fri Oct 27 06:01:06 2006 / Running

Since I wrote yesterday, the job that was being run, 12my03ab.6570.9121.23586.3.70_3_0 exited with zero status, ..., 10 seconds of new work was requested, ..., scheduler requested to report completed task, reported 1 task, 14my03aa... exited with zero status..., and 14my03aa.14896.9682.329810.3.159_2 was restarted. The last message is Scheduler request succeeded.

I have these Energy Saver settings:
Put the computer to sleep when it is inactive for 15 min, put display to sleep when the computer is inactive for 15 minutes. Display sleeps before screen saver activates. BOINC preferences are Run based on preferences and Network activity based on preferences.

I'm willing to type in all the messages if that will help your troubleshooting. I certainly appreciate your help. Kit

I have these Energy Saver settings:
Put the computer to sleep when it is inactive for 15 min

I guess that’s your problem right there. Let the monitor power down, but not the CPU. A sleeping computer can’t crunch—and BOINC doesn’t stop properly when interrupted by a sleep state. If you really want to put your computer to sleep, quit BOINC first.

---

I have these Energy Saver settings:
Put the computer to sleep when it is inactive for 15 min

I guess that’s your problem right there. Let the monitor power down, but not the CPU. A sleeping computer can’t crunch—and BOINC doesn’t stop properly when interrupted by a sleep state. If you really want to put your computer to sleep, quit BOINC first.

But isn't the computer kept active doing SETI calculations?

Thanks very much to both of you for your help. I'll change the prefs right away. Kit

---

But isn't the computer kept active doing SETI calculations?

I have only a vague idea of how Energy Saver works, but it’s my impression that “internal” events don’t keep the system awake. Using the mouse or keyboard does, or accessing the system over a network. BOINC runs at a very low priority, and I surmise that the OS considers its activities to be mere ‘housekeeping chores’ that it’s free to interrupt, getting around to them later.

---

I get the same error, and my computer runs 24/7 and does not sleep.

Here are the log entries

Sat Dec 16 01:56:14 2006|SETI@home|Computation for task 16mr99ab.29284.26577.292318.3.58_0 finished
Sat Dec 16 01:56:14 2006|SETI@home|Restarting task 16mr99ab.29284.26818.704834.3.148_1 using setiathome_enhanced version 513
Sat Dec 16 01:56:16 2006|SETI@home|Started upload of file 16mr99ab.29284.26577.292318.3.58_0_0
Sat Dec 16 01:56:21 2006|SETI@home|Finished upload of file 16mr99ab.29284.26577.292318.3.58_0_0
Sat Dec 16 01:56:21 2006|SETI@home|Throughput 6278 bytes/sec

Sat Dec 16 02:02:06 2006||Can't rename state file: Error -1
Sat Dec 16 02:02:06 2006||Couldn't write state file: system rename

Sat Dec 16 02:03:06 2006|SETI@home|Task 16mr99ab.29284.26818.704834.3.148_1 exited with zero status but no 'finished' file
Sat Dec 16 02:03:06 2006|SETI@home|If this happens repeatedly you may need to reset the project.
Sat Dec 16 02:03:06 2006||Rescheduling CPU: application exited
Sat Dec 16 02:03:06 2006|SETI@home|Restarting task 16mr99ab.29284.26818.704834.3.148_1 using setiathome_enhanced version 513
Sat Dec 16 02:03:07 2006|SETI@home|Task 17mr99aa.8520.6690.217308.3.44_3 exited with zero status but no 'finished' file
Sat Dec 16 02:03:07 2006|SETI@home|If this happens repeatedly you may need to reset the project.
Sat Dec 16 02:03:07 2006||Rescheduling CPU: application exited
Sat Dec 16 02:03:07 2006|SETI@home|Restarting task 17mr99aa.8520.6690.217308.3.44_3 using setiathome_enhanced version 513
Sat Dec 16 02:03:08 2006|SETI@home|Task 17mr99aa.8520.6690.217308.3.48_0 exited with zero status but no 'finished' file
Sat Dec 16 02:03:08 2006|SETI@home|If this happens repeatedly you may need to reset the project.
Sat Dec 16 02:03:08 2006||Rescheduling CPU: application exited
Sat Dec 16 02:03:08 2006|SETI@home|Restarting task 17mr99aa.8520.6690.217308.3.48_0 using setiathome_enhanced version 513
Sat Dec 16 02:03:09 2006|SETI@home|Task 17mr99aa.8520.6690.217308.3.143_2 exited with zero status but no 'finished' file
Sat Dec 16 02:03:09 2006|SETI@home|If this happens repeatedly you may need to reset the project.
Sat Dec 16 02:03:09 2006||Rescheduling CPU: application exited
Sat Dec 16 02:03:09 2006|SETI@home|Restarting task 17mr99aa.8520.6690.217308.3.143_2 using setiathome_enhanced version 513
Sat Dec 16 02:31:27 2006|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Sat Dec 16 02:31:27 2006|SETI@home|Reason: To fetch work
Sat Dec 16 02:31:27 2006|SETI@home|Requesting 30 seconds of new work, and reporting 1 completed tasks
Sat Dec 16 02:31:32 2006|SETI@home|Scheduler request succeeded

I think some of it may be due to the error -1 (separated in log to see better), but I get a lot of the zero status no finished file.

Any suggestion?

---

no suggestion, but the absolutely same problem with my 24/7 system.

What can we do ?

---

no suggestion, but the absolutely same problem with my 24/7 system.

What can we do ?

No idea. Ive reset the project, removed and reinstalled boinc. excluded all directories with the seti data from my virus scanner, set permissions on the files and directories for boinc etc to everyone read write and stilll no change. The boinc wikipedia lists the error but gives no solution.


:(

---

Victor and Olivose have you verified the power management like Odysseus has described ?
Have you any IO and/or CPU intensive tasks running, when SETI is running ?

---

Victor and Olivose have you verified the power management like Odysseus has described ?
Have you any IO and/or CPU intensive tasks running, when SETI is running ?

Power management is disabled on my system except "put the disks to sleep when possible".

I only have an occasional heavy use application that runs at about 15:10 for 1 hour (TV recording over firewire). The error comes at all times of day and night.

---

I am getting the same errors.

Sun Feb 18 18:44:21 2007||Restarting 24no03aa.2465.6162.742326.3.119_1 - message timeout
Sun Feb 18 18:44:22 2007|SETI@home|Task 24no03aa.2465.6162.742326.3.119_1 exited with zero status but no 'finished' file
Sun Feb 18 18:44:22 2007|SETI@home|If this happens repeatedly you may need to reset the project.

I have reset the project, but still get the same message. My energy saver is set for the monitor to sleep, but not the hard drive.

This has started since I upgraded to BoincManager 5.8.8

---

Hello from Earth

This has started since I upgraded to BoincManager 5.8.8

So far I know could this happen with the BOINC cient 5.8.8, but it is not a serious problem and will fixed in the next stable relase.

---

This has started since I upgraded to BoincManager 5.8.8

So far I know could this happen with the BOINC cient 5.8.8, but it is not a serious problem and will fixed in the next stable relase.

No offense, but how long will that take :/ ??? I've been waiting for a half a year (or more) for a fix. My personal feeling is that a quick fix for the Macintosh should be a priority considering it is (and I believe it's only) a Macintosh issue. Sorry ^_~ ...

---

I upgraded to 5.8.11 last night and I am still getting those messages, just not as often.
But now I am getting:
Tue Feb 20 06:27:53 2007||[error] Process 208 not found

Each time it is a different process number.

It would be nice to get a stable version of Boinc for the Mac. :)

---

Hello from Earth

I upgraded to 5.8.11 last night and I am still getting those messages, just not as often.
But now I am getting:
Tue Feb 20 06:27:53 2007||[error] Process 208 not found

Each time it is a different process number.

It would be nice to get a stable version of Boinc for the Mac. :)

It is the same like on the other message. It is NO problem or bug and you should ignored it !

---

I had this problem using BOINC 5.8.8 with MacOSX 10.4.8 on a dual G4 PowerMac.
The first WU's I got at the start of using this BOINC version (just a few weeks
ago), I got small WU's and the job was done with about 4 hours per WU. But after
changing some settings I got larger WU's where the above problem occurred. Since
then this happened to almost every WU that was downloaded. After resetting the
project and aborting de WU's that were more than once restarted (very frustrating
when checking the progress that was almost 80% first and than just 1% an hour
later), I gave up on BOINC 5.8.8 and tried an earlier version as was suggested
somewhere.
So now I'm using BOINC 5.4.9 on the same computer (although BOINC registers it
as a new computer due to a shorter description of my CPU) and this version seems
to be working much better on OSX 10.4.8. Even the (manual) sleep mode doesn't
effect the crunching of BOINC now.

What was changed in 5.8.8 to become so instable ? Or was this version only made
with the intel machines in mind ?

---

Grt. Merlin

What was changed in 5.8.8 to become so instable ? Or was this version only made
with the intel machines in mind ?

They were tinkering with a lot of things; I get the impression thete was a flurry of ‘last-minute’ changes. There have been at least a couple more minor version updates since 5.8.8 came out as well, as they chase down some of the bugs. I’m not involved with the development efforts, but it seems there was some hurry to get this version released, even though it wasn’t quite ‘ready for prime time’. My policy of waiting a few weeks before upgrading seems to have been vindicated this time around …

---

Merlin, I have seen a posting, that there will be a fix for the problem in the next stable version. In the moment the next release is in alpha stage.

---

I'm getting the same issue on my Intel MacBook. I was reminded that I hadn't download Boinc to start up Seti@Home by a friend (I switched computers over the summer), so I installed the newest version of Boinc last night, and I'm getting error messages too:

Fri Feb 23 00:20:14 2007||Restarting 15au03aa.20522.14689.123566.3.105_2 - message timeout
Fri Feb 23 00:20:15 2007|SETI@home|Task 15au03aa.20522.14689.123566.3.105_2 exited with zero status but no 'finished' file
Fri Feb 23 00:20:15 2007|SETI@home|If this happens repeatedly you may need to reset the project.

I don't know how to reset the project, but, from what I'm seeing, that won't really help either. My hard disc does NOT sleep unless I turn off my computer, though my monitor does (it's a foot from my bed, so I turn off the screen every night).

Is there anything outside of waiting for Boinc to catch up with OSX?

---