Hi Snagletooth & Mod. Sense,

Snags you are the BOMB!!

I looked at the statement in Messages for what you suggested... "General prefs: from rosetta@home (last modified 31-Oct-2010 15:20:47)".
What I found was "General prefs: from SETI@home (last modified 21-Sep-2010 09:26:17)".

I logged into SETI to update my global "Computing Preferences". Made one change and clicked Update to see if it would work. I exited the BOINC app and then restarted BOINC, looked for the "General prefs" message and it had not changed. (Maybe because the SETI project is currently down)

I then decided to log into Rosetta and modified 1 item in the "Computing Preferences" and clicked Update. I then exited BOINC and restarted it.
Lo and behold I saw "11/3/2010 10:58:12 AM rosetta@home General prefs: from rosetta@home (last modified 03-Nov-2010 10:51:03)".

I'm now running just fine on both PCs with no "CPU usage too high" messages.

Thanks very much to you, Mod.Sense & Murasaki for taking the time with this and providing input. It is VERY much appreciated!!!! I was going through "crunch withdrawl".

Pardner

Well, Pardner, I don't know quite why that worked but nonetheless I am very happy it did. (And very glad Mod.Sense quickly caught my omission of the "update" step. Details, details are everything!)

Happy crunching,
Snags

If you are willing to satisfy my curiosity (or, more likely, risk provoking it further) you could say whether you ever saw the "Reading preferences override file".

All I can suggest is that this doesn't sound like how it was intended to work, and so I'd check to see if there is a fix in a newer version of BOINC Manager for such a problem. What BOINC version are you running?

Hi Mod.Sense,

I'm using BOINC 6.10.58 and I see that as the current/latest version. It's doing it on 2 of my computers too. Guess I just get the "fun issues". I think I'll let the Tasks that I have complete and then drop Rosetta since that's the only app where I have this issue.

Thanks anyway.

I know you went into local prefs to set them but did you confirm that BOINC is actually using them? The easiest way to do this is to quit BOINC. Upon restarting BOINC open the messages tab and look for "Reading preferences override file". It should be about 20 lines down. If it's not there, despite your best efforts, BOINC is using website prefs instead of local ones. It may simply be your copy of BOINC has developed a glitch and a reinstall is all that's needed to set things right again.

When using global prefs the BOINC client uses the most recently modified preferences. Rosetta@home uses a somewhat older server code that does not know about this relatively new client setting. IF, when you signed up a few days ago, you made any changes in the computing preferences section on the web site AND your BOINC client is insisting, for whatever reason, on using global instead of local prefs, then the client would default to 25% for this setting and that would explain what's happening. You can confirm where BOINC is reading the global prefs by looking at those first 20 lines in the messages tab. You should see a line something like "General prefs: from rosetta@home (last modified 31-Oct-2010 15:20:47)".

IF, while you were running SETI, you edited the computing preferences on the SETI website including changing that 25 to 0 AND your BOINC client is insisting, for whatever reason, on using global instead of local prefs, then, well, you would notice nothing wrong since your global and local prefs would exactly match.

It may be that signing up for a project using an older server code has exposed a fault in your copy of BOINC that was previously invisible.

If your client says it's reading the override file but you are still seeing the "cpu usage too high" message and, as in the message line described above, your "general prefs" are from rosetta, then try this: go back to the SETI website and edit the computing preferences again. You don't have to actually change anything; the goal is just to make sure the SETI prefs are the last modified and so the ones BOINC will use. You can check the modified date at the top of the web page. Restart BOINC and see what happens.

Of course, it would be odd for the same glitch to occur on two different PCs at the same time (unless you copied over a broken BOINC from the first pc to the second rather than downloading a fresh copy from Berkeley) so ... when you changed the local prefs did you close the window by clicking OK or by some other method? Forgive me if that sounds silly; I'm just trying to cover all the bases.


Best,
Snags

All I can suggest is that this doesn't sound like how it was intended to work, and so I'd check to see if there is a fix in a newer version of BOINC Manager for such a problem. What BOINC version are you running?

Thanks for the quick reply and info both Marasaki & Mod.sense.
I have been using SETI and of course BOINC for a while now. I'm familiar with the CPU usgae settings and mine are at 100% and 0 (run always). I did not have this issue when running the SETI Tasks. I am only running Rosetta now as SETI is down for a server upgrade so there is no competing for Projects.

As you are familiar with BOINC I assume you are aware that local settings can override web-settings. Therefore if you have checked the BOINC Manager preferences on your local computer and they say 0 then there isn't anything more I can suggest. Hopefully someone else can provide an answer.

I am new to Rosetta but am getting the Tasks "Suspended" a lot. The Task (a single Task) runs fine when I "Suspend" all the other Tasks. But if I let them all be active (so that 2 are "Running"),that's when the "Suspended" constantly occurs. I have verified that my PC meets all the "Minimum Requirements". Below is what I'm getting as far as "Messages".

This sounds like a problem with your BOINC preferences set on your computer. In your BOINC manager's preferences you will have a setting for running the programme "while processor usage is less than X%". If on that setting you have 25%, then when your CPU becomes more than 25% busy BOINC will suspend activity.

You can either set the setting to a higher percentage, or set it to 0% so the setting becomes ignored. When 0% is set BOINC will continue running as best it can no matter how busy your CPU is.

This update fixes the memory and invalidation issues from 2 weeks ago.
please report bugs here.