| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My Ubu-64bit-machine have been getting a lot of exit 193 error in the resultsStatus log and an "output file <x> absent" error message in the BOINC_V7.0.28 eventLog for HFCC and HCC WUs. I'm trying to track down the cause. I've not done any changes to the machine fresh off crunching CFSW-WUs to near perfection (rare invalids and zero errors to my recollection) so the sudden 180-degree turn of events was a bit surprising...
![]() ; |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello andzgrid,
I thought 193 sounded familiar, but when I searched for 3 months back, then for 6 months, I didn't come up with any posts. That sounds like a problem with your system or with BOINC 7.0.28. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello Lawrence.
I finally tracked down the issue: a problem with my Ubu-64-bit-machine system, alright -- from too high an overclock. What intrigues me is that the machine had the same overclock settings when it crunched CFSW-WUs to near perfection. My three(3)-curiosities as to why that might be: 1] HFCC and HCC require more precise computations while CFSW is a little more forgiving? 2] The electronics of the machine may have been 'polarized' from weeks of 24/7 overclock of nothing but CFSW that any other code execution from any other project's WUs would have failed equally? 3] It just happened that the dust build-up inside the machine reached critical levels at exactly the time that I went for HFCC / HCC WUs? Anyways, I did some cleaning, re-checked and re-seated hardware components, and toned down the overclock a bit. Result: no more errors and I'm a happy camper once again. ![]() ; |
||
|
|
|