2004-11-15 15:01:52 [SETI@home] Result 07mr04ab.6777.6690.192314.205_3 exited with zero status but no 'finished' file
2004-11-15 15:01:52 [SETI@home] If this happens repeatedly you may need to reset the project.
2004-11-15 15:01:52 [SETI@home] Restarting result 07mr04ab.6777.6690.192314.205_3 using setiathome version 4.02

This ALWAYS happens when processor 1 uploads a workunit. Whenever CPU 1 uploads, CPU 0 restarts. Percentage done stays as it was before, but CPU time starts from 0 therefore CPU 0 always claims too little credit (given that claimed credit is a function of time and benchmark results).

---

bump.

Basically, the change that should correct this problem has been made to the development release of BOINC, but not yet in the public release.

Are you willing to download the BOINC source and compile it for your platform?

The development source may not compile, however you could download the public source, make the necessary changes and give that a try.

As mentioned in the other thread, I do not own a mac, but as far as I know, compiling the source is reasonably similar to Linux. Any MAC guru's are welcome to help us out here...:-)

---

On my machine this does not happen every time:

2004-11-28 00:31:34 [SETI@home] Computation for result 09ap04aa.18889.3234.592306.117 finished
2004-11-28 00:31:34 [SETI@home] Starting result 09ap04aa.1991.23353.940902.173_2 using setiathome version 4.30
2004-11-28 00:31:34 [SETI@home] Started upload of 09ap04aa.18889.3234.592306.117_2_0
2004-11-28 00:31:35 [SETI@home] Finished upload of 09ap04aa.18889.3234.592306.117_2_0
2004-11-28 00:31:35 [SETI@home] Throughput 174491 bytes/sec
2004-11-28 00:32:30 [SETI@home] Computation for result 09ap04aa.18889.3234.592306.142 finished
2004-11-28 00:32:30 [SETI@home] Starting result 09ap04aa.1991.23353.940902.170_0 using setiathome version 4.30
2004-11-28 00:32:30 [SETI@home] Started upload of 09ap04aa.18889.3234.592306.142_1_0
2004-11-28 00:32:31 [SETI@home] Finished upload of 09ap04aa.18889.3234.592306.142_1_0
2004-11-28 00:32:31 [SETI@home] Throughput 239289 bytes/sec
2004-11-28 00:35:14 [SETI@home] Computation for result 09ap04aa.1991.23353.940902.173 finished
2004-11-28 00:35:14 [SETI@home] Starting result 09ap04aa.1991.23353.940902.172_0 using setiathome version 4.30
2004-11-28 00:35:14 [SETI@home] Started upload of 09ap04aa.1991.23353.940902.173_2_0
2004-11-28 00:35:15 [SETI@home] Finished upload of 09ap04aa.1991.23353.940902.173_2_0
2004-11-28 00:35:15 [SETI@home] Throughput 268221 bytes/sec
2004-11-28 03:43:54 [SETI@home] Computation for result 09ap04aa.1991.23353.940902.170 finished
2004-11-28 03:43:54 [SETI@home] Starting result 09ap04aa.1991.23353.940902.164_1 using setiathome version 4.30
2004-11-28 03:43:54 [SETI@home] Started upload of 09ap04aa.1991.23353.940902.170_0_0
2004-11-28 03:43:55 [SETI@home] Finished upload of 09ap04aa.1991.23353.940902.170_0_0
2004-11-28 03:43:55 [SETI@home] Throughput 280096 bytes/sec
2004-11-28 03:46:51 [SETI@home] Computation for result 09ap04aa.1991.23353.940902.172 finished
2004-11-28 03:46:51 [SETI@home] Starting result 09ap04aa.1991.23353.940902.145_2 using setiathome version 4.30
2004-11-28 03:46:51 [SETI@home] Started upload of 09ap04aa.1991.23353.940902.172_0_0
2004-11-28 03:46:52 [SETI@home] Finished upload of 09ap04aa.1991.23353.940902.172_0_0
2004-11-28 03:46:52 [SETI@home] Throughput 260364 bytes/sec
2004-11-28 03:50:27 [SETI@home] Computation for result 09ap04aa.1991.23353.940902.145 finished
2004-11-28 03:50:28 [SETI@home] Starting result 09ap04aa.1991.23353.940902.171_0 using setiathome version 4.30
2004-11-28 03:50:28 [SETI@home] Started upload of 09ap04aa.1991.23353.940902.145_2_0
2004-11-28 03:50:29 [SETI@home] Finished upload of 09ap04aa.1991.23353.940902.145_2_0
2004-11-28 03:50:29 [SETI@home] Throughput 264271 bytes/sec

It seems that my energy saver settings "Put hard disk(s) to sleep when possible" was having an impact?

---

<img src="http://boinc.mundayweb.com/seti2/stats.php?userID=1790&amp;trans=off">_<img src="http://seti.mundayweb.com/stats.php?userID=524&amp;trans=off">_<img src="http://www.flagofearth.com/Decal2.jpg" HEIGHT="70">

<BR><B><I>Regards, UA

Hi,

I also have this problem from time to time, mostly when I have just downloaded a bunch of wu's then have a problem and have to shut down Terminal. On restarting Terminal it will not recognise the wu's immediatly and downloads a bunch more. I then get this:-


2004-12-29 09:41:23 [SETI@home] Result 24mr04ab.8365.17713.36058.111_0 exited with zero status but no 'finished' file
2004-12-29 09:41:23 [SETI@home] If this happens repeatedly you may need to reset the project.
2004-12-29 09:41:23 [SETI@home] Restarting result 24mr04ab.8365.17713.36058.111_0 using setiathome version 4.30


The work unit is restarted and finishes normaly. So I just let it run until the old wu's are proccessed. You can double check that SAH is proccessing by takeing a look at the Activity Monitor (Panther).

K.

---

http://spacetimes.info

> Basically, the change that should correct this problem has been made to the
> development release of BOINC, but not yet in the public release.
>
> Are you willing to download the BOINC source and compile it for your
> platform?
>
> The development source may not compile, however you could download the public
> source, make the necessary changes and give that a try.
>
> As mentioned in the other thread, I do not own a mac, but as far as I know,
> compiling the source is reasonably similar to Linux. Any MAC guru's are
> welcome to help us out here...:-)


No change in verssion 4.19!

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.

---

>This ALWAYS happens when processor 1 uploads a workunit. Whenever CPU 1
>uploads, CPU 0 restarts. Percentage done stays as it was before, but CPU
>time starts from 0 therefore CPU 0 always claims too little credit (given
>that claimed credit is a function of time and benchmark results).

Martin, how do you know which CPU works on a WU?

If you mean that when the WU in slots/1 completes the WU in slots/0 restarts, those aren't for the CPU but to match the shared memory segments with the application running a WU. Shared memory gets used for sending messaegs between BOINC and the science applications.

If this is the case, that means theres a bug in the WU startup code or maybe the cleanup code for the previous WU. Basically, its not starting the new WU properly so "sleeps" for 35 seconds, which causes the other WU to exit early. See this message for details.