Has anyone else seen these recursive messages ? Is so, what had to be done ? Thanks


9/25/2005 6:42:03 AM|rosetta@home|Result 1btn__abrelax_02357_0 exited with zero status but no 'finished' file
9/25/2005 6:42:03 AM|rosetta@home|If this happens repeatedly you may need to reset the project.
9/25/2005 6:42:03 AM||request_reschedule_cpus: process exited
9/25/2005 6:42:03 AM|rosetta@home|Restarting result 1btn__abrelax_02357_0 using rosetta version 4.77

---

I reset the project at the "Projects" tab in the Manager and it downloaded a bunch of files. Looks like it's running ok now. Wonder what happened to cause this? Do files get corrupted? There should be a feature installed that counts the warning messages and downloads automatically when a threshold is reached.

Has anyone else seen these recursive messages ? Is so, what had to be done ? Thanks


9/25/2005 6:42:03 AM|rosetta@home|Result 1btn__abrelax_02357_0 exited with zero status but no 'finished' file
9/25/2005 6:42:03 AM|rosetta@home|If this happens repeatedly you may need to reset the project.
9/25/2005 6:42:03 AM||request_reschedule_cpus: process exited
9/25/2005 6:42:03 AM|rosetta@home|Restarting result 1btn__abrelax_02357_0 using rosetta version 4.77

---

I reset the project at the "Projects" tab in the Manager and it downloaded a bunch of files. Looks like it's running ok now. Wonder what happened to cause this? Do files get corrupted? There should be a feature installed that counts the warning messages and downloads automatically when a threshold is reached.

A reset should be the last resort. The first thing to try is to quit and restart BOINC. Second, a computer restart may help, if there is something running in the background that is interfering or hogging memory. Third is to abort only the problem work unit. (might be bad).

If all of those fail, then reset the project. Many times though, the above three steps will resolve the issue quickly and avoid lost work.

---

Team MacNN - The best Macintosh team ever.

Yikes, it's happening again ! It does it with different work units too. I did all the things suggested and it reoccurs. Wondering if I'll have to uninstall/reinstall the silly thing ? What do the Berkeley guys say about this sort of thing?

---

Yikes, it's happening again ! I did all three things suggested and it reoccurs ! Wondering if I'll have to uninstall/reinstall the stupid thing ?

I see you've been successful in doing WU's so far and have 4 recent outstanding WU's which I guess are the ones your having trouble with. That's telling me that it is less a BOINC/Rosetta application problem and more something that changed on your computer that is conflicting.

If you've made any changes to your computer very recently, you could try backing those changes out as a test as well to see if that solves the problem. It's possible the application files became corrupted though so try resetting the project if nothing else has worked.

---

I don't find there's any need to worry.

I moved my BOINC folder over to a different more stable HD on my system and I still get it although not as much. It happened with all projects. I just ignore it. The only pain was it lost CPU time and %Complete with the old Rosetta app. but now that's fixed, I don't find it's a problem, the WU just continues from where it left off.

Until it stops a WU from crunching I'll leave it be.

If you really are bothered, set Rosetta to No New Work, run the WU queue dry and then do a project reset.

Boinc-Wiki explanation

---