Problems with Rosetta version 5.40

Message boards : Number crunching : Problems with Rosetta version 5.40

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4

AuthorMessage
Profile Feet1st
Avatar

Send message
Joined: 30 Dec 05
Posts: 1755
Credit: 4,690,520
RAC: 0
Message 31815 - Posted: 29 Nov 2006, 15:24:57 UTC

Buffalo Bill, I wanted to clarify your situation a little if we can. Could you copy/paste the message you were seeing? Also, I wanted to confirm which direction the file was heading when you had problems. From Rosetta to your PC is a "download"... to send the result from your PC back to Rosetta is an "upload". Since many people misuse the terms, I just wanted to be sure.
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/
ID: 31815 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Buffalo Bill
Avatar

Send message
Joined: 25 Mar 06
Posts: 71
Credit: 1,630,458
RAC: 0
Message 31825 - Posted: 29 Nov 2006, 17:36:52 UTC - in response to Message 31815.  

Buffalo Bill, I wanted to clarify your situation a little if we can. Could you copy/paste the message you were seeing? Also, I wanted to confirm which direction the file was heading when you had problems. From Rosetta to your PC is a "download"... to send the result from your PC back to Rosetta is an "upload". Since many people misuse the terms, I just wanted to be sure.


I don't have the message but it looks like the same one Steffen got. At that point the task had completed and was "Uploading" just before the "Ready to report" message normally appears in the Status column of the tasks page.
ID: 31825 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mike Gelvin
Avatar

Send message
Joined: 7 Oct 05
Posts: 65
Credit: 10,612,039
RAC: 0
Message 31826 - Posted: 29 Nov 2006, 17:43:04 UTC
Last modified: 29 Nov 2006, 18:01:17 UTC

This result did not progress beyond 20 seconds on a remote computer for 9 days

DOC_1FSS_R061114_pose_u_global_search_1402_1511

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=42483747

I stopped BOINC, and restarted, it froze again at 19 seconds

I aborted the work unit.

Work units that hog the resources of a computer are UNACCEPTABLE!

This is the second time in a few months that Rosetta has messed up on the production (not Ralph) site.

One more time and I shall pull my support of Rosetta.

Edit: I think I have another system out there that has been hung for 29 days but since you seem to purge results going back that far, I cant tell if its Rosetta that's the problem. I am not scheduled to visit that site for another 3 weeks, so it looks like that system is useless to ALL BOINC projects until I can clear you out.

A scary thought is that some of my remote computers are hyper-threaded, or have multi-processors. A Rosetta task could take down one of the cores and yet the computer will still report into projects and I won’t be able to tell.
ID: 31826 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
R.L. Casey

Send message
Joined: 7 Jun 06
Posts: 91
Credit: 2,728,885
RAC: 0
Message 31855 - Posted: 30 Nov 2006, 13:49:58 UTC - in response to Message 31826.  

This result did not progress beyond 20 seconds on a remote computer for 9 days

DOC_1FSS_R061114_pose_u_global_search_1402_1511

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=42483747

I stopped BOINC, and restarted, it froze again at 19 seconds

I aborted the work unit.
...


Mike, the computer you reference has only 128 MB of RAM. I have a small laptop crunching Roseta that has only 168 MB, and for some work units, it can take a very long time to show progress. Also, you might want to check the amount of cache and increase it if possible. I try to run around 1 GB on the laptop. It's slow, but persistent! :-)



ID: 31855 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mike Gelvin
Avatar

Send message
Joined: 7 Oct 05
Posts: 65
Credit: 10,612,039
RAC: 0
Message 31870 - Posted: 30 Nov 2006, 18:38:20 UTC - in response to Message 31855.  
Last modified: 30 Nov 2006, 18:54:48 UTC

This result did not progress beyond 20 seconds on a remote computer for 9 days

DOC_1FSS_R061114_pose_u_global_search_1402_1511

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=42483747

I stopped BOINC, and restarted, it froze again at 19 seconds

I aborted the work unit.
...


Mike, the computer you reference has only 128 MB of RAM. I have a small laptop crunching Roseta that has only 168 MB, and for some work units, it can take a very long time to show progress. Also, you might want to check the amount of cache and increase it if possible. I try to run around 1 GB on the laptop. It's slow, but persistent! :-)



I'm not talking about progress... I'm talking about CPU time accumulated. It froze at 20 seconds.


Edit: Thanks for pointing out the 128 issue. I have detached this computer from the project.



ID: 31870 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Conan
Avatar

Send message
Joined: 11 Oct 05
Posts: 150
Credit: 3,818,279
RAC: 728
Message 31897 - Posted: 1 Dec 2006, 11:09:19 UTC

The following result locked up on the 25/11 and did not go again till I checked the machine on the 30/11. As a single core computer this meant that nothing else processed till I aborted the workunit, so 5 days lost production.

https://boinc.bakerlab.org/rosetta/result.php?resultid=47666358

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x77F75A58

Engaging BOINC Windows Runtime Debugger...

No screensaver involved as on this machine Boinc is installed as a service.
ID: 31897 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 · 2 · 3 · 4

Message boards : Number crunching : Problems with Rosetta version 5.40



©2024 University of Washington
https://www.bakerlab.org