Error: Exited with zero status but no 'finished' file

Questions and Answers : Windows : Error: Exited with zero status but no 'finished' file
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Charles Crawley

Send message
Joined: 23 May 99
Posts: 10
Credit: 2,631,574
RAC: 0
United Kingdom
Message 133836 - Posted: 7 Jul 2005, 17:54:45 UTC

Hi all,

I have been getting the following error messages on multiple (I think all) computers that I am running Seti@Home / BOINC v4.45 on:

07/07/2005 13:33:25|SETI@home|Result 29ja04ab.18903.22336.422146.111_1 exited with zero status but no 'finished' file
07/07/2005 13:33:25|SETI@home|If this happens repeatedly you may need to reset the project.
07/07/2005 13:33:25||request_reschedule_cpus: process exited
07/07/2005 13:33:25|SETI@home|Restarting result 29ja04ab.18903.22336.422146.111_1 using setiathome version 4.18

There are various PCs, running either XP SP2 or Win2K Adv Serv SP4, all running BOINC as a service with the service account having administrative priviledges on each PC.

Any ideas?

Cheers,

Charles
ID: 133836 · Report as offensive
Profile Thierry Van Driessche
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3083
Credit: 150,096
RAC: 0
Belgium
Message 133858 - Posted: 7 Jul 2005, 18:21:44 UTC
Last modified: 7 Jul 2005, 18:22:41 UTC

A lot of WU's seems to have the message

"No heartbeat from core client".

From Boinc Wiki:

Courtesy of Walt Gribben (with minor edits by Paul):

This message means that the BOINC Client Software stopped communicating with the Science Application.

The BOINC Daemon sends a heartbeat message out so that the Science Application programs know its still alive and kicking. So if the messages stop, its supposed to mean that the BOINC Daemon isn't running anymore (perhaps it crashed?) and the Science Applications are also supposed to exit. Thats after they don't get a heartbeat message for 30 seconds. So, they print the "no heartbeat" error and exit. The Science Applications are using an exit code of zero to indicate there isn't any error, at least not with the Work Unit.

Later, the BOINC Daemon sees that the Science Application exited (zero status) but wasn't finished with the Work Unit (there is no finished file) so it restarts the Work Unit. And from where it left off, or at least from the last Checkpoint.

There might be a problem with BOINC Daemon to the Science Application communications, but its not all that serious. Some time is lost in restarting the Work Unit, but its not like it has to start from the beginning each time. After I saw the Work Units were completing in around the same time whether or not they got "no heartbeat" messages, I stopped looking into it.


Retrieved from "http://boinc-doc.net/boinc-wiki/index.php?title=No_heartbeat_from_core_client_-_exiting"
Read the News at the homepage
Have a look at the Technical News
Look if your question is not answered at the Boinc Wiki

Best greetings, Thierry
ID: 133858 · Report as offensive

Questions and Answers : Windows : Error: Exited with zero status but no 'finished' file


 
©2025 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.