Skip to main content
NetApp Knowledge Base

Slice service crashes with signal SIGSEGV Segmentation fault

Last Updated:

Applies to

Element OS 12.5


Slice service crashes with signal SIGSEGV, Segmentation fault
  • Crash dump
GNU gdb (Gentoo 9.2 vanilla) 9.2
Reading symbols from /sf/bin/sfapp...
Reading symbols from /sf/bin/sfapp.debug...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/".
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `sfapp -service=slice -serviceid=ID# -vserviceid=ID# -tserviceid=ID# -noruninproces'.
Program terminated with signal SIGSEGV, Segmentation fault.
  • Kernel.log
2022-08-27T17:23:49.386992Z node_name kernel: [2700569.480857] libmicro httpd[162826]: segfault at 1d8 ip 00007f754788b8c0 sp 00007f5a626e7158 error 4 in[7f7547885000+10000]
2022-08-27T17:23:49.386999Z node_name kernel: [2700569.480864] Code: 06 8b 56 04 89 47 30 31 c0 85 d2 0f 95 c0 89 47 1c 31 c0 c3 66 0f 1f 44 00 00 31 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 <8b> 57 18 64 8b 04 25 d0 02 00 00 39 c2 0f 84 65 01 00 00 41 57 41

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.