<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Script exited abnormally with code 114 in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395913#M4359</link>
    <description>&lt;P&gt;Pls accept the comment, so this query appears answered.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Feb 2019 16:34:37 GMT</pubDate>
    <dc:creator>lakshman239</dc:creator>
    <dc:date>2019-02-11T16:34:37Z</dc:date>
    <item>
      <title>Script exited abnormally with code 114</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395910#M4356</link>
      <description>&lt;P&gt;I'm getting a scripting error on our Enterprise Security server every hour:&lt;/P&gt;

&lt;P&gt;msg="A script exited abnormally" input="$SPLUNK_HOME/etc/apps/splunk_instrumentation/bin/instrumentation.py" stanza="default" status="exited with code 114"&lt;/P&gt;

&lt;P&gt;Other than that, everything seems to be working. How can I resolve this error?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 22:41:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395910#M4356</guid>
      <dc:creator>lball</dc:creator>
      <dc:date>2020-09-29T22:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: Script exited abnormally with code 114</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395911#M4357</link>
      <description>&lt;P&gt;Did the warning go after you restarted the instance? I assume you haven't added custom config to instrumentation app. &lt;/P&gt;

&lt;P&gt;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]&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2019 17:45:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395911#M4357</guid>
      <dc:creator>lakshman239</dc:creator>
      <dc:date>2019-01-10T17:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: Script exited abnormally with code 114</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395912#M4358</link>
      <description>&lt;P&gt;That did the job! Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 16:07:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395912#M4358</guid>
      <dc:creator>lball</dc:creator>
      <dc:date>2019-02-11T16:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Script exited abnormally with code 114</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395913#M4359</link>
      <description>&lt;P&gt;Pls accept the comment, so this query appears answered.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 16:34:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Script-exited-abnormally-with-code-114/m-p/395913#M4359</guid>
      <dc:creator>lakshman239</dc:creator>
      <dc:date>2019-02-11T16:34:37Z</dc:date>
    </item>
  </channel>
</rss>

