This thread is for reporting problems with Rosetta Version 5.22.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

My compuer is freezing on one of these two WUs - 19746278 or 19737574. It's happened several times today. I'd come into the room, note that the graphics weren't animated, the steps weren't incrementing, and the clock would be stopped. I'd move the mouse (I have it configured to work on the project only when I'm not using the machine), and would get a notice that there was an error and would I like to report to MicroSoft. Next time, I'll get a screenshot.

Bandit's Mom

---

My compuer is freezing on one of these two WUs - 19746278 or 19737574. It's happened several times today. I'd come into the room, note that the graphics weren't animated, the steps weren't incrementing, and the clock would be stopped. I'd move the mouse (I have it configured to work on the project only when I'm not using the machine), and would get a notice that there was an error and would I like to report to MicroSoft. Next time, I'll get a screenshot.

Bandit's Mom

It is possible that there is a background task running(disk defrag, virus check, etc) that is preventing your system from becoming fully idle. This of course would also prevent BOINC from processing any work.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

It is possible that there is a background task running(disk defrag, virus check, etc) that is preventing your system from becoming fully idle. This of course would also prevent BOINC from processing any work.

Nope - the only other things I have open are Word (x2), Excel (x2), Reference Manager, and a Mah Jongg game program.

Here's the text of the error message: "rosetta_5.22_windows_intelx86.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Bandit's Mom

---

It is possible that there is a background task running(disk defrag, virus check, etc) that is preventing your system from becoming fully idle. This of course would also prevent BOINC from processing any work.

Nope - the only other things I have open are Word (x2), Excel (x2), Reference Manager, and a Mah Jongg game program.

Here's the text of the error message: "rosetta_5.22_windows_intelx86.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Bandit's Mom

There was a problem with the screen saver on some Windows systems with version 5.16. This was supposed to be fixed in the new release. Have you tried running BOINC with the screen saver turned off?

In order to assist you you will either have to provide a link to the reported results in your Stats list, or make your computer visible. Currently your computers are hidden so I cannot look up any of your results to see the actual errors.

You can make your computers visible from your preferences without risk to your computer security. If you want to see the kind of information others might see, you can clink on any other user in the forums, and then clink on the link to view their computers.

Of course the system will allow you to see more information on your own systems than it would reveal to others.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

---

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

This is a normal shutdown for a successfully completed workunit.

The note regarding the watchdog is just to identify that now that the work unit has finished, the watchdog function is being closed down as well.

---

Regards,
Bob P.

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

This is a normal shutdown for a successfully completed workunit.

The note regarding the watchdog is just to identify that now that the work unit has finished, the watchdog function is being closed down as well.

Noted and thanks Bob for your clarification

Regards
Ricardo

---

I've turned the screensaver off on the Control Panel - is there something I should do in my BOINC preferences? (Color me ignorant, and what I read isn't staying with me at the moment.) You should be able to "see" my computer now, unless there's something else I should do. "... provide a link to the reported results in your Stats list ..." Not sure how to do this.

Bandit's Mom

There was a problem with the screen saver on some Windows systems with version 5.16. This was supposed to be fixed in the new release. Have you tried running BOINC with the screen saver turned off?

In order to assist you you will either have to provide a link to the reported results in your Stats list, or make your computer visible. Currently your computers are hidden so I cannot look up any of your results to see the actual errors.

You can make your computers visible from your preferences without risk to your computer security. If you want to see the kind of information others might see, you can clink on any other user in the forums, and then clink on the link to view their computers.

Of course the system will allow you to see more information on your own systems than it would reveal to others.

---

...You should be able to "see" my computer now, unless there's something else I should do.

They still show "hidden". In your Rosetta preferences, select YES for the question "Should Rosetta@home show your computers on its web site". More details here.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

It's selected as "yes." Maybe it needed time to implement in the system. Maybe you could try again?

Bandit's Mom

They still show "hidden". In your Rosetta preferences, select YES for the question "Should Rosetta@home show your computers on its web site".

---

It's selected as "yes." Maybe it needed time to implement in the system. Maybe you could try again?

Did you hit the "Update preferences" button at the bottom of the screen? I just looked again and it still shows as "hidden".

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I went back to look and it was saved as "yes," but hit the "Update" button again, just for giggles and grins. Maybe it didn't take the first time around.

Bandit's Mom

Did you hit the "Update preferences" button at the bottom of the screen? I just looked again and it still shows as "hidden".

---

I went back to look and it was saved as "yes," but hit the "Update" button again, just for giggles and grins. Maybe it didn't take the first time around.

Bandit's Mom

Did you hit the "Update preferences" button at the bottom of the screen? I just looked again and it still shows as "hidden".

Looking at your two errors, one is not well described, and in fact looks like a normal work unit. The latest has a fountain of error data to examine, but at first glance it does seem to be related to the screen saver issue, (-107 error) but the window that was in the foreground when the system terminated the work unit was Explorer. This could just be an artifact of the way windows uses explorer, but is there any chance you had left your browser loaded when the problem occurred?

My best guess right now is that if you set your screen saver to something other than BOINC or turn it off (from what I read you already did that) the problem may go away. If it does could you please let us know? We are trying to fix that particular issue, and the programmers thought they had it under control. We need to know if they do not.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

It's not only possible, it's probable that IE was loaded. With the BOINC screensaver off, I'm not certain that I would be able to tell that there was a problem as quickly, but am willing to give it a go.

I'm going to switch my computer back to "hidden."

Thanks for your help.

Bandit's Mom

... but is there any chance you had left your browser loaded when the problem occurred?

My best guess right now is that if you set your screen saver to something other than BOINC or turn it off (from what I read you already did that) the problem may go away. If it does could you please let us know? We are trying to fix that particular issue, and the programmers thought they had it under control. We need to know if they do not.

---

...I'm going to switch my computer back to "hidden."

Thanks for your help.

Bandit's Mom
...

While there is no requirement that you leave your computer visible, there is no real risk to you in doing os. It is almost impossible for people to assist you unless they can look at the work unit results for your computer if there is a problem. it is your choice however.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Hello Moderator9

I pulled a client error on Work Unit 19677012 (the result is at https://boinc.bakerlab.org/rosetta/result.php?resultid=23357465), with exit code -1. Client messages for the error began with, "rosetta not responding to screensaver, exiting"

Then again on WU 19684873 (result link https://boinc.bakerlab.org/rosetta/result.php?resultid=23366061). Exit code was again -1, client-side messages once again report, "rosetta notresponding to screensaver, exiting".

The first was a 5.16 client, the second was with a 5.22. I'm not sure the screensaver bug is completely dead yet?

Cheers,
Alan

---

I have sent a message to the project team regarding the possibility that the screen saver may still be causing problems for a few of you. If you report a problem that seems related to the screen saver, please be certain to make your computers visible in your preferences to assist them in examining the problem. Also if you could provide a link to any workunit results that may have been produced during the time you noticed the problem that would be helpful.

For those of you who may not know how to create a link -

1) Go to the place you want the link to take the user and copy the "HTTP" address from the browser address field at the top of your browser window.
2) Open the post in which you wish to place the link and type "[_url=" (leaving out the "_" which I have added here to disable the command) at the point in the message where you want the link to appear.
3) Paste the link address after the "=" with no spaces and add a "]" to the end of the address.
4) Type any text you may want to identify the link.
5) Complete the link command by typing "[/url]".

So if I wanted to create a link to the Rosetta FAQs it would look like this -
(Except you would leave out the "_", which I added for display purposes)

[_url=https://boinc.bakerlab.org/rosetta/forum_thread.php?id=669]Rosetta FAQs[/url]

And it would look like this in the final message.

Rosetta FAQs

Thank you.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Possible problem with a t299_CASP7 work unit (link to WU). Was a happy camper, then at step 370K+ on Model 6 my CPU dropped from 100% to nothing, and graphics display showed no progress. Didn't write down the stuck step number, sorry.

Suspend on that task released the waiting next, which drove the CPU back to full load. Suspended task #2 and resumed #1, but it still didn't seem to grab any CPU.

For lack of knowing any better (new user), I shutdown BOINC and restarted, which I think I understand to mean that the task resumes at the previous checkpoint (model boundary)? It is now running again.

What is accepted practice if it hangs up again, please? Do I wait for some watchdog abort, or manually abort it? I don't really care about credits, I'll take whatever action provides the best feedback about the failure. Thanks!

---

see above

---