Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 
World Community Grid Forums
  Category: Active Research
  Forum: Africa Rainfall Project
  Thread: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 31
Posts: 31   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 9087 times and has 30 replies Next Thread
Crystal Pellet
Veteran Cruncher
Joined: May 21, 2008
Post Count: 1403
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Unexpected error task ARP1_0034023_089. 5 replications and 3 errors so far.
My error task ARP1_0034023_089_3 https://www.worldcommunitygrid.org/contribution/results/1987115908/log
Could be related to SIGSEGV, cause it's also failing to access memory.
RAM is OK and enough (64GB).
[Oct 23, 2021 8:06:40 AM]   Link   Report threatening or abusive post: please login first  Go to top 
alanb1951
Veteran Cruncher
Joined: Jan 20, 2006
Post Count: 1317
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
There's another one out there too -- ARP1_0033560_098, of which I got the final retry!

All the returned tasks had the SIGSEGV error after two checkpoints, and identical stack traces (as per usual...), so I've not bothered showing the stderr report(s) :-)

I tend to abort any of these that show up with two or more identical SIGSEGV returns, but I missed this one's arrival; fortunately it failed relatively early...

Cheers - Al.

[Edit - forgot to mention that this was on Linux...]
----------------------------------------
[Edit 1 times, last edit by alanb1951 at Oct 23, 2021 12:17:50 PM]
[Oct 23, 2021 12:15:49 PM]   Link   Report threatening or abusive post: please login first  Go to top 
MJH333
Senior Cruncher
England
Joined: Apr 3, 2021
Post Count: 300
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Al,

Earlier in this thread you were asking about whether this issue was arising on Windows machines. I thought you might find this interesting:
https://www.worldcommunitygrid.org/contribution/workunit/854352096

Three tasks were sent to Windows machines, which all errored out. The next three wingmen were Linux machines (mine was _4), which all gave the SIGSEGV error.

The Windows machines all gave "Unhandled Exception Detected" errors. These error logs don't seem to mention SIGSEGV.

I have no technical background, so I'm afraid that none of these errors means anything to me!

Cheers,
Mark
[Oct 23, 2021 12:50:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
nyanthiss
Cruncher
Joined: Nov 23, 2012
Post Count: 15
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
I had more than a dozen tasks this week, all with this exact error.

What happened in my case: i was testing BOINC in a new OS installation on my machine. I noticed that i got a mix of x86-64 and i686 tasks. I put the i686 ones on suspend, let the x86-64 finish, then turned off BOINC, and added the no-alt-platform tag into cc_config.xml, and started BOINC again. It looked at i686 tasks, decided that i686 is not a "valid" platform anymore, and tried to run the same tasks with the x86-64 binary (AFAICT):

App version has unsupported platform i686-pc-linux-gnu; changing to x86_64-pc-linux-gnu


... all of them ended with segfault and the same backtrace.
----------------------------------------
Intel Xeon E3-1231 v3
AMD A10 7800
AMD Ryzen 5 3500U
AMD Ryzen 1700X
AMD Ryzen 5900X
2x RaspberryPi, 1x Odroid
[Oct 23, 2021 1:30:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
alanb1951
Veteran Cruncher
Joined: Jan 20, 2006
Post Count: 1317
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Al,

Earlier in this thread you were asking about whether this issue was arising on Windows machines. I thought you might find this interesting:
https://www.worldcommunitygrid.org/contribution/workunit/854352096

Three tasks were sent to Windows machines, which all errored out. The next three wingmen were Linux machines (mine was _4), which all gave the SIGSEGV error.

The Windows machines all gave "Unhandled Exception Detected" errors. These error logs don't seem to mention SIGSEGV.

I have no technical background, so I'm afraid that none of these errors means anything to me!

Cheers,
Mark

Thanks, Mark -- it's good to have a cross-platform confirmation that, whatever the fault is, it seems to bite both platforms in exactly the same way and, presumably, at exactly the same stage of execution; after all, these all ran on the same data (presumably!). Hopefully the technicians can do something with that information...

As an ex "systems/technical programmer" I'd be fascinated to have the symbol tables and source code to look at - however, I can only dream (and hope that if/when the issue is found we get to hear what it was!...)

As for SIGSEGV - that's just the Unix/Linux signal name for "Segmentation Violation", so it's exactly the same sort of thing as "Access Violation (0xc0000005)" on Windows.

By the way, if anyone's noting task names, this one was ARP1_0033871_089

Cheers - Al.

P.S. It would be interesting to know whether the drop-off in available work units at present is a coincidence or the result of shutting things down briefly to look into these error tasks...

[Edit - "normal service" was restored round about when I posted this!!!]
----------------------------------------
[Edit 1 times, last edit by alanb1951 at Oct 23, 2021 4:04:55 PM]
[Oct 23, 2021 3:24:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
MJH333
Senior Cruncher
England
Joined: Apr 3, 2021
Post Count: 300
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
As for SIGSEGV - that's just the Unix/Linux signal name for "Segmentation Violation", so it's exactly the same sort of thing as "Access Violation (0xc0000005)" on Windows.

Al,
Many thanks for the explanation. I learn something every time I visit this forum!

Cheers,
Mark
[Oct 23, 2021 5:21:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
In addition to my earlier posting, I also noticed that a copy of task ARP1_0034171_090_4 was resent (as ARP1_0034171_090_5)
to the same device(name) again:

workunit 855488444
Details:
(snip, snip, snip)
ARP1_0034171_090_1  Linux Ubuntu  Error      2021-10-22T20:12:05  2021-10-23T06:57:03    0.00/0.00       0.0/0.0   
	Devicename: ITXMint
ARP1_0034171_090_2  Linux Pop     Error      2021-10-22T22:34:21  2021-10-22T22:36:48    0.00/0.00       0.0/0.0   
	Devicename: aorus-b550
ARP1_0034171_090_3  Linux Debian  Error      2021-10-22T22:38:46  2021-10-23T00:57:42    0.00/0.00       0.1/0.0   
	Devicename: boinc-epycinstance-2
ARP1_0034171_090_4  Linux         Error      2021-10-23T01:00:03  2021-10-23T01:03:07    0.00/0.00       0.1/0.0   
	Devicename: WCG-10-5-173-151
ARP1_0034171_090_5  Linux         Error      2021-10-23T01:05:02  2021-10-23T01:07:41    0.00/0.00       0.0/0.0   
	Devicename: WCG-10-5-173-151

In my opinion, this should not be happening and must be prevented.
----------------------------------------
[Edit 1 times, last edit by adriverhoef at Oct 24, 2021 12:42:59 PM]
[Oct 24, 2021 12:42:04 PM]   Link   Report threatening or abusive post: please login first  Go to top 
MJH333
Senior Cruncher
England
Joined: Apr 3, 2021
Post Count: 300
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Adri,
Do you think this problem is getting worse? I’ve had three of these errors since yesterday, two on Windows and one on Linux. They were ARP1_0034390_091, ARP1_0034098_090 and ARP1_0033792_094 respectively.
Cheers,
Mark
[Oct 26, 2021 8:26:46 AM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Adri,
Do you think this problem is getting worse? I’ve had three of these errors since yesterday, two on Windows and one on Linux. They were ARP1_0034390_091, ARP1_0034098_090 and ARP1_0033792_094 respectively.
Cheers,
Mark

Well, as long as they crash within minutes after starting... it isn't that bad. wink
Personally I've seen only three thus far (in the past week); two a few days ago, the third one this past night:
workunit 858963625
Details:
ARP1_0033794_093_0  Linux Ubuntu  Error      2021-10-26T00:30:05  2021-10-26T04:00:06    0.00/0.00       0.1/0.0   
	OS-Version: Ubuntu 20.04.3 LTS [5.11.0-38-generic|libc 2.31 (Ubuntu GLIBC 2.31-0ubuntu9.2)]
ARP1_0033794_093_1  Linux         Error      2021-10-26T00:30:02  2021-10-26T00:32:16    0.00/0.00       0.1/0.0   
	OS-Version: 4.4.0-62-generic
	Devicename: WCG-10-5-173-151
ARP1_0033794_093_2  Linux Fedora  Error      2021-10-26T00:34:09  2021-10-26T00:55:24    0.00/0.00       0.0/0.0   
	OS-Version: Fedora 34 (Xfce) [5.13.16-200.fc34.x86_64|libc 2.33 (GNU libc)]
ARP1_0033794_093_3  Linux Debian  Error      2021-10-26T00:55:54  2021-10-26T02:04:16    0.00/0.00       0.1/0.0   
	OS-Version: Debian GNU/Linux 10 (buster) [4.19.0-17-amd64|libc 2.28 (Debian GLIBC 2.28-10)]
ARP1_0033794_093_4  Linux         Error      2021-10-26T02:05:06  2021-10-26T02:07:49    0.00/0.00       0.0/0.0   
	OS-Version: 4.4.0-62-generic
	Devicename: WCG-10-5-173-149
ARP1_0033794_093_5  Linux Ubuntu  Error      2021-10-26T02:09:14  2021-10-26T04:09:53    0.00/0.00     502.8/0.0   
	OS-Version: Ubuntu 20.04.2 LTS [5.10.28-Unraid|libc 2.31 (Ubuntu GLIBC 2.31-0ubuntu9.2)]

At least they weren't resent to the same machine. blushing
----------------------------------------
[Edit 2 times, last edit by adriverhoef at Oct 26, 2021 1:52:13 PM]
[Oct 26, 2021 9:25:07 AM]   Link   Report threatening or abusive post: please login first  Go to top 
MJH333
Senior Cruncher
England
Joined: Apr 3, 2021
Post Count: 300
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Error: SIGSEGV: segmentation violation, process exited with code 193 (0xc1, -63)
Thanks, Adri. Probably just a coincidence that I’ve had quite a few of these errors in a short space of time.
Cheers,
Mark
[Oct 26, 2021 12:56:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 31   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread