Splunkd in Universal Forwarder is crashing due to a Segmentation fault.

Available Languages

Updated:September 29, 2026

Document ID:SPLK046481

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Universal Forwarder Splunk Enterprise

Description

When splunkd process is stopping frequently.

Investigation

As per crash files:

$ ls crash*
crash-2021-08-10-17:12:18.log crash-2021-08-11-10:54:56.log 
crash-2021-08-11-12:31:22.log crash-2021-08-11-12:37:52.log[build a1a6394cc5ae] 2021-08-11 12:37:52
Received fatal signal 11 (Segmentation fault).
Cause:
Unknown signal origin (si_code=128, si_addr=[0x0000000000000000]).
Crashing thread: archivereader

This error indicates that signal 11 originated from the OS.

Resolution

There is a bug that causes a race condition with the ingestion pipeline. The settings below safely prevent the race condition and avoids the re-use of a channel.

Modify the limits.conf [input_channels] stanza as below:

[input_channels]
max_inactive = 5100
lowater_inactive = 5000

A restart is needed for the fix to be applied.

Revision History

Revision	Publish Date	Comments
1.0	29-Sep-2026	Initial Release

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)