| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Human Proteome Folding - Phase 2
Thread: Signal 11 for all HPF2 WU's on Linux box |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am currently receiving the following error on a 64-bit Ubuntu box for all HPF2 WU's.
----------------------------------------<core_client_version>6.12.33</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> </stderr_txt> ]]> This box was running HPF2 WU's fine a couple of weeks ago, before I switched over to CFSW. Since CFSW is currently suspended, I switched back to HPF2 and now I am receiving the above Error on every HPF2 WU on that box. Sometimes it happens immediately, sometimes after 2.5 to 3 hours. I have aborted all of the remaining HPF2 WU's on that box, since there's no point crunching 2.5 to 3 hours for nothing. For what it's worth -- I was also running GFAM and CEP2 WU's on the same box at the same time. [Edit 1 times, last edit by Former Member at Aug 26, 2012 11:33:42 PM] |
||
|
|
wplachy
Senior Cruncher Joined: Sep 4, 2007 Post Count: 423 Status: Offline |
BOINC FAQs on Signal 11 error suggest it may be a memory/disk error or running 32bit app on 64bit OS without 32 bit libs. I also found a few references to network connection errors. Given HPF2 was running before it's probably not a 32/64bit issue. When HPF2 was running OK were you also running CEP and GFAM at the same time?
----------------------------------------
Bill P
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I was running CEP2 before, but not GFAM.
|
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
Bad network connections (particularly wireless) are notorious for crashing out work with signal 11 on Linux. The error comes from the system being overtaxed whether from searching for a network or excessive memory useage. Unfortunately, it's one of those catch-all errors and difficult to track down if not something other people have commonly experienced.
---------------------------------------- Distributed computing volunteer since September 27, 2000 |
||
|
|
|