topic Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1" in Splunk Enterprise Security

msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

mcronkrite — Mon, 28 Sep 2020 16:12:53 GMT

msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

Error Message appears twice, once for each indexer every 4 hours.
Running Splunk 6.0.2, Splunk Enterprise Security 3.0.1

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

jcoates_splunk — Mon, 24 Mar 2014 00:27:50 GMT

ES is notifying of error exit codes. The app for Cisco IPS is generating one. Why?

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

lbogle — Mon, 28 Apr 2014 18:09:56 GMT

I have the same issue. Any responses to this?

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

sfmike — Mon, 28 Sep 2020 16:44:40 GMT

This error is occurring because Enterprise Security contains a "configuration_checker.py" modular input that attempts to alert you when misconfigurations are detected - we attempt to be proactive and alert to conditions that might be causing the application to misbehave.

In this case, the intent of the alert is to alert when a scripted input or modular input has exited abnormally. The definition of "abnormally" that we use means "exited with a non-zero exit code".

Sometimes, as in this case, this particular check backfires. The error you're seeing is benign and is occurring because the scripted inputs included with the TA-windows add-on use non-zero exit codes even when they exit successfully. This has been corrected in an upcoming version (which of course doesn't help in this instance).

If you would like to just get rid of the message, you can disable this input stanza in the Manager:

Settings --> Data Inputs --> Configuration Checker --> confcheck_script_errors
However, that would disable the exit status checking for ALL scripted and modular inputs on the system. If you'd like a more robust solution, reach out to support and mention this posting, and we can provide a small patch to the configuration_checker.py script which will deal with this in a more intelligent fashion - with the caveat that it wouldn't persist beyond an upgrade.

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

mcronkrite — Thu, 12 Jun 2014 01:16:45 GMT

http://answers.splunk.com/answers/123207/enterprise-security-message

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

mcronkrite — Sun, 15 Jun 2014 17:48:52 GMT

This worked for me. I disabled configuration checker and messages stopped.

Re: msg="A script exited abnormally input="$SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py " stanza="default" status="exited with code 1"

bpaul_splunk — Tue, 29 Sep 2020 06:52:34 GMT

With Enterprise Security version 3.3.0, you can now adjust the configuration script, rather than disable it.

go to the Settings > Data Inputs page.
Click on Configuration Checker.
Modify the "Suppression string" parameter of confcheck_script_errors to exclude the items needing to be suppressed.

Only do this if you are sure the script is exiting normally, and returning the referenced code value.