| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Error, although Result Log reports successful completion |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
rkar22
Cruncher Joined: Nov 17, 2004 Post Count: 48 Status: Offline Project Badges: 
|
Two jobs errored out recently on my EEE-PC
 . For the first one, two repair units were sent out - the first one ended Inconclusive, the second one completed successfully, so finally both ended up as Valid:faah5383_ 004189_ MC_ xmdEq_ 1HSI_ 09_ 2-- Valid 09-03-16 04:16:19 09-03-16 15:59:52 3.68 71.0 / 79.7 faah5383_ 004189_ MC_ xmdEq_ 1HSI_ 09_ 1-- Valid 09-03-15 07:47:09 09-03-16 04:11:21 7.32 88.4 / 79.7 faah5383_ 004189_ MC_ xmdEq_ 1HSI_ 09_ 0-- Error 09-03-13 14:20:21 09-03-15 07:40:40 27.12 114.4 / 0.0 I took a closer look at the result logs; the first wingman's one and mine differ in the client version (5.10.30 and 6.2.28 respectively), but look pretty much the same otherwise, except for some extra lines somewhere in the middle of mine: ... Finished Docking number 5 Failed to get VersionInfo size: 1812 Restoring grahics. bestEnergy: -13.028400 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-0.02 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 6) Finished Docking number 6 ... In the second wingman's result log (client version 5.8.16) this extra block occurs 11 times, with some debugging info between the first and the second block: ... Finished Docking number 7 Failed to get VersionInfo size: 1812 Restoring grahics. bestEnergy: -13.028400 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-0.02 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 8) Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x0047EDDF read attempt to address 0x0539C000 Engaging BOINC Windows Runtime Debugger... ******************** BOINC Windows Runtime Debugger Version 6.3.3 Dump Timestamp : 03/16/09 21:21:19 Install Directory : C:\Program Files\BOINC\ Data Directory : C:\Program Files\BOINC Project Symstore : Loaded Library : C:\Program Files\BOINC\\dbghelp.dll Loaded Library : C:\Program Files\BOINC\\symsrv.dll Loaded Library : C:\Program Files\BOINC\\srcsrv.dll LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126 Loaded Library : version.dll Failed to get VersionInfo size: 1812 Restoring grahics. bestEnergy: -13.028400 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-0.02 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 8) Failed to get VersionInfo size: 1812 Restoring grahics. bestEnergy: -13.028400 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... ... So what made the difference between success and failure here? The last sections of all three result logs look identical and seem to indicate successful completion: ... Finished Docking number 10 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[23:23:11] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[23:23:40] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 11) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ called boinc_finish </stderr_txt> ]]> It may be of interest that at the same time this result was returned an HFCC job returned an error with exactly the same symptoms (result log indicating successful completion, but containing those few extra lines quoted at the beginning of this post). My second FAAH job errored out about 10 hours ago: faah5389_ 005667_ MC_ xmdEq_ 2AZ8_ 03_ 1-- In Progress 09-03-18 00:07:20 09-03-20 23:24:08 0.00 0.0 / 0.0 faah5389_ 005667_ MC_ xmdEq_ 2AZ8_ 03_ 0-- Error 09-03-14 06:38:29 09-03-18 00:01:18 30.04 122.9 / 0.0 Its result log looks exactly like a successful job's one, with no extra lines of information. Will have to wait for the rescue unit to complete, to be able to compare result logs,but then ... Do the result logs contain any useful information to explain this issue? Any helpful hints appreciated. Robert |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The only real error from what I know that is seen in all of the presented is
----------------------------------------Reason: Access Violation (0xc0000005) at address 0x0047EDDF read attempt to address 0x0539C000 The Inconclusive is a result from the first validation attempt of 2 results, 1 marked error, the other inconclusive, which then required the 3rd to be send out, the top of the 3 in the list. After that got back, 2-- and 1-- were validated. FAAH was just switched to heavy work: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=24803 faah5383 and faah5389 are not part of these, thus not sure why you have now these errors popping up. Finish the results you have and start with a project reset and a boot. Later do some system diagnostics.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
rkar22
Cruncher Joined: Nov 17, 2004 Post Count: 48 Status: Offline Project Badges:
|
Thank you for your answer.
The only real error from what I know that is seen in all of the presented is Reason: Access Violation (0xc0000005) at address 0x0047EDDF read attempt to address 0x0539C000 It seems a bit strange to me that this only real error occured in the result log of faah5383_ 004189_ MC_ xmdEq_ 1HSI_ 09_ 2-- which finally made this WU validate while my errored out faah5383_ 004189_ MC_ xmdEq_ 1HSI_ 09_ 0-- ended up with an apparently error free result log. FAAH was just switched to heavy work: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=24803 faah5383 and faah5389 are not part of these, thus not sure why you have now these errors popping up. Finish the results you have and start with a project reset and a boot. Later do some system diagnostics. Seems the only logical way to proceed in this situation. Thanks again, Robert |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi rkar22,
'Access Violation (0xc0000005)' is a bad error. The result with that should not be Valid. The 2 results without it have a good chance of being Valid. I know that you say that the result with this error was marked Valid, but I think that either you are misreading the Results Status page or you have discovered a bug in the Results Status page software. Could you please double-check this? Lawrence |
||
|
|
|