| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project - Phase 2 Forum
Thread: Output file absent error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: 
|
I wonder if others have come across this before.:
----------------------------------------Output file E.... for task E..... absent. Seems related to ssd/hdd at a guess but I suppose it could be something in memory. The odd thing is that no matter how many CEP2 jobs are running they all fail at once. (but anything else keeps running) Something with TRIM maybe? Linux mint 64, 16c 32t rig 32GB ram and not more than 24 CEP2 still fails. system shows max 7GB mem in use and 1/3rd of ssd in use. I can put a clean install on this SSD or on a HDD but I wonder if anyone knows something about why this is?  [Edit 1 times, last edit by OldChap at Jul 18, 2013 12:05:27 AM] |
||
|
|
captainjack
Advanced Cruncher Joined: Apr 14, 2008 Post Count: 140 Status: Offline Project Badges: 
|
Hey OldChap,
I got some of those earlier today too. Happened when there was a network glitch and BOINC lost touch with WCG. If you look in the result log for one of the tasks that bombed, see if it says something about "process got signal 11". That is one of the unique attributes of Linux. It gets those signal 11 errors from time to time and causes tasks to abort. Sometimes it happens when the CPU gets really busy and BOINC stalls. You can search the forums for "signal+11" and find numerous other threads with some recommended settings to try to reduce the number of times you get the signal 11 in Linux. Hope that helps. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7219 Status: Offline Project Badges:
|
I have experienced the CEP2 failures on Linux Mint 64 also, so I just don't even run them on my Linux machines. Some of them were signal 11 errors which seems to mean the machine is too busy, but they only seemed to occur when communication(wireless) became unavailable. There were different errors also, but Cep2 was problematic on all the the Linux machines which were all using the same wireless extender. No problem with the windows machines. This may or may not be related to your problem, but I just don't know. Good luck with a resolution.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
|