Splunk Enterprise

Segmentation fault crash log on Indexer

delgendy
Explorer

I have multiple crashes on my VM Linux servers "SUSE 12" that are running Splunk service in a cluster, mainly what is crashing are indexers and Search heads. We had different causes from the crash logs under Splunk which is Segmentation Fault and also on the var/log messages we see logs for crashes with a Segmentation fault. What can be monitored on the Server OS level to identify the root cause of the issue like what resources should be monitored to triage these crashes?

Tags (1)
0 Karma

codebuilder
Influencer

That means Splunk is consuming more memory than it is allowed by the OS, or it is exhausting all of the system memory and/or SWAP.

Ensure that ulimits are set correctly for your system:
https://docs.splunk.com/Documentation/Splunk/8.0.2/Installation/SystemRequirements#Considerations_re...

Increase the memory on your VM's or increase the size of your cluster, or decrease the workload.

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma

codebuilder
Influencer

If you found the suggestions to help, please "accept" the answer so that the community can benefit.

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma
Get Updates on the Splunk Community!

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...

Updated Data Management and AWS GDI Inventory in Splunk Observability

We’re making some changes to Data Management and Infrastructure Inventory for AWS. The Data Management page, ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...