Questions and Answers :
Macintosh :
exited with zero status but no 'finished' file
Why Does This Happen Repeatedly: "exited with zero status but no 'finished' file"???
Message board moderation
Author | Message |
---|---|
LarryB56 Send message Joined: 22 Apr 02 Posts: 73 Credit: 4,402,310 RAC: 0 |
On Many of my Macs, I get the following: 2005-01-30 19:32:33 [SETI@home] Finished upload of 30ja04aa.12489.20320.753390.113_3_0 2005-01-30 19:32:33 [SETI@home] Throughput 104863 bytes/sec 2005-01-30 19:33:04 [SETI@home] Result 30ja04aa.12489.20320.753390.156_1 exited with zero status but no 'finished' file 2005-01-30 19:33:04 [SETI@home] If this happens repeatedly you may need to reset the project. 2005-01-30 19:33:04 [SETI@home] Restarting result 30ja04aa.12489.20320.753390.156_1 using setiathome version 4.02 After several occurrances of such messages, I will "reset" the project. THEN it will happen AGAIN!!! Howcum??? Something I can do to stop this? Larry LarryB56 |
ursmed Send message Joined: 30 Jun 01 Posts: 7 Credit: 59,047,988 RAC: 104 |
same here... im using OSX.2.8 whats your version? any solution/hint? |
LarryB56 Send message Joined: 22 Apr 02 Posts: 73 Credit: 4,402,310 RAC: 0 |
> same here... > im using OSX.2.8 > whats your version? > > any solution/hint? > I'm running OSX.3.7 on all the Macs. How did you get OSX.2.8 to run? I have been unable to do it... That's another thing, though. Thanks; LarryB56 |
Martin P. Send message Joined: 19 May 99 Posts: 294 Credit: 27,230,961 RAC: 2 |
This problem is well know for months. On my dual processor Macs almost every fourth WU ends with this message (always the same processor!). Nobody seems to be interested in this topic though, although it does cost lots of credit. One example here (My machine is the one that claimes 16.46): http://setiweb.ssl.berkeley.edu/workunit.php?wuid=9083091. This WU was at 12,000 seconds when the WU from the other processor finished. I received the message "...exited with zero status but no 'finished' file" and the WU started calculating from 0 seconds again. Percentage and scientific output is not affected by this, just the total time. So, instead of 19,777 seconds my computer calculated with only 7777 seconds and therefore the claimed credit is less than half of what it should be. According to the rules for credits the second lowest claimed credit will be given to all users who returned a valid result. In this case all users will loose appr. 25 credit points due to this error. |
©2024 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.