Message boards : Number crunching : Problems with Rosetta version 5.85 (or 5.86 for linux)
Previous · 1 . . . 3 · 4 · 5 · 6 · 7 · 8 · Next
Author | Message |
---|---|
upstatelabs Send message Joined: 22 Jun 06 Posts: 10 Credit: 516,767 RAC: 0 |
the VM useage is ridiculous - you're starting to lose people with lots of computers that have been running the project for a long time. Can we have some feedback on what's happening with this issue pls? Yes, I agree, what's the deal here? Is rosetta@home dumping all the loyal crunchers by having huge increases in system minimums? As if I have big $$ to apply to upgrades. It would also have been nicer if you'd let us know - so we don't waste time trying to figure it out. I like contributing to worthwhile projects, but I dislike being treated like a rube. How about an announcement on the main web page, for starters. A little courtesy goes a long way. |
eric Send message Joined: 2 Jan 07 Posts: 23 Credit: 815,696 RAC: 0 |
Two of my computers also crashed running the new version. One is a Intel P4 D with only 512 MB and the other is a X2 4600 with 1 GB RAM. I am also going to stop crunching Rosetta until this problem gets fixed. |
Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0 |
the VM useage is ridiculous - you're starting to lose people with lots of computers that have been running the project for a long time. Can we have some feedback on what's happening with this issue pls? There is ALOT of lack of communication in this project. For instance, the active workunits thread has not been touched in ages. We do not get any updates about where the project is headed or what successes have been seen in the work so far. There is ALOT of lack of communication in telling users what the cause or solution to their errors in the various versions or specific types of projects. Luckily with my old computer I do not get many errors or issues that newer and bigger computers get. But still the lack of any sort of comunication by the project leaders is a bit annoying. Except for the MOD's there isn't that much information being presented by the group. And as you see we lose another computer due to the lack of communication. |
Oldguy Send message Joined: 2 Nov 05 Posts: 1 Credit: 6,714,237 RAC: 0 |
[quote] the VM useage is ridiculous - you're starting to lose people with lots of computers that have been running the project for a long time. Can we have some feedback on what's happening with this issue pls? Yes, I agree, what's the deal here? Is rosetta@home dumping all the loyal crunchers by having huge increases in system minimums? As if I have big $$ to apply to upgrades. It would also have been nicer if you'd let us know - so we don't waste time trying to figure it out. I like contributing to worthwhile projects, but I dislike being treated like a rube. How about an announcement on the main web page, for starters. A little courtesy goes a long way. There is ALOT of lack of communication in this project. For instance, the active workunits thread has not been touched in ages. We do not get any updates about where the project is headed or what successes have been seen in the work so far. There is ALOT of lack of communication in telling users what the cause or solution to their errors in the various versions or specific types of projects. Luckily with my old computer I do not get many errors or issues that newer and bigger computers get. But still the lack of any sort of comunication by the project leaders is a bit annoying. Except for the MOD's there isn't that much information being presented by the group. And as you see we lose another computer due to the lack of communication. [/quoted] Is it just me or are some messages disappearing from this thread? |
googloo Send message Joined: 15 Sep 06 Posts: 133 Credit: 22,726,603 RAC: 3,137 |
Here's one: what does the error mean? And why did't I get any credit? TIA Task ID 125782244 Name 1mz9__BOINC_SYMM_FOLD_AND_DOCK_RELAX-1mz9_-crystal_foldanddock__2355_33156_0 Workunit 114342087 Created 10 Dec 2007 4:49:26 UTC Sent 10 Dec 2007 4:52:05 UTC Received 11 Dec 2007 15:02:07 UTC Server state Over Outcome Client error Client state Compute error Exit status 1 (0x1) Computer ID 307276 Report deadline 20 Dec 2007 4:52:05 UTC CPU time 4884.390625 stderr out <core_client_version>5.10.28</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> # cpu_run_time_pref: 10800 # random seed: 3706845 ERROR:: Exit from: .hbonds.cc line: 641 </stderr_txt> ]]> Validate state Invalid Claimed credit 12.703163708355 Granted credit 0 application version 5.85 |
Dr Who Fan Send message Joined: 28 May 06 Posts: 70 Credit: 268,055 RAC: 300 |
This task only ran for 1.482131 seconds before crashing with this error Too many restarts with no progress. Keep application in memory while preempted. Strange thing is all my tasks are set to stay in memory... the programmers need to take a close look at their code. https://boinc.bakerlab.org/rosetta/result.php?resultid=125202471 <core_client_version>5.10.28</core_client_version> <![CDATA[ <stderr_txt> # cpu_run_time_pref: 7200 # random seed: 3962165 No heartbeat from core client for 31 sec - exiting # cpu_run_time_pref: 7200 No heartbeat from core client for 31 sec - exiting # cpu_run_time_pref: 7200 No heartbeat from core client for 31 sec - exiting # cpu_run_time_pref: 7200 No heartbeat from core client for 31 sec - exiting # cpu_run_time_pref: 7200 No heartbeat from core client for 31 sec - exiting # cpu_run_time_pref: 7200 No heartbeat from core client for 31 sec - exiting Too many restarts with no progress. Keep application in memory while preempted. ====================================================== DONE :: 1 starting structures 1.33192 cpu seconds This process generated 0 decoys from 0 attempts 0 starting pdbs were skipped ====================================================== BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down... </stderr_txt> <message> <file_xfer_error> <file_name>w099_1_homologymodel_strictosidine_synthase_2352_37836_1_0</file_name> <error_code>-161</error_code> </file_xfer_error> </message> ]]> |
M.L. Send message Joined: 21 Nov 06 Posts: 182 Credit: 180,462 RAC: 0 |
Task ID 125312175 Name 1c9oA_BOINC_ABINITIO_BEST25_VF_SCORE3-5--1c9oA-vf__2360_200_0 Workunit 113902323 stderr out <core_client_version>5.10.28</core_client_version> <![CDATA[ <stderr_txt> # cpu_run_time_pref: 14400 # random seed: 3369001 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 # cpu_run_time_pref: 14400 ====================================================== DONE :: 1 starting structures 7468.3 cpu seconds This process generated 10621892 decoys from 1962295457 attempts ====================================================== Claims a new World record!!!!!! for number of decoys. Wishes I had seen the screen picture.There seems to be a prob with the cpu run times as I had to take PC for repairs and the shop did a saturation test and reboot over and over again trying to reproduce the fault. Sorry!! |
Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0 |
Task ID 125312175 Damn! 1422.26 decoys per second! |
Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0 |
Task ID 125312175 Damn! 1422.26 decoys per second! Thats a heck of a machine! |
Thomas Leibold Send message Joined: 30 Jul 06 Posts: 55 Credit: 19,627,164 RAC: 0 |
I'm still hoping to get some response regarding the validator errors that have been reported not just by myself but also several other users. I came to Rosetta from another DC project because I was disappointed in the way project members treated reports of problems by users and it sounded at the time that Baker Lab was doing a better job at that. I'm not so sure anymore that this is really the case. In the meantime here is something else (to be ignored?): Task ID 125965972 Name BAK_3chy_loop_model_2377_5470_0 Workunit 114511247 Created 11 Dec 2007 2:06:31 UTC Sent 11 Dec 2007 2:07:35 UTC Received 11 Dec 2007 10:18:34 UTC Server state Over Outcome Client error Client state Compute error Exit status 1 (0x1) Computer ID 679308 Report deadline 21 Dec 2007 2:07:35 UTC CPU time 0 stderr out <core_client_version>5.10.21</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> Graphics are disabled due to configuration... # cpu_run_time_pref: 28800 ERROR:: Exit from: fragments.cc line: 691 </stderr_txt> ]]> Validate state Invalid Claimed credit 0 Granted credit 0 application version 5.86 This one didn't even 'get off the ground' and failed instantly. Team Helix |
AMD_is_logical Send message Joined: 20 Dec 05 Posts: 299 Credit: 31,460,681 RAC: 0 |
I have one like the previous poster that exited from fragments.cc after zero time: https://boinc.bakerlab.org/rosetta/result.php?resultid=125960772 I also have two that exited from hbonds.cc after crunching for some hours: https://boinc.bakerlab.org/rosetta/result.php?resultid=125788003 https://boinc.bakerlab.org/rosetta/result.php?resultid=125738162 |
jond Send message Joined: 28 May 07 Posts: 3 Credit: 13,865 RAC: 0 |
the VM useage is ridiculous - you're starting to lose people with lots of computers that have been running the project for a long time. Can we have some feedback on what's happening with this issue pls? Add me to the list. I just came back to my computer a few minutes ago, and the rosetta screensaver was on and guess what... My computer was 100% locked. I finally had to hard power it down. I just suspended rosetta and am giving everything back to seti@home until this can be fixed. |
cg770 Send message Joined: 5 Oct 05 Posts: 1 Credit: 225,848 RAC: 0 |
Rosetta 5.85 beta has crashed and locked up 3 of my six computers that WERE dedicated to this project. Allowing users to opt out of beta testing would be swell. I'm taking my support elsewhere, it seems I'm working harder on this project than whomever is supposed to be running it. Sorry to see it come to this, but I don't feel like you care. CG |
EdMulock Send message Joined: 14 Mar 06 Posts: 30 Credit: 2,347,485 RAC: 0 |
Beta 5.85 causes my four Intel P4 cpus to crash in Visual C++ with a Runtime Error. This requires manual intervention, which I cannot give, since these are off-site. The error reads: Program ...Bakerlab.org_rosettarosetta_beta_5.05_windows_intelx86.exe The application requested the runtime to terminate in an unusual way. Please contact the applications suppport team for more information. These are crashing within 3 to 4 minutes. I've probably had 50 of these over the last two weeks. Here's an id.: 179513 |
par Send message Joined: 3 May 07 Posts: 3 Credit: 128,191 RAC: 0 |
As several others have posted, I am stopping all Rosetta work. I think this project has potential for producing something useful but I can't afford to have my systems shut down by something non-essential. Last night Rosetta requested 2G of virtual memory even though I have set it to only use 30% of virtual memory and there should only have been 1.2G of virtual memory. Not only did all Rosettas crash, but several other applications crashed and the only way to shut down was to power off. This is totally unacceptable. Please let me know when the project is better behaved. |
jegs Send message Joined: 16 May 07 Posts: 9 Credit: 80,767 RAC: 0 |
As several others have posted, I am stopping all Rosetta work. I think this project has potential for producing something useful but I can't afford to have my systems shut down by something non-essential. Set your VM to 3 gigs and crunch away. Works for me. |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
BOINC is in control of the memory allocation, and enforcing the configured limits, not Rosetta. So for those that are seeing your configured limits exceeded, please post about it on the BOINC message boards, and at a minimum let us know your BOINC version and your platform (Linux, Mac or Windows). Rosetta Moderator: Mod.Sense |
upstatelabs Send message Joined: 22 Jun 06 Posts: 10 Credit: 516,767 RAC: 0 |
BOINC is in control of the memory allocation, and enforcing the configured limits, not Rosetta. So for those that are seeing your configured limits exceeded, please post about it on the BOINC message boards, and at a minimum let us know your BOINC version and your platform (Linux, Mac or Windows). With all due respect, none of the other projects I participate in have this problem. Passing the buck will not get me to reassign hosts back to this project. Nevertheless, I am running BOINC versions 5.10.28 and 5.10.13, all on windows systems (98/2000/XP). The errors I have had occurred on both versions. |
jegs Send message Joined: 16 May 07 Posts: 9 Credit: 80,767 RAC: 0 |
BOINC is in control of the memory allocation, and enforcing the configured limits, not Rosetta. So for those that are seeing your configured limits exceeded, please post about it on the BOINC message boards, and at a minimum let us know your BOINC version and your platform (Linux, Mac or Windows). Only one of your machines meet the system requirements for Rosetta@home so if they crash don't blame the project. From the Rosetta@home recommended system requirements page. "If your machine does not meet the minimum system requirements, we recommend that you do not start the Rosetta@home project. If you have already started the project and decide it is too demanding on your PC, stop the BOINC client process or if you are using the BOINC Manager, "Detach" the Rosetta@home project. There may be other BOINC projects that are suitable for your machine." |
EdMulock Send message Joined: 14 Mar 06 Posts: 30 Credit: 2,347,485 RAC: 0 |
System Requirements : Windows XP 500MHz or higher 200MB 256MB Thats not the problem. |
Message boards :
Number crunching :
Problems with Rosetta version 5.85 (or 5.86 for linux)
©2024 University of Washington
https://www.bakerlab.org