| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Lots of Error results |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think the past 2 days all work units I finished results in "Computation Error" and the Results Status page lists them with "Error" status. The content of the error messages is cryptic and not helpful at all.
What is going on? Please tell me what information is needed to get to the source of this. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Start by posting a 'cryptic' result log and a piece of the client message log that shows some results ending in computation error.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
<core_client_version>6.2.28</core_client_version> <![CDATA[ <stderr_txt> Failed to get VersionInfo size: 1812 INFO:[13:53:43] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[13:54:00] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 0) _maxGenSeenSoFar changed: 2500 _maxGenSeenSoFar changed: 2626 _maxGenSeenSoFar changed: 2758 _maxGenSeenSoFar changed: 2896 _maxGenSeenSoFar changed: 3041 _maxGenSeenSoFar changed: 3194 _maxGenSeenSoFar changed: 3354 _maxGenSeenSoFar changed: 3522 _maxGenSeenSoFar changed: 3699 _maxGenSeenSoFar changed: 3885 _maxGenSeenSoFar changed: 4080 _maxGenSeenSoFar changed: 4285 _maxGenSeenSoFar changed: 4500 _maxGenSeenSoFar changed: 4726 _maxGenSeenSoFar changed: 4963 _maxGenSeenSoFar changed: 5212 _maxGenSeenSoFar changed: 5473 _maxGenSeenSoFar changed: 5747 _maxGenSeenSoFar changed: 6035 _maxGenSeenSoFar changed: 6337 _maxGenSeenSoFar changed: 6654 _maxGenSeenSoFar changed: 6987 _maxGenSeenSoFar changed: 7337 _maxGenSeenSoFar changed: 7704 _maxGenSeenSoFar changed: 8090 _maxGenSeenSoFar changed: 8495 _maxGenSeenSoFar changed: 8920 _maxGenSeenSoFar changed: 9367 _maxGenSeenSoFar changed: 9836 _maxGenSeenSoFar changed: 10328 Updating Best Energy for WU: 0.00 Finished Docking number 0 Finished Docking number 1 Updating Best Energy for WU: -8.67 Finished Docking number 2 Finished Docking number 3 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Finished Docking number 8 Failed to get VersionInfo size: 1812 Restoring grahics. bestEnergy: -9.212010 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 9) Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Finished Docking number 16 Finished Docking number 17 Finished Docking number 18 Finished Docking number 19 Finished Docking number 20 Finished Docking number 21 Finished Docking number 22 Finished Docking number 23 Finished Docking number 24 Finished Docking number 25 Finished Docking number 26 Finished Docking number 27 Finished Docking number 28 Finished Docking number 29 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[18:38:21] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[18:38:52] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 30) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ called boinc_finish </stderr_txt> <message> <file_xfer_error> <file_name>HFCC_t1_00483138_TrkB_0003_0_0</file_name> <error_code>-108</error_code> </file_xfer_error> <file_xfer_error> <file_name>HFCC_t1_00483138_TrkB_0003_0_1</file_name> <error_code>-108</error_code> </file_xfer_error> <file_xfer_error> <file_name>HFCC_t1_00483138_TrkB_0003_0_2</file_name> <error_code>-108</error_code> </file_xfer_error> <file_xfer_error> <file_name>HFCC_t1_00483138_TrkB_0003_0_3</file_name> <error_code>-108</error_code> </file_xfer_error> </message> ]]> The errors for the other projects are similar and have the -108 error code in common (as far as I checked). I don't think any messages in the Messages tab of BOINC relate to any of the tasks that resulted in Computation Errors and I don't know of any other log location. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Did you do anything to the permissions? The error is described in a wiki as:
----------------------------------------http://boincfaq.mundayweb.com/index.php?language=1&view=71 ERR_FOPEN -108 1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC directory and its sub directories. Then BOINC can't find where it is running from. Solution: Do not hide your BOINC directory. 2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file. Solution: Exit BOINC completely and restart it. 3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it). Solution: Restart your computer. 4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC directory/subdirectories. The directories their read-only attributes are set. Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC directory and subdirectories.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I didn't manipulate the permissions.
Thanks for the wiki link. I restarted BOINC now and one of the work units will finish shortly. Let's see if that helped. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Still getting Computation Error. The messages tab simply states:
2009-05-04 23:13:34|World Community Grid|Restarting task HFCC_t1_00481262_TrkB_0000_0 using hfcc version 610 2009-05-04 23:26:49|World Community Grid|Computation for task HFCC_t1_00481262_TrkB_0000_0 finished |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just double-checked the attributes on "C:\Documents and Settings\All Users\Application Data\BOINC" and the read-only box was in intermediate state. So some files were actually read-only.
I just don't see why they would be. BOINC has been running fine for days before the problem occurred. And also it was able to download new work units to the same folder in the first place. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Even after removing the read-only attribute on the folder the problem remains.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think the first thing you try should be resetting the project. Open BOINC Manager, go to the Projects tab, select World Community Grid and click "Reset".
If this fails, you will need to reinstall. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks, I just reset it. Let's see how the new work units will end.
|
||
|
|
|