Problems with version 5.90/5.91

Message boards : Number crunching : Problems with version 5.90/5.91

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next

AuthorMessage
Profile David Emigh
Avatar

Send message
Joined: 13 Mar 06
Posts: 158
Credit: 417,178
RAC: 0
Message 50091 - Posted: 27 Dec 2007, 0:05:09 UTC
Last modified: 27 Dec 2007, 0:09:08 UTC

This task triggered both the Windows debugger and the BOINC debugger.

It was a "1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_ etc." task.
Rosie, Rosie, she's our gal,
If she can't do it, no one shall!
ID: 50091 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Shippley Watson

Send message
Joined: 17 Dec 07
Posts: 1
Credit: 924
RAC: 0
Message 50092 - Posted: 27 Dec 2007, 1:14:22 UTC
Last modified: 27 Dec 2007, 1:15:22 UTC

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
ID: 50092 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
BarryAZ

Send message
Joined: 27 Dec 05
Posts: 153
Credit: 30,841,260
RAC: 237
Message 50096 - Posted: 27 Dec 2007, 6:47:19 UTC - in response to Message 50091.  

Same here -- on a number of different systems.



This task triggered both the Windows debugger and the BOINC debugger.

It was a "1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_ etc." task.


ID: 50096 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
M.L.

Send message
Joined: 21 Nov 06
Posts: 182
Credit: 180,462
RAC: 0
Message 50097 - Posted: 27 Dec 2007, 8:24:40 UTC

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.
ID: 50097 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Conan
Avatar

Send message
Joined: 11 Oct 05
Posts: 148
Credit: 3,290,567
RAC: 558
Message 50101 - Posted: 27 Dec 2007, 11:18:51 UTC

> 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.
ID: 50101 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile rochester new york
Avatar

Send message
Joined: 2 Jul 06
Posts: 2839
Credit: 2,020,043
RAC: 0
Message 50104 - Posted: 27 Dec 2007, 12:20:22 UTC
Last modified: 27 Dec 2007, 12:21:15 UTC

ID: 50104 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luuklag

Send message
Joined: 13 Sep 07
Posts: 262
Credit: 4,171
RAC: 0
Message 50105 - Posted: 27 Dec 2007, 15:19:13 UTC

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
ID: 50105 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile sslickerson

Send message
Joined: 14 Oct 05
Posts: 101
Credit: 578,497
RAC: 0
Message 50107 - Posted: 27 Dec 2007, 16:10:35 UTC
Last modified: 27 Dec 2007, 16:11:11 UTC

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
ID: 50107 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luuklag

Send message
Joined: 13 Sep 07
Posts: 262
Credit: 4,171
RAC: 0
Message 50112 - Posted: 27 Dec 2007, 16:54:03 UTC - in response to Message 50006.  

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.

1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4256_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_15109_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3990_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_25051_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4607_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4333_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4804_0

And in particular, 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0

After it crashed, it was still listed as a running task, still accumulating CPU time but not actually running. It was even listed in the job list as a computation error. Message log:

9:02:00 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
9:02:00 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
9:02:02 AM	[file_xfer] Started upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Finished upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Throughput 29612 bytes/sec
9:09:19 AM	Sending scheduler request: To report completed tasks
9:09:19 AM	Reporting 1 tasks
9:09:24 AM	Scheduler RPC succeeded [server version 601]
9:09:24 AM	Deferring communication for 4 min 2 sec
9:09:24 AM	Reason: requested by project
9:47:51 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
9:47:51 AM	log flags: task, file_xfer, sched_ops
9:47:51 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
9:47:51 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
9:47:51 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
9:47:51 AM	Memory: 1011.04 MB physical, 0 bytes virtual
9:47:51 AM	Disk: 70.87 GB total, 64.30 GB free
9:47:51 AM	URL: https://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
9:47:51 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
9:47:51 AM	Host location: none
9:47:51 AM	General prefs: using your defaults
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:07:57 AM	Aborting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0: exceeded disk limit: 129.67MB > 95.37MB
11:07:57 AM	Deferring communication for 1 min 0 sec
11:07:57 AM	Reason: Unrecoverable error for result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 (Maximum disk usage exceeded)
11:08:02 AM	Computation for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 finished
11:08:02 AM	Output file 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0_0 for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 absent
11:08:03 AM	[error] Process 1936 not found
11:08:26 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
11:08:26 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:43:11 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
11:43:11 AM	log flags: task, file_xfer, sched_ops
11:43:11 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
11:43:11 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
11:43:11 AM	[error] State file error: result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 is in wrong state
11:43:11 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
11:43:11 AM	Memory: 1011.04 MB physical, 0 bytes virtual
11:43:11 AM	Disk: 70.87 GB total, 64.30 GB free
11:43:11 AM	URL: https://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
11:43:11 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
11:43:11 AM	Host location: none
11:43:11 AM	General prefs: using your defaults
11:43:11 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
11:43:12 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0
11:43:12 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0 using rosetta_beta version 591



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.!!!!
ID: 50112 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5573
Credit: 5,565,689
RAC: 916
Message 50113 - Posted: 27 Dec 2007, 18:48:51 UTC - in response to Message 50112.  
Last modified: 27 Dec 2007, 18:52:43 UTC

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.

1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4256_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_15109_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3990_0
1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_25051_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4607_0
1zpy__BOINC_TWIST_RINGS_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_4333_0
1zpy__BOINC_TWIST_RINGS_MORE_SLIDESYMM_FOLD_AND_DOCK-1zpy_-native__2476_4804_0

And in particular, 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0

After it crashed, it was still listed as a running task, still accumulating CPU time but not actually running. It was even listed in the job list as a computation error. Message log:

9:02:00 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
9:02:00 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
9:02:02 AM	[file_xfer] Started upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Finished upload of file 1q9a__BOINC_NO_SRL_TORSION_RNA_ABMIN-1q9a_-_2473_4714_0_0
9:02:38 AM	[file_xfer] Throughput 29612 bytes/sec
9:09:19 AM	Sending scheduler request: To report completed tasks
9:09:19 AM	Reporting 1 tasks
9:09:24 AM	Scheduler RPC succeeded [server version 601]
9:09:24 AM	Deferring communication for 4 min 2 sec
9:09:24 AM	Reason: requested by project
9:47:51 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
9:47:51 AM	log flags: task, file_xfer, sched_ops
9:47:51 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
9:47:51 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
9:47:51 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
9:47:51 AM	Memory: 1011.04 MB physical, 0 bytes virtual
9:47:51 AM	Disk: 70.87 GB total, 64.30 GB free
9:47:51 AM	URL: https://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
9:47:51 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
9:47:51 AM	Host location: none
9:47:51 AM	General prefs: using your defaults
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
9:47:51 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:07:57 AM	Aborting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0: exceeded disk limit: 129.67MB > 95.37MB
11:07:57 AM	Deferring communication for 1 min 0 sec
11:07:57 AM	Reason: Unrecoverable error for result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 (Maximum disk usage exceeded)
11:08:02 AM	Computation for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 finished
11:08:02 AM	Output file 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0_0 for task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 absent
11:08:03 AM	[error] Process 1936 not found
11:08:26 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0
11:08:26 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 using rosetta_beta version 591
11:43:11 AM	Starting BOINC client version 5.8.11 for i686-pc-linux-gnu
11:43:11 AM	log flags: task, file_xfer, sched_ops
11:43:11 AM	Libraries: libcurl/7.16.0 OpenSSL/0.9.8d zlib/1.2.3
11:43:11 AM	Data directory: /home/armada/nodes/armada5/bin/boinc
11:43:11 AM	[error] State file error: result 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_4758_0 is in wrong state
11:43:11 AM	Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
11:43:11 AM	Memory: 1011.04 MB physical, 0 bytes virtual
11:43:11 AM	Disk: 70.87 GB total, 64.30 GB free
11:43:11 AM	URL: https://boinc.bakerlab.org/rosetta/; Computer ID: 404492; location: (none); project prefs: default
11:43:11 AM	General prefs: from rosetta@home (last modified 2007-07-21 12:29:21)
11:43:11 AM	Host location: none
11:43:11 AM	General prefs: using your defaults
11:43:11 AM	Restarting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK-1zpy_-native__2474_3756_0 using rosetta_beta version 591
11:43:12 AM	Starting 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0
11:43:12 AM	Starting task 1zpy__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1zpy_-native__2477_16554_0 using rosetta_beta version 591



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.!!!!


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.
ID: 50113 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile David Emigh
Avatar

Send message
Joined: 13 Mar 06
Posts: 158
Credit: 417,178
RAC: 0
Message 50115 - Posted: 27 Dec 2007, 20:16:40 UTC - in response to Message 50113.  

Major, major flaws in any 1zpy job with TWIST_RINGS {...}



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.!!!!


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.


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!
ID: 50115 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Snags

Send message
Joined: 22 Feb 07
Posts: 198
Credit: 2,682,262
RAC: 340
Message 50120 - Posted: 27 Dec 2007, 20:27:05 UTC
Last modified: 27 Dec 2007, 20:30:02 UTC

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.
ID: 50120 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Yank
Avatar

Send message
Joined: 18 Apr 06
Posts: 71
Credit: 1,752,514
RAC: 0
Message 50122 - Posted: 27 Dec 2007, 20:31:24 UTC

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.

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

Send message
Joined: 18 Apr 06
Posts: 71
Credit: 1,752,514
RAC: 0
Message 50124 - Posted: 27 Dec 2007, 21:08:25 UTC

Just up-dated BOINC program to 5.10.30. Maybe that was the problem?

ID: 50124 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
M.L.

Send message
Joined: 21 Nov 06
Posts: 182
Credit: 180,462
RAC: 0
Message 50125 - Posted: 27 Dec 2007, 23:59:58 UTC
Last modified: 28 Dec 2007, 0:02:05 UTC

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
ID: 50125 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Snags

Send message
Joined: 22 Feb 07
Posts: 198
Credit: 2,682,262
RAC: 340
Message 50126 - Posted: 28 Dec 2007, 3:10:04 UTC - in response to Message 50120.  

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?

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.


update:Completed 2 decoys in 2 attempts in 77911.01 seconds, validated and credit granted. result
ID: 50126 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Conan
Avatar

Send message
Joined: 11 Oct 05
Posts: 148
Credit: 3,290,567
RAC: 558
Message 50127 - Posted: 28 Dec 2007, 7:36:03 UTC

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.
ID: 50127 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5573
Credit: 5,565,689
RAC: 916
Message 50128 - Posted: 28 Dec 2007, 10:30:35 UTC

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.
ID: 50128 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Luuklag

Send message
Joined: 13 Sep 07
Posts: 262
Credit: 4,171
RAC: 0
Message 50129 - Posted: 28 Dec 2007, 11:00:41 UTC

this one errored out after just 16 min.
error
ID: 50129 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Astro
Avatar

Send message
Joined: 2 Oct 05
Posts: 987
Credit: 500,253
RAC: 0
Message 50133 - Posted: 28 Dec 2007, 14:25:36 UTC
Last modified: 28 Dec 2007, 14:50:47 UTC

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.
ID: 50133 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next

Message boards : Number crunching : Problems with version 5.90/5.91



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