I have been getting messages like the one i copy pasted below for some time..i noticed it a couple weeks ago after i had begun running rosetta again ...i reset project and it seemed to be better for a few days or so but now i am continually getting these messages again. I reset it again last night but am still continually noticing messages similar to this one...

8/29/2015 10:44:18 AM | rosetta@home | Task gr081015_HEEHheeh_go3_nods_new_heeh_24.bp_r16_pass_20150719073127_fragments_fold_SAVE_ALL_OUT_291549_56_0 exited with zero status but no 'finished' file

any help or insite into this would be greatly appreciaited.

Your computers are hidden so I can't look at the actual tasks.

0 exit status is actually good - it indicates no errors - the problem is with the 'but no 'finished' file' part.

At first guess, it sounds like for some reason R@H is being denied write access (ie. by an overly zealous antivirus program - in my time on this forum I've seen antivirus being the root cause of probably more than half of these types of issues) or the disk is full (you'd probably know if your hard drive were full I'd guess though) or the Boinc DATA folder or sub folders related specifically to R@H (ie folders inside: C:ProgramDataBOINC if you installed with default settings on Windows) have some sort of permissions issue etc.

Would it be possible to un-hide your computers (in rosetta settings on this site under 'Your Account') so we can take a peak at the tasks on them more easily? Or provide links to the task details?

This is a common error and there are many threads about this on the forum. It is a BOINC issue that randomly affects all projects and not a Rosetta specific problem.

Just do a Google search for

"exited with zero status but no 'finished' file" rosetta

and you will find all sorts of advice. I could give you the answer now but I do get tired of writing the same thing everytime.

Timo i have un-hidden my computer...i will take a look online in the meantime to see what others have tried..the issue does seem to be related to only rosetta for me as i run 6 projects and i have never seen this message with any of the others before...not sure why you would post murasaki i am looking for help not negativity..if you don't want to help then you could have just foregone posting anything rather than basically saying you are tired of people asking the same question that you could answer but feel like not doing so.

I'm not being negative. I am just saying that you can find your answer in Google if you take 5 minutes to post the error information and the word Rosetta into the search bar and look through the first few entries.

You may find it beneficial to search before posting a question next time as you would have found the answer long ago yourself in this case. If you have tried searching and are still struggling then I would be far more sympathetic. Also, if you take a lesson from this and try searching next time, then my advice is positive - it depends on your perspective.

As I am having to post again anyway, one topic that you can find through searching is this thread where the user managed to fix the problem after trying the advice suggested.

As I said, the issue is a BOINC problem that affects projects at random. For you it has occurred with Rosetta, for others it affects SETI or other projects.

Well thanks for posting again...i had ruled out all the most common problems when i found a similiar post but i really dont want to set my cpu usage to 100..i already have only 4 of 6 cores running at 90 and it heats up my machine pretty good...i will set to 100 and see what happens and maybe just run 3 cores..or if that is the only fix maybe i just drop rosetta and run my other projects at my preferences...i really dont want to upgrade a heat sink just to run this application.

I've always found BOINC's "use at most x% of CPU time" to be poorly implemented (it seems to basically 'sleep' for entire seconds out of a 10 second period - ie. putting it at 90% will mean it runs 100% for 9 seconds and then take a 1 second break.. I could often hear the fan spinning up and down - reglardless of project.)

On some of my machines where temperature is more of a concern, I have instead modified the CPU power inside the windows power plan, which effectively changes the clock speed of the CPU so it can run at "100%" at a lower clock speed and achieve the temperatures I want without having to worry about anything.

To do this, goto Power Options (Start->Search for 'Power Options' in the start menu is the easiest way, though it can also be accessed from Control Panel)

Then change the maximum CPU temps by modifying the plan settings (Note you may need to click on 'Change settings that are currently unavailable' in a couple places not shown in my screenshots here**)






Once you're here, you're looking for 'Maximum Processor State' under Processor power management which is a percentage that will allow the OS to control the CPU clock speed maximum in a much more robust way than BOINC itself can:


I hope that helps :)

Thanks for the tip i will try that and see how it works..what you stated at the beginning is exactly what my pc does at 100..i can hear the fan cycling up and down constantly which is what is concerning me..it only does it when i run boinc so i think this will definitely help.I appreciate you taking the time to post this for me.

edit... :-) set it to 95..no more cycling at all...i doubt i will notice any performance difference in other applications.

Thanks for the tip i will try that and see how it works..what you stated at the beginning is exactly what my pc does at 100..i can hear the fan cycling up and down constantly which is what is concerning me..it only does it when i run boinc so i think this will definitely help. I appreciate you taking the time to post this for me.

edit... :-) set it to 95..no more cycling at all...i doubt i will notice any performance difference in other applications.

This is a bit confusing. Aren't the fans supposed to respond in this way?

Last year I decided to review the cooling in my PC after I started overclocking. I started simple with the case fans and accepted a recommendation from my local store. I didn't expect much tbh because they didn't look any different to what I already had, but I was positively shocked by the improvement, both in temperature and reduced noise. The temperature drop at normal speeds may prevent any need for them to kick up at all.

The fan I was pointed toward was the Coolermaster JetFlo 120mm - I see they're just $7 in the US (£10 in England for some unknown reason). Even if you keep your other settings as they are, it's a nice cheap and trivial upgrade that's worth considering.

---

This is a bit confusing. Aren't the fans supposed to respond in this way?

Yes, the fans ARE supposed to respond in this way - the problem is that the cycling of fans from high to low is audibly annoying. The fix I posted above basically removes the need to have BOINC's inefficient CPU time throttling, and instead offers a much more robust way of regulating the CPU clock speed from within the OS in a manner that keeps the fans running at a constant, and less audible speed.

PanicMan sent me a private message a bit after this and reported that not only did this offer a great fix for him, but its allowed him to run 5 cores out of 6 (he was previously running 4 out of 6) while keeping things cool and quiet.

This is a bit confusing. Aren't the fans supposed to respond in this way?

Yes, the fans ARE supposed to respond in this way - the problem is that the cycling of fans from high to low is audibly annoying. The fix I posted above basically removes the need to have BOINC's inefficient CPU time throttling, and instead offers a much more robust way of regulating the CPU clock speed from within the OS in a manner that keeps the fans running at a constant, and less audible speed.

PanicMan sent me a private message a bit after this and reported that not only did this offer a great fix for him, but its allowed him to run 5 cores out of 6 (he was previously running 4 out of 6) while keeping things cool and quiet.

Yes, I agree the method of throttling is unusual in BOINC. I noticed it some years ago using a sidebar gadget in Vista.

I can also appreciate the problem is to do with noise rather than normal operation, so I thought it worth mentioning both the improved airflowcooling at standard speed as well as the quietness (and cheapness) of replacements for what's supplied as stock can be very worthwhile. The ones I bought came with little extension cables that retarded the maximum speed from 2000RPM to 1600 or 1200RPM if that was all that's necessary.

I just found them neat, simple and effective and continue to use them when I upgraded.

---

I know of the speed limiting cables you speak of Sid, they are great, I had some come with a Noctua case fan I purchased. If one simply wants to limit fan speeds - at least when it comes to the actual CPU fan, other fans may not be controllable - you can use programs like SpeedFan but a) you want to ensure you're not overheating your CPU and b) it does have a bit of a technical/power user tilt to how it's designed so use at your own risk *in fact I don't recommend using this program unless you know what you're doing

I know of the speed limiting cables you speak of Sid, they are great, I had some come with a Noctua case fan I purchased. If one simply wants to limit fan speeds - at least when it comes to the actual CPU fan, other fans may not be controllable - you can use programs like SpeedFan but a) you want to ensure you're not overheating your CPU and b) it does have a bit of a technical/power user tilt to how it's designed so use at your own risk *in fact I don't recommend using this program unless you know what you're doing

Certainly not with the CPU fan, I agree. That's a whole other ball game that takes a bit of research. I'm only talking about case fans - they're $7 after all. Most of the fan noise I've ever noticed has come from there.

I have upgraded my CPU cooling a couple of times. My first attempt brought very disappointing results. It was only when I got new case fans - almost as an afterthought, with no expectations - that I found the heat was finally being removed from the case. As I said, a higher throughput as standard, while being quieter. And because of the more efficient heat removal, it didn't need to kick up the speed either. (I'm sure I've said this a few times, so I'll stop now)

---