Folks,

I am seeing the following error message on my PC running Windows XP and my Intel MAC running OSX.

Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|Task hadcm3transb1_0gz5_50361175_0 exited with zero status but no 'finished' file
Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|If this happens repeatedly you may need to reset the project.

It is solid for 1 app, CPDN beta on my Mac, but I also see it on several apps on my PC. I believe that this has started since BOINC 5.8.11 was released. How can I diagnose this ?

Thnaks,
Jim

Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|Task hadcm3transb1_0gz5_50361175_0 exited with zero status but no 'finished' file
Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|If this happens repeatedly you may need to reset the project.

It is solid for 1 app, CPDN beta on my Mac, but I also see it on several apps on my PC. I believe that this has started since BOINC 5.8.11 was released. How can I diagnose this ?

This is not new and is not happening only on Macs. I've seen some of such messages on both Windows and Linux and with any BOINC CC.

This basically means that project application (in your case CPDN Beta) ended in abnormal way - most probably it just crashed. This is not a problem as it'll get started again and will continue from last checkpoint. I've seen one cae when application (CPDN) kept crashing and I had to abort it.

In short: keep an eye on it to see if it keeps crashing while no new progress is done. In this case you'd have to abort task or even reset the project.

---

Metod ...

Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|Task hadcm3transb1_0gz5_50361175_0 exited with zero status but no 'finished' file
Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|If this happens repeatedly you may need to reset the project.

It is solid for 1 app, CPDN beta on my Mac, but I also see it on several apps on my PC. I believe that this has started since BOINC 5.8.11 was released. How can I diagnose this ?

This is not new and is not happening only on Macs. I've seen some of such messages on both Windows and Linux and with any BOINC CC.

This basically means that project application (in your case CPDN Beta) ended in abnormal way - most probably it just crashed. This is not a problem as it'll get started again and will continue from last checkpoint. I've seen one case when application (CPDN) kept crashing and I had to abort it.

In short: keep an eye on it to see if it keeps crashing while no new progress is done. In this case you'd have to abort task or even reset the project.

I always seem to make progress. However, the frequency of these messages seems to have increased with BOINC 5.8.11. I just saw one for Einstein and another for S@H on my Mac. I have never seen these messages for these two apps on my Mac.

Jim

Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|Task hadcm3transb1_0gz5_50361175_0 exited with zero status but no 'finished' file
Thu Feb 15 10:06:26 2007|Climateprediction.net Beta|If this happens repeatedly you may need to reset the project.

It is solid for 1 app, CPDN beta on my Mac, but I also see it on several apps on my PC. I believe that this has started since BOINC 5.8.11 was released. How can I diagnose this ?

This is not new and is not happening only on Macs. I've seen some of such messages on both Windows and Linux and with any BOINC CC.

This basically means that project application (in your case CPDN Beta) ended in abnormal way - most probably it just crashed. This is not a problem as it'll get started again and will continue from last checkpoint. I've seen one case when application (CPDN) kept crashing and I had to abort it.

In short: keep an eye on it to see if it keeps crashing while no new progress is done. In this case you'd have to abort task or even reset the project.

I always seem to make progress. However, the frequency of these messages seems to have increased with BOINC 5.8.11. I just saw one for Einstein and another for S@H on my Mac. I have never seen these messages for these two apps on my Mac.

Jim

I can now confirm that these messages are occurring every time an app transitions from running to "waiting to run" on my Mac. I don't know if the transition is because of a crash or it is because of a checkpoint being taken or whether BOINC is realloacating resources.

Jim

From the alpha list...

Yes, these are bogus (but harmless) messages.
I checked in a change that gets rid of them.
-- David

---

Kathryn :o)