In the last couple of weeks I've noticed that my applications are not accumulating work done. Progress remains at 0.000% permanently and if my computer is restarted the elapsed time disappears to ---. The app then appears to restart. Hmm.

I don't know the answer to that.
The only change recently, about a week ago I think, perhaps less, is a new Status message: No Resubmission.
I don't know if this would affect your running models, but I don't think so.

I've made a post in the News thread about problems with this message, and informed the project people, but it'll be a while yet before they're back at work.

In the meantime, perhaps shut down the manager AND the client, and then re-boot.
It cures some things, but not all.

---

Backups: Here

hmm - assume I'm pretty ignorant - I'm not sure what you meant by shutting down the client and the manager, I'm assuming both are shut down whenever the computer is shut down. I've tried resetting the project but with no effect on the problem.

It was possible, at least a few versions back, to shut down just the manager (the gui), without shutting down the client (the worker part, or daemon). This would cause model crashes, because it's necessary to have the model shut down BEFORE shutting down the computer. Otherwise, the model (more accurately, the program running the modelling process), might not have time to close all of the files involved in the modelling.
This leaves the files in an indeterminate state the next time the program tries to start up. And CRAAASSSSSHHHH ....

The same thing applies to just turning off the computer to stop the model from running.

Sometimes you'll get away with just turning off the computer with everything running, and sometimes you won't.
As Clint Eastwood's character Dirty Harry once said: "What you have to ask yourself is: Are you feeling lucky?"

---

Backups: Here

right - no, I don't just shut it off, I close BOINC down first. I found out that detaching and reattaching don't seem to solve it.

detaching and reattaching don't seem to solve it.

Which would indicate that it's something to do with your hardware/software.

---

Backups: Here

hmm - assume I'm pretty ignorant - I'm not sure what you meant by shutting down the client and the manager, I'm assuming both are shut down whenever the computer is shut down. I've tried resetting the project but with no effect on the problem.

I am not that familiar with Mac’s, but, in Windows to shut down the Client you click on the “Advanced” tab in the boinc manager and then click on the “Shut down Connected Client” entry in the menu. Then shut down the boinc manager. Then reboot. Hope this helps.

---

Thanks for the explanation about shutting down the client etc. Unfortunately this doesn't seem to have fixed the problem.

I think I'm having a similar problem. I first posted about it here:
http://climateprediction.net/board/viewtopic.php?f=6&t=9857

To summarize, I have an Mac OS 10.4.11 Intel-based laptop running Boinc 6.10.58. I noticed that recently CPDN models have been crashing and restarting. Someone responded that it might be a result of my settings. At the time, I was skeptical because I've run CPDN and other projects with the same settings without problem.

Since those posts, I've done more experimenting. The CPDN models seem to restart more frequently when %CPU usage is set below 100%. However, when I set this to 100%, I see the behavior that Scott Probst describes: BOINC thinks the model is running, the elapsed time ticks up and the to completion time ticks down-- but after 2.5 hrs, I have 0.000% progress and a very hot laptop. Upon restart of BOINC, time elapsed is back to 0:00.

A couple of other details that seem unusual:
-- when the model is "running" at 100% CPU according to BOINC, the process monitor shows that in fact the CPDN model process is only getting ~50-60%, with the remainder going to the kernel process for as long as CPDN is "running." This is completely abnormal- running any other BOINC project, the kernal is in --at most-- single digits;

-- "snoozing" BOINC does not suspend the CPDN task, i.e., BOINC says "task suspended", but the kernel and hadamXX processes are still screaming along in the process monitor;

-- Les Bayliss says, "...it's something to do with your hardware/software," so I've tried booting with minimal a system ("safe boot"), but this has no effect. Thus if it's software, it seems to be somewhat isolated to BOINC and/or CPDN instead of some other software (eg anti-virus). Other BOINC projects run quite happily, so it's not a general problem with my machine & BOINC. Do the current CPDN tasks require Mac OS 10.5 or greater, perhaps?

Can someone suggest other settings to adjust? Is anyone else having similar no-progress issues? Any help would be appreciated. Thanks very much!

I have the same result running on Mac OSX 10.4.11 on an Intel iMac Core Duo.

Time is counting down and up but progress stays at zero. On task suspended, the task still shows up as running on Activity Manager. Only solution seems to be to abort and stop running CPDN tasks.

There's a sticky post at the top of this section of the board which may explain these problems, along with a cure.

---

Backups: Here

I tried resetting the project. There was no change. Tasks make no progress and Activity Monitor shows tasks still running while on "suspend" and curiously there is 40% CPU activity on Process ID 0, kernel task. That can't be desirable.