I don\'t understand this WU.
It says \"errors: Too many error results Too many total results\"
On the list I seem to be the only one out of 8 that is actually doing some work on it. Everybody else had either \"client error\", 1 \"client detached\" and 2 \"didn\'t need\"?
What does that mean: \"Too many error results\"?
What does: \"Too many total results\" mean?

I suppose my work in progress will still be useful, as it\'s still chugging silently along...

---

Robi

That part of the software is used by other projects, but here the info is fairly meaningless. Just ignore it. The only thing of use on that page is the list of other models running, if YOU start to have a problem with yours and you want to see how others are doing.

This matter has been mentioned a lot of times, and you may be able to find these posts by using the search option at the top of this page if you want more information.

That part of the software is used by other projects, but here the info is fairly meaningless. Just ignore it. The only thing of use on that page is the list of other models running, if YOU start to have a problem with yours and you want to see how others are doing.

This matter has been mentioned a lot of times, and you may be able to find these posts by using the search option at the top of this page if you want more information.

Hi Les, thank you for the explanation.

BTW I did try the search before I posted :) I also looked through the FAQs, but couldn\'t find anything that would explain it, at least I didn\'t see anything on the \"too many\" search that I entered (right now only my post shows up if I search for \"too many\") ;)

...and as I mentioned, I seem to have the ONLY model running %-/
But again, thanks for the explanation. Now I know that all I need to do is just keep it up & running :)

---

Robi

Before Christmas we were discussing with Milo, one of the CPDN programmers, whether it\'s possible to get rid of at least some of these phrases that mislead lots of our members. Now that the holidays are over we\'ll need to restart this discussion. The problem is that this stuff is built into the BOINC-provided web pages because most projects need it all.

To maximise your chances of completing the model, have a look at the CPDN README collections. There\'s a link in my signature. It\'s very useful to select a backup method from the collection so that if your model does crash you can restore and continue it.

---

Cpdn news

Before Christmas we were discussing with Milo, one of the CPDN programmers, whether it\'s possible to get rid of at least some of these phrases that mislead lots of our members. Now that the holidays are over we\'ll need to restart this discussion. The problem is that this stuff is built into the BOINC-provided web pages because most projects need it all.

To maximise your chances of completing the model, have a look at the CPDN README collections. There\'s a link in my signature. It\'s very useful to select a backup method from the collection so that if your model does crash you can restore and continue it.

Hi mo.v,
if and when you restart those discussions, it would be grand to implement a CPDN own backup strategy and not rely on users who might or rather not do backups of

• their systems
  
• BOINC
  
• CPDN
  

or the ones that do a backup don\'t stop CPDN... and then have a crash of the model...

---

Robi

There are now some other projects with fairly long tasks that would also benefit. However, as far as I know nobody has yet thought of a way to make BOINC completely exit from itself (ie stop running completely) but still remain active to back itself up. It would have to be done by BOINC itself.

---

Cpdn news

There are now some other projects with fairly long tasks that would also benefit. However, as far as I know nobody has yet thought of a way to make BOINC completely exit from itself (ie stop running completely) but still remain active to back itself up. It would have to be done by BOINC itself.

what I meant to say is, that CPDN should back up its own task(s) and upon error (if it\'s not computation but crash) restore to its last \"checkpoint\"?
Id est, let each project backup its own tasks.

yes, it would be nice if BOINC could implement an automatic backup strategy (especially for the service installation), but with my meager 3 projects, CPDN seems to be the only one with crashing problems (note: so far I haven\'t had a crash on CPDN with this system [knock on wood] although 4 systems have this far quit on me :(... )

---

Robi

There are now some other projects with fairly long tasks that would also benefit. However, as far as I know nobody has yet thought of a way to make BOINC completely exit from itself (ie stop running completely) but still remain active to back itself up. It would have to be done by BOINC itself.

I think there are some ways for XP and Vista running as BOINC service:

[code]net stop BOINC
backup
net start BOINC[/code]

or

[code]sc stop BOINC
backup
sc start BOINC[/code]

should do the trick...

---

Robi

what I meant to say is, that CPDN should back up its own task(s) and upon error (if it\'s not computation but crash) restore to its last \"checkpoint\"

The CPDN science application does this already: it will rewind to the start of the day in which the crash occurs and try again - that\'s rather closer than a checkpoint. The checkpoint mechanism will also have saved many quick crashes, when the computer reboots and the science application just restarts from the last checkpoint. Lots of models that complete sucessfully will actually have been automatically recovered, possibly many times, without the user noticing.

The use of manual backups simply means that BOINC/CPDN is pessimistic relative to experienced users - i.e. more models can be restarted than BOINC/CPDN supposes. It may be that more completions could be achieved by making the joint BOINC/CPDN error handling more subtle and optimistic than by inventing an inevitably problematic backup mechanism.