I have a new computer (Windows 7 Professional, SSD). I am running BOINC 7.0.28 (x64). I was getting this message only on the rb tasks in the beginning, but when it started to happen on other tasks, I did as the messages suggested, and reset the project. Still happening. Any suggestions?

Here are the entire 2 lines: 8/28/2012 5:40:18 PM | rosetta@home | Task sfr_sc1_1014116m10_abinitio_SAVE_ALL_OUT_56042_170_0 exited with zero status but no 'finished' file
8/28/2012 5:40:18 PM | rosetta@home | If this happens repeatedly you may need to reset the project.

I have the same problem here, even after resetting the project. Whats going on here?? I run Boinc Manager 7.0.28 on a 64bit Windows 7 Ultimate, Rosetta has currently Mini Rosetta 3.41 running here...

I have no idea what to do...

---

On Rosetta this is usually solved by increasing the "use at most xxx% of CPU time" setting to 100. You may then want to reduce the "on multiprocessors, use at most xxx% of the processors" to something less than currently set. Most people find this handles the temperature regulation concerns (that the cpu throttling was designed to address) perfectly.

Another possible cause are virus scanners; most folks exclude BOINC from those scans or set it to run only when BOINC isn't active.

An explanation and more possible causes can be found here: BOINC FAQ Service

Please know that this only becomes a fatal error when it occurs 100 times to a particular task; at that point BOINC assumes the task will never be able to finish and gives up on it, ending it as a client error. If you see this message only occasionally it is safe to ignore it.


Best,
Snags

Sorry if I'm bit confused here, but there don't appear to be any errors in your finished tasks and credits are fully awarded. Or did I miss something?

Attempting to micro-manage every last warning message doesn't lead anywhere. On the rare occasion I ever see this kind of thing I've usually had an issue with another program I'm running which has a knock-on effect with Boinc, but not sufficiently that it actually breaks anything. Looks like nothing to me.

---

Seeing the same issue on a new Win7 machine that I cranked up with BOINC 7.0.28. Per your note, I've just switched from 75% CPU on four jobs (one per core) to 100% CPU, only two concurrent jobs. Waiting to see if that reduces the problem, and how the temperature settles out.

Question: Any correlation between this error and the, "mismatch" between Rosetta and BOINC 7.x? Should I be planning my retreat to BOINC 6 because I'm seeing this failure?

...
Please know that this only becomes a fatal error when it occurs 100 times to a particular task; at that point BOINC assumes the task will never be able to finish and gives up on it, ending it as a client error. If you see this message only occasionally it is safe to ignore it.


Best,
Snags

Understood, but does the restart imply loss-of-work back to the previous checkpoint for the job?

---

Seeing the same issue on a new Win7 machine that I cranked up with BOINC 7.0.28. Per your note, I've just switched from 75% CPU on four jobs (one per core) to 100% CPU, only two concurrent jobs. Waiting to see if that reduces the problem, and how the temperature settles out.

Question: Any correlation between this error and the, "mismatch" between Rosetta and BOINC 7.x? Should I be planning my retreat to BOINC 6 because I'm seeing this failure?

I shouldn't think so. This error message was first added for BOINC 5. We saw quite a spate of posts about it a while ago well before BOINC 7 was released. I haven't noticed any of the posts citing problems with BOINC 7 listing this as a symptom.

...
Please know that this only becomes a fatal error when it occurs 100 times to a particular task; at that point BOINC assumes the task will never be able to finish and gives up on it, ending it as a client error. If you see this message only occasionally it is safe to ignore it.


Best,
Snags

Understood, but does the restart imply loss-of-work back to the previous checkpoint for the job?

Yes but as Sid notes most of the time it isn't worth fretting over as a rare occurrence it would be difficult to track down the conflict and may be impossible to avoid. If it continues to happen frequently click through to the BOINC FAQ Service and check out Jord's list of suggestions. The link in my previous post takes you straight to the relevant page.


Best,
Snags

Question: Any correlation between this error and the, "mismatch" between Rosetta and BOINC 7.x? Should I be planning my retreat to BOINC 6 because I'm seeing this failure?

Rosetta OFFICIALLY does NOT support Version 7 of Boinc! They are happy with version 6 and are NOT upgrading any of their systems to support version 7. IF it works or not is not their concern. It DOES work for some people, but most find reverting to version 6 works better. Just be aware that downgrading means you WILL lose all existing units on your system, from EVERY Project!! So plan wisely!

...

Yes but as Sid notes most of the time it isn't worth fretting over as a rare occurrence it would be difficult to track down the conflict and may be impossible to avoid. If it continues to happen frequently click through to the BOINC FAQ Service and check out Jord's list of suggestions. The link in my previous post takes you straight to the relevant page.

Best,
Snags

It was definitely happening frequently, but I did try the suggestion of not using BOINC's CPU throttling (switched from using four cores at 75% to just two at 100%), and that seems to have cleaned the problem up for me, at the "cost" of a wider spread in core temperatures and somewhat less crunching that I was hoping to get done.

Thanks,
Alan

---

at the "cost" of a wider spread in core temperatures and somewhat less crunching that I was hoping to get done.

To get about the same job done you should use 3 cores @100%, that's 75% out of 4. Best performance you get of course with all 4 cores and since you apparently have enough RAM to run 4 tasks you could consider that, BOINC tasks are running at very low priority, so usually there should not be any performance issues with other applications.

---

.

Question: Any correlation between this error and the, "mismatch" between Rosetta and BOINC 7.x? Should I be planning my retreat to BOINC 6 because I'm seeing this failure?

Rosetta OFFICIALLY does NOT support Version 7 of Boinc! They are happy with version 6 and are NOT upgrading any of their systems to support version 7. IF it works or not is not their concern. It DOES work for some people, but most find reverting to version 6 works better. Just be aware that downgrading means you WILL lose all existing units on your system, from EVERY Project!! So plan wisely!

Thanks, mikey. Reverting to version 6.12.34 (x64) seems to have solved the problem.

---