Posts by nouqraz

1) Message boards : Number crunching : Problems with version 5.96 (Message 53579) Posted 7 Jun 2008 by nouqraz Post: Woke up this morning to an error message on my screen - rosetta_beta_5.96_windows_intelx86.exe caused an error and needs to close blah blah... This task: http://boinc.bakerlab.org/rosetta/result.php?resultid=169429650 <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> # cpu_run_time_pref: 10800 # random seed: 2005994 Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x00BF05EB read attempt to address 0x0E3AF000 Engaging BOINC Windows Runtime Debugger... .... full debugging info in link to task.
2) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53355) Posted 26 May 2008 by nouqraz Post: Two 1.25 units failed on this host after 12 seconds. http://boinc.bakerlab.org/rosetta/result.php?resultid=166504595 http://boinc.bakerlab.org/rosetta/result.php?resultid=166500492 errors for each look about the same: <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> WARNING: Override of option -out:nstruct sets a different value 9 10000 3 9 1 3 Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x006F8BD0 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... This one failed almost immediately http://boinc.bakerlab.org/rosetta/result.php?resultid=166371066 <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR: in::file::zip minirosetta_database_rev21566.zip does not exist! ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 91 called boinc_finish </stderr_txt> ]]>
3) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53333) Posted 25 May 2008 by nouqraz Post: http://boinc.bakerlab.org/rosetta/result.php?resultid=166371066 <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR: in::file::zip minirosetta_database_rev21566.zip does not exist! ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 91 called boinc_finish </stderr_txt> ]]> looks like this task also failed on the other host(s) it got assigned to.
4) Message boards : Number crunching : minirosetta v1.24 bug thread (Message 53285) Posted 22 May 2008 by nouqraz Post: Adam, can you join our Ralph test project? http://ralph.bakerlab.org With Rom Walton's help, we are reviving the use of the windows symbol store debugging utility on Ralph and hopefully this will give us some information. Okay, I signed up at Ralph, set the host with the problem to work on ralph and suspended rosetta on that host. This is the host on Ralph: http://ralph.bakerlab.org/show_host_detail.php?hostid=13930 This is my account on Ralph: http://ralph.bakerlab.org/show_user.php?userid=4329 --Adam
5) Message boards : Number crunching : minirosetta v1.24 bug thread (Message 53259) Posted 22 May 2008 by nouqraz Post: Just got 4 minirosetta 1.24 WUs on my 4 Xeon (2 dual core chips) machine, and it appears to be doing the same thing that I reported in the 1.19 thread (http://boinc.bakerlab.org/rosetta/forum_thread.php?id=4094&nowrap=true#53225) --- The work units are listed as "running", but no CPU time is used (either as viewed in BOINC or through task manager). I will leave them 'running' for a while and see if they 'wake up'. If they're still hung up tomorrow night I guess I will have to abort them as I have been doing with 1.19 WUs on this machine. Thanks, Adam
6) Message boards : Number crunching : minirosetta v1.19 bug thread (Message 53225) Posted 21 May 2008 by nouqraz Post: One of my systems seems to be having issues runing minirosetta v1.19 WUs. It is a 4 processor Intel Xeon CPU X3210 (two dual core chips) running server 2003 R2. It seems to be crunching through Rosetta Beta 5.96 WUs no problem, but when it goes to start a mini 1.19 WU, it switches the task to "running" but CPU time is ever used and the task stays at 0%. If I suspend all of the mini 1.19 WUs that are queued up the system immediately begins crunching on any Rosetta Beta 5.96 WUs without any problem. I have left the system sitting in the "running" @ 0% state on mini units for hours and it hasn't gotten anywhere, my only option seems to be to suspend or abort the work units. I have two other machines - one an Intel P4, the other a Core 2 Quad 9300, both running XP - that seem to have no problems running mini or beta WUs. Is it possible to get the client to not receive mini WUs? Or is there some known reason behind these stalled work units that there is a workaround for? Thanks, Adam