| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Computation Errors |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Norwich Gadfly,
The first nothing can be done... we have to live with line:711 as not lab reproducible. The Second, don't know how your AV/Firewall settings are but make sure to exclude the BOINC Data_dir (path printed at start of BOINC message log). Also if you have stray errors, a soft reboot always helps to clean up memory, no matter what OS. Also, running cache empty and then doing a project reset will pull a complete new set of science applications with all settings / permissions / bits refreshed. Conflicts during execution (false positve /heuristic aggressive scanning by AVs is not unknown, hence the exclusion to scan the data_dir. BOINC is a sand-boxed environment, particularly if installed as service. When there is an error, always visit the Result Status page and click on the work unit name so quorum can be seen and outcome of wingman. Many times, if the wingman succeeds, the pointers more strongly are towards a client issue rather than a science app or work unit. ttyl |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The Second, don't know how your AV/Firewall settings are but make sure to exclude the BOINC Data_dir (path printed at start of BOINC message log). Also if you have stray errors, a soft reboot always helps to clean up memory, no matter what OS. Also, running cache empty and then doing a project reset will pull a complete new set of science applications with all settings / permissions / bits refreshed. Conflicts during execution (false positve /heuristic aggressive scanning by AVs is not unknown, hence the exclusion to scan the data_dir. BOINC is a sand-boxed environment, particularly if installed as service. The second one is probably related to the Signature Update (i.e. science app updates from v.6.X to v.6.40) issue (happens when a WU was being crunched using the old version and suddenly (after rebooting the machine, for example) the science app was replaced by the new version before the WU was finished; also nothing could be done). [Edit 1 times, last edit by Former Member at Mar 14, 2011 5:31:25 AM] |
||
|
|
|