Splunk Enterprise

Segfault errors on a search head

TISKAR
Builder

Hello,

We encounter this type of message in the Splunk Serch Head, which causes the restart of the splunk service and the delays at the level of the Splunk web login page, dashbords display.

Have you encountered this type of problem? if so what is it (this type of messag is not clear)?

Splunk Entreprise, Search Head 8.x.x

 

Thank you

[build 545206cc9f70] 2021-08-27 11:21:24
Received fatal signal 11 (Segmentation fault).
Cause:
No memory mapped at address [0x0000000000000008].
Crashing thread: BundleReplicatorThread
Registers:
RIP: [0x00007F5BF348CC24] ? (libjemalloc.so.2 + 0x11C24)


Sep 21 10:13:16 prpgv-splksh01c kernel: [4960554.728167] splunkd[26359]: segfault at 8 ip 00007f2b51845c24 sp 00007f2b279fc868 error 6 in libjemalloc.so.2[7f2b51834000+49000]

 

Labels (2)
Tags (1)
0 Karma

agneticdk
Path Finder

We see the same on a 8.1.4 search head cluster, if you have any info you got from splunk support ?

Or we will try and upgrade first.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Contact Splunk Support for help with that.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...