Due to a mistake from my side (never play with permissions on a running computer, especially not recursively), I locked the boinc client and science apps out of their own directories, in other words rw-access to state and log-files was denied. This happened while crunching a S@H WU. Boinc tried to restart this WU twice by re-downloading it (but failed as no write access) and then gave up. In parallel BOINC was trying to start CPDN. This obviously did not happen either, and by the looks of my WU got aborted. BOINC here tried to download a new one once (which also did not work).
Unfortunately I then compounded the problem by correcting the permissions problem (leave it to humans to really screw up), and only then stopping/restarting boinc. The nett effect of this is that I now got a new CPDN WU, have all the data of the other WU (PH 3, i trickle). The program I use to interpret the boinc state files lists the oldest CPDN WU as \'completed/uploaded\' and boinc does not switch to it, but rather starts the new WU.

Is the oldest WU truely borked, i.e. boinc will not start crunching it? I scanned the client_state.xml files (unsuccesfully) for a clue.
Is it possible to restart CPDN on the oldest WU by going back to a check-point? How?

---

It\'s possible to restart a Wu if you\'ve got a backup of the whole BOINC folder made before your problem occured.
If you don\'t have a backup, it\'s \"game over\" for your old Wu, because of the missing infos contained in the client_state.xml file.(now, your client_state.xml have just infos about your new wu, as you have perhaps seen)

---

Arnaud

It\'s possible to restart a Wu if you\'ve got a backup of the whole BOINC folder made before your problem occured.
If you don\'t have a backup, it\'s \"game over\" for your old Wu, because of the missing infos contained in the client_state.xml file.(now, your client_state.xml have just infos about your new wu, as you have perhaps seen)

Thanks, no backup, so no restart. I have \"inserted a new coin\" and hope that I will complete a WU with the next one. Probably should set up a cron job to make such a backup...

Thanks for the response anyhow.

---