Message boards : Number crunching : Alas: My first Computing error with a 5.13 WU
Author | Message |
---|---|
Jose Send message Joined: 28 Mar 06 Posts: 820 Credit: 48,297 RAC: 0 |
On a positive note: I was able to process a 5.12 unit ( The type that was going nuts/bonkers for others.) without hassles and with 50 decoys produced. ( It seems my computer is becoming a contrarian :) . ) This and no other is the root from which a Tyrant springs; when he first appears he is a protector.†Plato |
Jose Send message Joined: 28 Mar 06 Posts: 820 Credit: 48,297 RAC: 0 |
Latter edit: After I rebooted my computer the graphic screen corrected itself and restarted processing the unit. I like the way the box opens and closes readjusting itself to the size of the image of molecule shown. This and no other is the root from which a Tyrant springs; when he first appears he is a protector.†Plato |
Jose Send message Joined: 28 Mar 06 Posts: 820 Credit: 48,297 RAC: 0 |
https://boinc.bakerlab.org/rosetta/result.php?resultid=19841226 Interesting error message. (Better talk with my cardiologist LOL LOL LOL ) Name TEST_HOMOLOG_ABRELAX_hom001_1fna__503_338_0 Workunit 16478985 Created 11 May 2006 6:04:26 UTC Sent 11 May 2006 11:15:53 UTC Received 11 May 2006 12:26:51 UTC Server state Over Outcome Client error Client state Computing Exit status -1073741819 (0xc0000005) Report deadline 25 May 2006 11:15:53 UTC CPU time 247.171875 stderr out <core_client_version>5.2.13</core_client_version> <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> # cpu_run_time_pref: 14400 No heartbeat from core client for 31 sec - exiting # random seed: 3526643 # cpu_run_time_pref: 14400 LoadLibraryA( symsrv.dll ): GetLastError = 126 LoadLibraryA( srcsrv.dll ): GetLastError = 126 This and no other is the root from which a Tyrant springs; when he first appears he is a protector.†Plato |
Astro Send message Joined: 2 Oct 05 Posts: 987 Credit: 500,253 RAC: 0 |
welcome back Jose, It appears you still haven't fixed your puter. Overheating and/or bad memory (either ram or video memory) can cause this. tony |
Jose Send message Joined: 28 Mar 06 Posts: 820 Credit: 48,297 RAC: 0 |
Another 5.13 WU went the computing error way: https://boinc.bakerlab.org/rosetta/result.php?resultid=19834989 Result ID 19834989 Name JUMP_ALLBARCODES_ANTIPARALLEL_1tul__SAVE_ALL_OUT_491_48378_0 Workunit 16476688 Created 10 May 2006 21:31:02 UTC Sent 11 May 2006 9:27:13 UTC Received 11 May 2006 12:37:26 UTC Server state Over Outcome Client error Client state Computing Exit status -1073741819 (0xc0000005) Report deadline 25 May 2006 9:27:13 UTC CPU time 104.671875 stderr out <core_client_version>5.2.13</core_client_version> <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> # random seed: 3596603 # cpu_run_time_pref: 14400 </stderr_txt> This is all the information the I got. The program did not provide more information. Argh: Did I speak to fast in my joy of being able to process a 5.12 Unit. Sniff This and no other is the root from which a Tyrant springs; when he first appears he is a protector.†Plato |
Astro Send message Joined: 2 Oct 05 Posts: 987 Credit: 500,253 RAC: 0 |
The "no heartbeat from core" messages indicates loss of communications between the manager and the daemon. This can happen occasionally with little effect, but if it gets frequent then you have an issue. Many will see this message once or twice in the result ID, but it generally doesn't cause a WU to fail. tony |
Jose Send message Joined: 28 Mar 06 Posts: 820 Credit: 48,297 RAC: 0 |
The "no heartbeat from core" messages indicates loss of communications between the manager and the daemon. This can happen occasionally with little effect, but if it gets frequent then you have an issue. Many will see this message once or twice in the result ID, but it generally doesn't cause a WU to fail. Well this is the reason it gave for the failure. I have to admit I found the text the code writer used is funny. (I like funny lines of/in code.) This and no other is the root from which a Tyrant springs; when he first appears he is a protector.†Plato |
FluffyChicken Send message Joined: 1 Nov 05 Posts: 1260 Credit: 369,635 RAC: 0 |
The "no heartbeat from core" messages indicates loss of communications between the manager and the daemon. This can happen occasionally with little effect, but if it gets frequent then you have an issue. Many will see this message once or twice in the result ID, but it generally doesn't cause a WU to fail. Not exactly, these are the error codes [quote]Name TEST_HOMOLOG_ABRELAX_hom001_1fna__503_338_0 Workunit 16478985 Created 11 May 2006 6:04:26 UTC Sent 11 May 2006 11:15:53 UTC Received 11 May 2006 12:26:51 UTC Server state Over Outcome Client error Client state Computing Exit status -1073741819 (0xc0000005) Report deadline 25 May 2006 11:15:53 UTC CPU time 247.171875 stderr out <core_client_version>5.2.13</core_client_version> <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> # cpu_run_time_pref: 14400 No heartbeat from core client for 31 sec - exiting # random seed: 3526643 # cpu_run_time_pref: 14400 LoadLibraryA( symsrv.dll ): GetLastError = 126 LoadLibraryA( srcsrv.dll ): GetLastError = 126 Team mauisun.org |
Message boards :
Number crunching :
Alas: My first Computing error with a 5.13 WU
©2024 University of Washington
https://www.bakerlab.org