Message boards : Number crunching : Minirosetta v1.47 bug thread.
Previous · 1 · 2 · 3 · 4 · 5 · 6 . . . 10 · Next
Author | Message |
---|---|
AMD_is_logical Send message Joined: 20 Dec 05 Posts: 299 Credit: 31,460,681 RAC: 0 |
This WU had a validate error: normal_relax_rlbd_1ynv_IGNORE_THE_REST_DECOY_5565_171_0 It looks from the stderr file like it crunched normally for 16 hours (my current preference) with no error. However, it was then marked "Invalid" with no explanation. The only other thing I see is that it crunched an unusually high number of decoys (8777 decoys). Does that cause problems with the validator? |
![]() ![]() Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0 |
Jay, RE: page faults... If you change the view you can add a column to display the number of faults since the task started. I have long runtimes, but currently have two tasks from Ralph that topped 100,000,000 page faults. One in 15hrs and the other in 19hrs. This is the highest fault rate I've ever seen. Indeed, I recall the days when I thought that 1M per hour of runtime was excessive. The only solice I can offer is that not all faults are hard faults to disk. Some recorded faults are "soft". Perhaps someone else can further elaborate on the concepts. Add this signature to your EMail: Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might! https://boinc.bakerlab.org/rosetta/ |
![]() Send message Joined: 26 Apr 08 Posts: 32 Credit: 429,286 RAC: 0 |
a WU will get to around 85% complete , progress will stay the same. time to completion stays around 10 minutes. i suspend all tasks, resume then the "stuck" WUs will complete. edited: doing this also rolls back the "cpu time spent" to around 30 minutes |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Stephen, this may be part of why you are having problems keeping all 8 CPUs busy. Suggest you just let BOINC manage the machine for the next 12 hours or so. Don't abort, suspend, update, anything at all. Some tasks will take longer then 3 hours to run, and their % complete progress bar will not move steadily. Rather then tell you the task has -30 minutes left, they reflect the situation by making time move very slowly after the task gets to 10 minutes remaining. It's simply a problem with the estimate, not the work being done. Rosetta Moderator: Mod.Sense |
![]() ![]() Send message Joined: 30 May 06 Posts: 5690 Credit: 5,859,226 RAC: 190 |
how do you "lose credit" on a task? on this task i claimed 83 and got 68 for 4 hrs runtime. That is just weird when most of the other work I have been running always comes out on the plus side for granted. |
![]() ![]() Send message Joined: 2 Jul 06 Posts: 2842 Credit: 2,020,043 RAC: 0 |
|
![]() ![]() Send message Joined: 30 May 06 Posts: 5690 Credit: 5,859,226 RAC: 190 |
https://boinc.bakerlab.org/rosetta/result.php?resultid=213832280 you didn't have to reboot your computer a few times during the tasks run did you? that will kill a task. |
![]() ![]() Send message Joined: 2 Jul 06 Posts: 2842 Credit: 2,020,043 RAC: 0 |
yes i did... thanks for that info a Microsoft upgrade required a reboot https://boinc.bakerlab.org/rosetta/result.php?resultid=213832280 |
![]() ![]() Send message Joined: 30 May 06 Posts: 5690 Credit: 5,859,226 RAC: 190 |
heres a tip: before rebooting, because you never know how many times windows will want you to do that when you do a update install, goto the activity tab of boinc manager and put all activity in suspend. wait for your hardrive to stop grinding away with all the saving and then you can reboot. also be sure to have the leave jobs/tasks in memory turned on as well. then you will not lose your position in the task. suspend seems to save everything to the hardrive and you can reboot all you want and not lose any data for the task. yes i did... thanks for that info a Microsoft upgrade required a reboot |
![]() ![]() Send message Joined: 2 Jul 06 Posts: 2842 Credit: 2,020,043 RAC: 0 |
thanks again ...ill do that next time
|
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
I do not agree with greg's comments about preservation of work and reasons why, but would prefer to take them up in another thread if you'd like to discuss further. [edit] We're discussing this under a new thread here. Rosetta Moderator: Mod.Sense |
![]() ![]() Send message Joined: 2 Jul 06 Posts: 2842 Credit: 2,020,043 RAC: 0 |
ok i just want to know what to do I do not agree with greg's comments about preservation of work and reasons why, but would prefer to take them up in another thread if you'd like to discuss further. |
kr12 Send message Joined: 6 Dec 07 Posts: 2 Credit: 85,902 RAC: 0 |
"graphic viewer" hangs with this task cs_noe_fullw_nolin_homo_bench_cs_noe_abrelax_cs_mth1598_olange_5607_11086_0 (https://boinc.bakerlab.org/rosetta/result.php?resultid=215720373) |
stewjack Send message Joined: 23 Apr 06 Posts: 39 Credit: 95,871 RAC: 0 |
"graphic viewer" hangs with this task I had the same thing happen with this similar WU. cs_noe_fullw_nolin_homo_bench_cs_noe_abrelax_cs_nsp1_olange_5608_14752_0 Note: I didn't have time to mess with this one - so I just aborted it. ![]() |
rhb Send message Joined: 19 Jan 07 Posts: 5 Credit: 277,050 RAC: 0 |
I had a computation error. Running Ubuntu Linux 6.06, Boinc 5.4.9. This is the first error I've seen in the last two weeks. https://boinc.bakerlab.org/rosetta/result.php?resultid=215760302 Task ID 215760302 Name cs_noe_fullw_nolin_homo_bench_cs_noe_abrelax_cs_nsp1_olange_5608_24330_0 Workunit 196639962 <core_client_version>5.4.9</core_client_version> <message> process exited with code 193 (0xc1) </message> <stderr_txt> *** glibc detected *** double free or corruption (!prev): 0x0bd2d980 *** SIGABRT: abort called |
P . P . L . Send message Joined: 20 Aug 06 Posts: 581 Credit: 4,865,274 RAC: 0 |
Hi. This one has problems, it's failed twice. https://boinc.bakerlab.org/rosetta/workunit.php?wuid=194507659 <core_client_version>6.2.14</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> SIGSEGV: segmentation violation Stack trace (15 frames): [0x8b979b7] [0x8bc20b0] [0xffffe500] [0x84c0863] [0x85ddf0a] [0x85df32e] [0x85e65b8] [0x819a650] [0x818d3b7] [0x818ee89] [0x8127771] [0x8129a1a] [0x804b9c8] [0x8c1dbac] [0x8048111] Exiting... </stderr_txt> pete. ![]() |
svincent Send message Joined: 30 Dec 05 Posts: 219 Credit: 12,120,035 RAC: 8 |
I'm seeing problems when attempting to show graphics on workunits with names such as cs_noe* on Mac OS X 10.4.11. Its seems like several other people are seeing similar problems. The first time Show graphics is pressed the graphics app starts and displays a blank window. Moving the mouse causes the graphics app to crash. The second and subsequent times Show graphics is pressed the graphics app starts and displays a blank window along with the spinning rainbow beach ball. The graphics app is frozen and you can't even force quit in the normal way: it's necessary to quit via the Activity Monitor. |
lusvladimir Send message Joined: 18 Oct 05 Posts: 12 Credit: 1,784,854 RAC: 0 |
Running Debian Linux , Boinc 6.2.14. https://boinc.bakerlab.org/result.php?resultid=215464278 Task ID 215464278 Name cc_nonideal_1_3_nocst4_hb_t286__IGNORE_THE_REST_1VYHA_6_5693_20_0 Workunit 196380006 <core_client_version>6.2.14</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> # cpu_run_time_pref: 3600 *** glibc detected *** double free or corruption (!prev): 0x0e13a4f0 *** SIGABRT: abort called Stack trace (23 frames): |
NewtonianRefractor Send message Joined: 29 Sep 08 Posts: 19 Credit: 2,350,860 RAC: 0 |
The graphics for one of my Minirosetta 1.47 work units crash. If I click on the show graphics button under boinc, a windows is launched, but it remains black and to close it I have to physically end the unresponsive process. The work unit runs fine though. It's under boinc 6.2.19 |
![]() ![]() Send message Joined: 30 May 06 Posts: 5690 Credit: 5,859,226 RAC: 190 |
two more that wasted my cpu time crashing halfway https://boinc.bakerlab.org/rosetta/result.php?resultid=215547790 t071_1_RDC_NMR_NESG_5480_118996_0 Client state Compute error Exit status -1073741819 (0xc0000005) CPU time 941.5781 -------------- https://boinc.bakerlab.org/rosetta/result.php?resultid=215490731 t072_1_RDC_NMR_NESG_5481_92626_0 Client state Compute error Exit status -1073741819 (0xc0000005) CPU time 12309.66 ----------------------------- |
Message boards :
Number crunching :
Minirosetta v1.47 bug thread.
©2024 University of Washington
https://www.bakerlab.org