Problems with version 5.90/5.91
Message boards : Number crunching : Problems with version 5.90/5.91
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
| Author | Message |
|---|---|
|
Shippley Watson Send message Joined: 17 Dec 07 Posts: 1 Credit: 924 RAC: 0 |
Hello. I am running Mac OS 10.5.1 and using BOINC Manager. I run rosetta@home, einstien@home, ABC@home, as well as seti@home, QMC@home, and uFluids. Recently, seemingly randomly, I have an icon in my dock for an application thats running called "rosetta_beta_5.90_i686-apple-darwin". I can't quit it, I can't Force Quit it. The only way to make it go away, is to log out, and log back in. I don't think it should be there. If it's needed (and I assume it is), maybe it should be hidden somehow. Thanks |
|
BarryAZ Send message Joined: 27 Dec 05 Posts: 153 Credit: 30,843,285 RAC: 0 |
Same here -- on a number of different systems. This task triggered both the Windows debugger and the BOINC debugger. 
|
|
M.L. Send message Joined: 21 Nov 06 Posts: 182 Credit: 180,462 RAC: 0 |
Task ID 128909434 Name 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_55494_0 Workunit 117217885 Created 24 Dec 2007 13:28:53 UTC Sent 24 Dec 2007 13:31:00 UTC Received 27 Dec 2007 6:06:56 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x0) Computer ID 510574 Report deadline 3 Jan 2008 13:31:00 UTC CPU time 6762.234 stderr out <core_client_version>5.10.30</core_client_version> <![CDATA[ <stderr_txt> # cpu_run_time_pref: 14400 # random seed: 3430437 ********************************************************************** Rosetta score is stuck or going too long. Watchdog is ending the run! Stuck at score -88.8884 for 900 seconds ********************************************************************** GZIP SILENT FILE: .xx1zpy.out </stderr_txt> ]]> AMD 4800 4GB ram - W xp2. |
 Conan Send message Joined: 11 Oct 05 Posts: 150 Credit: 4,236,942 RAC: 3,767 
|
> This WU stopped doing anything after completing about 50%, just sat there on High Priority but was dead. Restarting BM did not fix this one. Two others were also locked up but after restarting BM they started again and then completed. This WU did not even start. Just sat there in High Priority but was not doing anything. I aborted both of these WU's. |
rochester new york Send message Joined: 2 Jul 06 Posts: 2842 Credit: 2,020,043 RAC: 0 |
|
|
Luuklag Send message Joined: 13 Sep 07 Posts: 262 Credit: 4,171 RAC: 0 |
Task ID 129266698 Name Molecular_replacement_trial_for_phasing_StrGen_target_w009_2478_118352_0 Workunit 117538029 Created 26 Dec 2007 17:36:29 UTC Sent 26 Dec 2007 17:39:28 UTC Received 27 Dec 2007 15:18:11 UTC Server state Over Outcome Client error Client state Done Exit status 1 (0x1) Computer ID 600844 Report deadline 5 Jan 2008 17:39:28 UTC CPU time 5742.5 stderr out <core_client_version>5.10.20</core_client_version> <![CDATA[ <message> Onjuiste functie. (0x1) - exit code 1 (0x1) </message> <stderr_txt> # cpu_run_time_pref: 14400 # random seed: 2967579 ABORT: bad to aa_rotno_to_packedrotno aa,rot1/2/3/4: MET 11 2 0 0 0 chi no 2 nchi 3 aav 1 is_chi_proton_rotamer(aa,aav,i) 0 ERROR:: Exit from: .rotamer_functions.cc line: 1461 </stderr_txt> ]]> Validate state Invalid Claimed credit 18.9503408337319 Granted credit 0 application version 5.90 after 1 hour and 35 minutes |
|
sslickerson Send message Joined: 14 Oct 05 Posts: 101 Credit: 578,497 RAC: 0 |
Here's one that fell about 22 hours short of my expected runtime. Seriously, what is going on here? This is starting to become ridiculous. I literally went hundreds of days without so much as a hiccup but I have had maybe a dozen errors in just the past week... 129143112 |
|
Luuklag Send message Joined: 13 Sep 07 Posts: 262 Credit: 4,171 RAC: 0 |
Major, major flaws in any 1zpy job with TWIST_RINGS and only those jobs.Any other 1zpy job runs properly. And before anyone blames my computers, I went through Thomas Leibold's computers and his results are showing the same problems. next time dont post the log like this, this makes the lay out of the forum go mad, it becomes absurdly wide, post it with enters in between or something, but not like this.!!!! |
Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0 |
Major, major flaws in any 1zpy job with TWIST_RINGS and only those jobs.Any other 1zpy job runs properly. And before anyone blames my computers, I went through Thomas Leibold's computers and his results are showing the same problems. i looked at his original post with my browser in full screen and i did not have to scroll side to side, except for one line which is a complete task description line. Other than that there was nothing wrong with the original post. my only comment is to get rid of the extra information not related to the task so that it is not so long and we see only the relevant information. |
David Emigh Send message Joined: 13 Mar 06 Posts: 158 Credit: 417,178 RAC: 0 |
Major, major flaws in any 1zpy job with TWIST_RINGS {...} So, at this point, an already lengthy post has been reposted in its entirety not once, but TWICE. Truly an exercise in absurdity. Rosie, Rosie, she's our gal, If she can't do it, no one shall! |
|
Snags Send message Joined: 22 Feb 07 Posts: 198 Credit: 2,888,320 RAC: 0 |
I am currently working on 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_167254. When I checked on it after around 9 hours it was working on the 2nd model having completed somewhere north of 72000 steps. Checking now after running for 17:42:03 it is still working on the 2nd model having completed 72751 steps. With a preferred runtime of 10 hours I would not have expected it to begin the second model (unless I misunderstand how that is supposed to work). I have no problem with setting the runtime for many hours longer than ten if it is helpful to the project but if I set it at 24 hours and it occasionally runs twice that don't I risk deadline problems (by confusing BOINC and overcommitting to my other projects if not rosetta)? I should also note that it is only by opening the graphics window that I can see that progress is still being made as the to completion time no longer updates presumably because BOINC thought it should be done over 17 hours ago and no longer has a clue what to expect. I wonder if this is causing some people to abort prematurely? Any ideas or comments would be welcome Snags edit: I'm sorry I don't know why this isn't wrapping properly. If someone can tell me what to do to fix it I'll gladly do so. |
Yank Send message Joined: 18 Apr 06 Posts: 71 Credit: 1,752,514 RAC: 0 |
Running Rosetta Beta 5.90 on a few machine, both Windows XP and Vista, and when checking the computers I am getting a lot of messages from the windows program some thing like...(we have encounter a problem with BOINC program 5.90 and shutting down). Can you tell me what the problem is? I haven't seen any line of data in the message area of the BOINC manager stating that a units was aborted. I have the BOINC version 5.10.28.  
|
|
Yank Send message Joined: 18 Apr 06 Posts: 71 Credit: 1,752,514 RAC: 0 |
Just up-dated BOINC program to 5.10.30. Maybe that was the problem?
|
|
M.L. Send message Joined: 21 Nov 06 Posts: 182 Credit: 180,462 RAC: 0 |
Task ID 129048149 Name 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_180091_0 Workunit 117342482 Created 25 Dec 2007 12:50:34 UTC Sent 25 Dec 2007 12:51:21 UTC Received 27 Dec 2007 23:53:02 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x0) Computer ID 510574 Report deadline 4 Jan 2008 12:51:21 UTC CPU time 10432.66 stderr out <core_client_version>5.10.30</core_client_version> <![CDATA[ <stderr_txt> # cpu_run_time_pref: 14400 # random seed: 3305840 ********************************************************************** Rosetta score is stuck or going too long. Watchdog is ending the run! Stuck at score -78.916 for 900 seconds ********************************************************************** GZIP SILENT FILE: .xx1zpy.out </stderr_txt> ]]> Validate state Valid Claimed credit 43.204186881999 Granted credit 48.9267252692226 application version 5.90 |
|
Snags Send message Joined: 22 Feb 07 Posts: 198 Credit: 2,888,320 RAC: 0 |
I am currently working on 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_167254. When I checked on it after around 9 hours it was working on the 2nd model having completed somewhere north of 72000 steps. Checking now after running for 17:42:03 it is still working on the 2nd model having completed 72751 steps. With a preferred runtime of 10 hours I would not have expected it to begin the second model (unless I misunderstand how that is supposed to work). I have no problem with setting the runtime for many hours longer than ten if it is helpful to the project but if I set it at 24 hours and it occasionally runs twice that don't I risk deadline problems (by confusing BOINC and overcommitting to my other projects if not rosetta)? I should also note that it is only by opening the graphics window that I can see that progress is still being made as the to completion time no longer updates presumably because BOINC thought it should be done almost 10 hours ago and no longer has a clue what to expect. I wonder if this is causing some people to abort prematurely? update:Completed 2 decoys in 2 attempts in 77911.01 seconds, validated and credit granted. result |
|
Conan Send message Joined: 11 Oct 05 Posts: 150 Credit: 4,236,942 RAC: 3,767
|
Had this WU that ran for 4 times as long as my preferences. It was running at High Priority but BM only showed less than 1 minute or so completed. If I kept watching every now and then a total would flash (25 H xx M xx S), then go back to the less than 1 minute total. I exited and then restarted BM and the result finished and uploaded without an error. This is the same problem we were having before on Linux, the WU would have kept running but for me stopping Boinc Manager. |
|
Greg_BE Send message Joined: 30 May 06 Posts: 5691 Credit: 5,859,226 RAC: 0 |
i don't know what problems were happening with the zpy tasks, but this one ran just fine. 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_1337_0 result was ok and credit granted was within the norm. i'm using a AMD 2800+ with Win XP SP2. |
|
Luuklag Send message Joined: 13 Sep 07 Posts: 262 Credit: 4,171 RAC: 0 |
this one errored out after just 16 min. error |
Astro Send message Joined: 2 Oct 05 Posts: 987 Credit: 500,253 RAC: 0 |
wooohoooo I got the 100th post. OK OK back to bidness. There's definitely something wrong with 5.90/5.91. Either the watchdog is set to a value below what it should be causing the watchdog to end a task, or the app itself has an error, or the Job type has an error, or it might be something else entirely. How can I make this claim??? your ask?? Below is a chart of all my recorded work from app 5.82 upwards (except 5.90 for linux which is "known bad"). You can see that the former apps didn't have near the incidence of watchdog time out that 5.91 does.  Note how there aren't any watchdog errors on earlier versions and almost no compute errors for earlier windows versions. The "compute" errors for earlier linux versions are tied to the "loss of internet" errors which I reported earlier. For host names 6000l is AMD64 X2 6000 under linux, 6000w is the same under windows, etc etc etc for the others. |
|
Astro Send message Joined: 2 Oct 05 Posts: 987 Credit: 500,253 RAC: 0 |
Here's a list of ALL the watchdog ended tasks for all hosts/OSes using 5.90 or 5.91 since Nov 26th 2007... Do they have something in common??? 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12692_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12604_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12581_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12309_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12265_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12266_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12225_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12206_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11882_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10396_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10466_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_14658_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_115770_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_115774_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_121452_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_156769_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_161145_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_183748_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_36172_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_148361_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_144472_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_144384_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_143544_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11173_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11055_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11186_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11059_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12138_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_15985_1 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_74554_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_74522_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10255_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10233_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10229_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_73415_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_73402_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_73393_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_50756_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_13658_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_13656_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_13652_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11899_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11965_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11959_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11976_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10875_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10838_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10826_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_10090_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_11281_0 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_30600_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12760_0 1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2470_12740_0 There are NO watch dog ended tasks for apps earlier than 5.90/5.91 |
Message boards :
Number crunching :
Problems with version 5.90/5.91
©2024 University of Washington
https://www.bakerlab.org