"Exited with zero status but no 'finished' file"
24 May 2011 0:53:20 UTC
Topic 195802
(moderation:
I've been having a problem with the error message "...Exited with zero status but no 'finished' file. If this happens repeatedly you may need to reset the project" on almost all tasks.
I'm runing Boinc 6.12.26 (x86) on a Intel Core i7 CPU M 620 @ 2.67GHz (laptop), I have reset the project several times and have updated BOINC to the latest version but the problem persists.
Can anyone help?
"Exited with zero status but no 'finished' file"
)
I am getting the same message after each 60 minutes session of a different BOINC project which uses a VirtualMachine, a project originating from CERN, but everything seems to function normally, so I would not worry much.
Tullio
On your list of hosts page I
)
On your list of hosts page I see two machines with an Intel Core i7 CPU M 620 @ 2.67GHz. Which one is giving you the "no finished file" message? Is it 4127568 or 3705844?
If it's 3705844 then you definitely need to worry about it because most of your BRP tasks on that host are ending with Error While Computing. In the Stderr Output for those tasks I see a lot of...
Have you tried rebooting Windows?
[edit]I see you're using driver 26099 on both of those computers. Is that the latest driver available for that GPU? Not sure but it seems a little old.[/edit]
BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux
Thanks for getting back to
)
Thanks for getting back to me.
I'm currently having the problem on 4127568.
However 4127568 and 3705844 are the same computer, but I installed the new version of BOINC and 4127568 is the operational account.
4127568 is my work computer and as far as I know I'm using the latest driver for this computer. I'll check later on when I get a chance.
I have tried restarting Windows as well, but no luck.
OK, you detached 3705844 and
)
OK, you detached 3705844 and when it was reattached it became 4127568. The CUDA driver did not change, only the BOINC version. It's interesting that 3705844 returned 90% of BRP tasks with compute errors and only 1 out of a dozen or so BRP tasks errored on 4127568. What kind of work do you do on that computer? Do you do any GPU intensive video/graphics work or heavy duty gaming?
Back to the original topic of this thread... the "no finished file" message. I recall that a couple years ago lots of people were getting the "no finished file" message but their tasks were returning error free which suggests there was a bug in BOINC. I don't remember how that situation was resolved but it seems to me the problem went away. Probably someone found the bug and fixed it, I just don't remember. Maybe that same bug (or whatever it was) has crept back in.
You may get other opinions on this but my advice is if you're not getting compute errors in your returned tasks (and you don't seem to be now) then don't worry about the "no finished file" message.
Finally, keep an on your completed tasks list to see if you start returning compute errors with the BRP tasks.
BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux
How often do you get that
)
How often do you get that message?
Is the host connected to a time server?
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Usually this message is
)
Usually this message is preceded by "No heartbeat from core client" in stderr_out of that tasks. There are a couple of reasons for this: the Core Client being busy with other things than communicating with the App (e.g. waiting for a slow DNS), or the time ticking differently between App and Client, as it happens occasionally when the time on your machine is adjusted e.g. to synchronize with an external timeserver.
Revisiting and rewriting or possible replacing the 'heartbeat' mechanism is a long standing item on the todo list of BOINC developers, but AFAIK hasn't been done yet. Making the Core Client talk to the App in a separate thread might also help, but AFAIK this also hasn't been addressed yet.
As long as BOINC sticks to the current implementation, the only thing you can do is to find out what prevents the Client from answering and stop that, e.g. network issues.
BM
BM
RE: e.g. network
)
Or an Anti-Virus or anti-malware program allowed to do background scans. Always exclude the BOINC Data directory and all its files and sub-directories from being active scanned by AV & AM. If you must do a scan, do one manually with BOINC suspended or exited.
@ Dagorath I'm an accountant,
)
@ Dagorath I'm an accountant, so no graphics intensive work or games - its a low end laptop.
@ Gundolf John, I get the message many times a day, about 5 tasks the machine is working on. I don't know about the time server question, its a work computer on the work network.
@ Bernd Machenschalk, I've never seen the message "No heartbeat from core client". As pointed out by Dagorath it doesn't seem to be stopping me from completing tasks normally so perhaps there is no actual problem, though it is annoying.
@ Ageless, its a work computer so I don't have that level of access to the setup unfortunately.
Thanks everybody for your help.
RE: @ Bernd Machenschalk,
)
I took a sample for this host on 2011-05-23 ;-)
http://einsteinathome.org/task/230778156
2011-05-23 14:59:09.7406 (6104) [normal]: 1/15
14:59:45 (6104): No heartbeat from core client for 30 sec - exiting
16:28:14 (5308): No heartbeat from core client for 30 sec - exiting
18:09:04 (5796): No heartbeat from core client for 30 sec - exiting
18:24:25 (4008): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230766557
2011-05-23 14:34:13.4885 (5104) [normal]: 4/48
14:35:17 (5104): No heartbeat from core client for 30 sec - exiting
17:38:19 (4016): No heartbeat from core client for 30 sec - exiting
18:09:04 (5900): No heartbeat from core client for 30 sec - exiting
18:24:24 (1540): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230766545
2011-05-23 14:58:38.7632 (3396) [normal]: 12/39
14:59:45 (3396): No heartbeat from core client for 30 sec - exiting
16:28:14 (3076): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230757946
2011-05-23 14:33:49.1204 (5600) [normal]: 12/28
14:35:17 (5600): No heartbeat from core client for 30 sec - exiting
14:59:46 (6024): No heartbeat from core client for 30 sec - exiting
16:28:14 (5448): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230752930
2011-05-23 18:06:35.1361 (5856) [normal]: 1/39
18:09:05 (5856): No heartbeat from core client for 30 sec - exiting
18:24:25 (3752): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230752928
2011-05-23 17:38:04.6492 (4636) [normal]: 1/32
17:38:19 (4636): No heartbeat from core client for 30 sec - exiting
18:09:05 (5012): No heartbeat from core client for 30 sec - exiting
18:24:25 (3516): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230713281
14:35:17 (1784): No heartbeat from core client for 30 sec - exiting
14:59:46 (3844): No heartbeat from core client for 30 sec - exiting
http://einsteinathome.org/task/230713277
16:28:14 (1224): No heartbeat from core client for 30 sec - exiting
17:38:19 (1076): No heartbeat from core client for 30 sec - exiting
That doesn't look like a timeserver issue (except for the 14:59 one) but could well be an AV or indexing service.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: @ Bernd Machenschalk,
)
Indeed, as mentioned by Bernd, that message only appears in the stderr output. In the Messages tab (Event log), you get another message, depending on your BOINC version. With 5.10.45, it's[pre]24/05/2011 20:51:59|Einstein@Home|Task h1_0095.55_S6GC1__49_S6BucketA_1 exited with a DLL initialization error.
24/05/2011 20:51:59|Einstein@Home|If this happens repeatedly you may need to reboot your computer.[/pre]
Gruß,
Gundolf
[edit]BTW, that restart was caused by a timeserver adjusting the system clock :-)[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)
