Splunk Enterprise Security

Script exited abnormally with code 114

lball
Explorer

I'm getting a scripting error on our Enterprise Security server every hour:

msg="A script exited abnormally" input="$SPLUNK_HOME/etc/apps/splunk_instrumentation/bin/instrumentation.py" stanza="default" status="exited with code 114"

Other than that, everything seems to be working. How can I resolve this error?

0 Karma
1 Solution

lakshman239
Influencer

Did the warning go after you restarted the instance? I assume you haven't added custom config to instrumentation app.

I have noticed in the past the modular inputs complained with exit code when the input wasn't initialized correctly. [ A clean stop/start or restart helped]

View solution in original post

0 Karma

lakshman239
Influencer

Did the warning go after you restarted the instance? I assume you haven't added custom config to instrumentation app.

I have noticed in the past the modular inputs complained with exit code when the input wasn't initialized correctly. [ A clean stop/start or restart helped]

0 Karma

lball
Explorer

That did the job! Thanks!

0 Karma

lakshman239
Influencer

Pls accept the comment, so this query appears answered.

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!

How Splunk AI Assistant Is Transforming Investigations: Insights from .conf26

At .conf26 in Denver, I spent much of my time in conversation with Splunk customers about Splunk AI Assistant. ...

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...