Message boards : BOINC client : exited with no finished file
Message board moderation
Author | Message |
---|---|
Send message Joined: 5 Mar 06 Posts: 16 ![]() |
Yes, you've seen this before, this is a little bit different, these all happened at once. I believe they did finish successfully. Still, it's strange. Previous to this by a couple of hours I had both IE and Firefox crash, it may be related to a general Windows screw-up. 2006-09-22 05:20:04 [rosetta@home] Task 1qgtA_BOINC_ABINITIO_SAVE_ALL_OUT__1240_12509_0 exited with zero status but no 'finished' file 2006-09-22 05:20:04 [rosetta@home] If this happens repeatedly you may need to reset the project. 2006-09-22 05:20:04 [---] Rescheduling CPU: application exited 2006-09-22 05:20:04 [Einstein@Home] Task h1_1056.0_S5R1__787_S5R1a_0 exited with zero status but no 'finished' file 2006-09-22 05:20:04 [Einstein@Home] If this happens repeatedly you may need to reset the project. 2006-09-22 05:20:04 [---] Rescheduling CPU: application exited 2006-09-22 05:20:04 [SETI@home] Task 11oc99aa.20018.23072.553406.3.177_3 exited with zero status but no 'finished' file 2006-09-22 05:20:04 [SETI@home] If this happens repeatedly you may need to reset the project. 2006-09-22 05:20:04 [---] Rescheduling CPU: application exited 2006-09-22 05:20:04 [rosetta@home] Restarting task 1qgtA_BOINC_ABINITIO_SAVE_ALL_OUT__1240_12509_0 using rosetta version 525 |
![]() Send message Joined: 29 Aug 05 Posts: 15585 ![]() |
Well, first off... this is a benign error. Unless it happens a lot of times for all results you get to crunch. Still, it's not something to report to BOINC. It's an error done by, in your case, the Rosetta science application. So you need to report it on the Rosetta Q&A or Number Crunching forums. You can read about it here in the Boinc Wiki. |
Send message Joined: 16 Apr 06 Posts: 386 ![]() |
If the PC system clock gets set back a 'zero status' message will be triggered, regardless of which science app is running. This may happen once every 3 hours or so when Windows does it's time sync. That's merely one of many different causes. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.