Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Help Stop TB Thread: Error 193 |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 13
|
Author |
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1671 Status: Offline Project Badges: |
Yesterday, two errored WUs with Error code 193: SIGSEGV: segmentation violation.
----------------------------------------- HST1_ 005095_ 000049_ KC0003_ T400_ F00044_ S00006_ 1-- after 5.6 hours - HST1_ 005096_ 000011_ KC0006_ T400_ F00092_ S00006_ 1-- after 0.41 hours In the both cases, there was enough free memory available. Cheers, Yve |
||
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: |
Looks like the other copies finished so it is not a workunit issue. Let me know if you have any other issues.
Thanks, armstrdj |
||
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1671 Status: Offline Project Badges: |
Hi armstrdj,
----------------------------------------the hosts are working fine again since the reboot after the WUs crashed. Since the hosts are more or less only crunching for WCG, I cannot really understand the reason for such a failure: no OC, enough free RAM, no high temperature, no collision with other applications ? ... Cheers, Yves |
||
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 259 Status: Offline Project Badges: |
Linux 64-bit - Several errors here like this :-
----------------------------------------Result Name: HST1_ 005492_ 000077_ KC0010_ T350_ F00062_ S00007_ 2-- <core_client_version>7.7.0</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> INFO: result number = 2 INFO: No state to restore. Start from the beginning. [10:33:16] INFO: Running initial simulation SIGSEGV: segmentation violation Stack trace (5 frames): [0x9a8f521] [0xf7775400] [0x9b46f6d] [0x830e241] [0x756f6e65] Exiting... </stderr_txt> ]]> Also run dry with HST1 and now running FAH2
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Core client 7.7.0? Self build maybe from latest code?
|
||
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 259 Status: Offline Project Badges: |
Yes - about one year ago...
----------------------------------------https://secure.worldcommunitygrid.org/forums/...ead,38190_offset,0#496917 First time I have seen a problem running this build... switched to FAH2 OK.
Run Time Stats https://grassmere-productions.no-ip.biz/
----------------------------------------[Edit 2 times, last edit by TonyEllis at Jul 18, 2016 9:37:06 AM] |
||
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Ah yes, https://secure.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=496917 (1 year ago in my slow lane :)
----------------------------------------There's more than a few problems with HST1 at this time [hardly a client issue], but I'd suggest you get yourself onto 7.6 version like 7.6.33 (RC), as that 7.7.0 will be very very very early alpha code. I'm using FKA as LocutusofBorg ppa for easy install of latest. ppa:costamagnagianfranco/boinc which is at 7.6.32 [Edit 1 times, last edit by SekeRob* at Jul 18, 2016 8:41:02 AM] |
||
|
pvh513
Senior Cruncher Joined: Feb 26, 2011 Post Count: 260 Status: Offline Project Badges: |
Looks like the other copies finished so it is not a workunit issue. Let me know if you have any other issues. The same problem is also discussed in the thread "Lots of errors on this project recently...". Others are seeing the segfault problem as well and the problem is mirrored by the wingmen in those cases. Here are some WUs HST1_ 005585_ 000005_ AT0016_ T325_ F00029_ S00007_ 0-- HST1_ 005582_ 000065_ KT0011_ T300_ F00065_ S00003_ 0-- HST1_ 005538_ 000022_ KT0010_ T400_ F00036_ S00003_ 0-- HST1_ 005538_ 000055_ KT0010_ T400_ F00069_ S00003_ 1-- HST1_ 005538_ 000074_ KT0010_ T400_ F00088_ S00003_ 1-- HST1_ 005538_ 000068_ KT0010_ T400_ F00082_ S00003_ 0-- HST1_ 005538_ 000039_ KT0010_ T400_ F00053_ S00003_ 0-- HST1_ 005538_ 000058_ KT0010_ T400_ F00072_ S00003_ 0-- HST1_ 005623_ 000049_ KT0004_ T300_ F00070_ S00003_ 0-- HST1_ 005623_ 000040_ KT0004_ T300_ F00061_ S00003_ 0-- HST1_ 005623_ 000045_ KT0004_ T300_ F00066_ S00003_ 1-- HST1_ 005583_ 000004_ KT0013_ T300_ F00004_ S00003_ 1-- HST1_ 005617_ 000077_ AC0022_ T300_ F00074_ S00007_ 1-- HST1_ 005555_ 000028_ AC0025_ T350_ F00023_ S00007_ 1-- HST1_ 005544_ 000004_ AC0001_ T300_ F00105_ S00006_ 0-- HST1_ 005544_ 000071_ AC0001_ T300_ F00526_ S00007_ 0-- HST1_ 005522_ 000033_ AC0026_ T325_ F00057_ S00006_ 1-- HST1_ 005492_ 000081_ KC0010_ T350_ F00066_ S00007_ 0-- |
||
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1671 Status: Offline Project Badges: |
With the yesterday "wave" of HST1 WUs, again two fault WUs with Error 193:
----------------------------------------- HST1_ 005623_ 000089_ KT0010_ T350_ F00010_ S00003_ 3-- after 12 hours - HST1_ 005625_ 000085_ KT0019_ T350_ F00006_ S00003_ 2-- after 13.7 hours Cheers, Yves |
||
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1671 Status: Offline Project Badges: |
Hi TechTeam,
----------------------------------------I've just noticed that the credits have been finally granted even the errorred status. By the way, I noticed as well that the same WU has been distributed simultaneously to Linux and Windows hosts. Until now, I assumed that some segregation was in place for avoiding that a WU is distributed to different computation environments. Cheers, Yves |
||
|
|