AIX Universal Forwarder Crash Due to Library Conflict in Splunk 9.1.x

Available Languages

Updated:September 29, 2026
Document ID:SPLK048312

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 Enterprise, Splunk Cloud

Description

Users reported that Splunk Universal Forwarders on AIX servers crashed during attempts to send data to indexers. The crashes resulted in millions of null field values and required manual restarts of the forwarders weekly. Analysis revealed that the crashes were caused by a library conflict with the pow() function in libbsd.a, leading to stack corruption.


Investigation

  • Identified similar issues in Jira SPL-245807 where UFs crashed when failing to connect to indexers.
  • Determined that the fix for SPL-245807 was accidentally reverted during the backport of SPL-252792.
  • Confirmed that the absence of debug symbols in the AIX build hindered detailed crash analysis.
  • Verified that the issue persists in Splunk versions 9.1.2 to 9.1.7.

Resolution

  • The permanent fix for the library conflict has been implemented in Splunk versions 9.2.x, 9.3.x, and 9.4.x.
  • Users are advised to upgrade their Splunk Universal Forwarders to one of these versions.
  • Testing the upgrade on a subset of servers is recommended before full deployment.
  • Splunk will not reintroduce the fix into the 9.1.x branch as it approaches end-of-life.

Revision History

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

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products