Deployment Architecture

What will cause AIX get core dump when Splunk Light Weight Forwarder restarts?

zliu
Splunk Employee
Splunk Employee

Sometimes when restart the Splunk Light Forwarder, user will experience a core dump. The forwarder still restarts and functions properly, but the core dump will fill up user's root filesystem.

The problem isn't limited to one host; it happens on several hosts, but all are running AIX 5.3-09.

Tags (1)
1 Solution

dwaddle
SplunkTrust
SplunkTrust

You might check aix's error logs (use the errpt command) - usually a core dump is logged there, with as much information as AIX can figure out.

Often, figuring this kind of thing out would mean having to have:

  • a copy of the binary that hasn't been stripped
  • the source code
  • an AIX machine at the exact same level of libc and kernel
  • the 'full' core file (run "chdev -l sys0 -a fullcore=true") and reboot

In other words, you'll probably need to engage Splunk support.

You might do as well to just disable corefiles for splunk. The only way (for sure) that I know how to do it would be to move $SPLUNK_HOME/bin/splunk to $SPLUNK_HOME/bin/splunk_real and make a shell script to replace the splunk binary, something like:

#!/bin/ksh
ulimit -c 0  #disable core dumps
exec splunk_real $0

View solution in original post

dwaddle
SplunkTrust
SplunkTrust

You might check aix's error logs (use the errpt command) - usually a core dump is logged there, with as much information as AIX can figure out.

Often, figuring this kind of thing out would mean having to have:

  • a copy of the binary that hasn't been stripped
  • the source code
  • an AIX machine at the exact same level of libc and kernel
  • the 'full' core file (run "chdev -l sys0 -a fullcore=true") and reboot

In other words, you'll probably need to engage Splunk support.

You might do as well to just disable corefiles for splunk. The only way (for sure) that I know how to do it would be to move $SPLUNK_HOME/bin/splunk to $SPLUNK_HOME/bin/splunk_real and make a shell script to replace the splunk binary, something like:

#!/bin/ksh
ulimit -c 0  #disable core dumps
exec splunk_real $0

dwaddle
SplunkTrust
SplunkTrust

no, it would not disable core drumps for all root processes. Again, I would strongly suggest getting Splunk support involved if you are getting core dumps regularly. My suggestion above was intended to be a temporary workaround to supress corefiles until Splunk support could figure out the root cause and fix it.

0 Karma

zliu
Splunk Employee
Splunk Employee

will this script disable core dumps for all root processes?

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...