<?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: Splunk alert failed to execute script on Windows 2008 64-bit in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49572#M660</link>
    <description>&lt;P&gt;Hi Drainy&lt;/P&gt;

&lt;P&gt;If I set the timezone to default, the splunk page will report a common error "str object.....", anyway I will try it, thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 11 May 2012 15:39:04 GMT</pubDate>
    <dc:creator>sonicant</dc:creator>
    <dc:date>2012-05-11T15:39:04Z</dc:date>
    <item>
      <title>Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49568#M656</link>
      <description>&lt;P&gt;I set up an alert to trigger a script (sample "&lt;CODE&gt;echo.bat&lt;/CODE&gt;" in &lt;CODE&gt;$SPLUNK_HOME\bin\scripts\&lt;/CODE&gt;)&lt;BR /&gt;
The alert fired normal, but the script was not executed.&lt;BR /&gt;
When I check the splunkd.log, it says:&lt;/P&gt;

&lt;HR /&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR ScriptRunner - Couldn't start child process. script="E:\Program Files\Splunk\etc\apps\search\bin\runshellscript.py"
ERROR script - Script execution failed for external search command 'runshellscript.'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;HR /&gt;

&lt;P&gt;I tried to add python.exe path to &lt;CODE&gt;%PATH&lt;/CODE&gt;, but it didn't help, strange.....&lt;/P&gt;

&lt;P&gt;splunk version: &lt;CODE&gt;4.3-115073-x64&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;windows: server 2008 64-bit&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 10:07:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49568#M656</guid>
      <dc:creator>sonicant</dc:creator>
      <dc:date>2012-05-11T10:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49569#M657</link>
      <description>&lt;P&gt;did you try to run it manually from the command line to see if you get an error?&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 10:15:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49569#M657</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-05-11T10:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49570#M658</link>
      <description>&lt;P&gt;It sounds like it may be the timezone bug that 4.3 has. It was fixed in 4.3.2 and it relates to Splunk firing scripts.&lt;/P&gt;

&lt;P&gt;To test do the following;&lt;BR /&gt;
Navigate to Manager in the top right, select Your Account in the bottom right, change the timezone to, "Default System Timezone". Hit save and try again.&lt;BR /&gt;
If that works then it is that bug that is affecting you.&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 11:33:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49570#M658</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-05-11T11:33:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49571#M659</link>
      <description>&lt;P&gt;Hi Mario, Yes I tried in search bar "xxxx | runshellscript echo.bat arg1 arg2.....", but it reported the runshellscript returned error 1&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 15:37:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49571#M659</guid>
      <dc:creator>sonicant</dc:creator>
      <dc:date>2012-05-11T15:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49572#M660</link>
      <description>&lt;P&gt;Hi Drainy&lt;/P&gt;

&lt;P&gt;If I set the timezone to default, the splunk page will report a common error "str object.....", anyway I will try it, thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 15:39:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49572#M660</guid>
      <dc:creator>sonicant</dc:creator>
      <dc:date>2012-05-11T15:39:04Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49573#M661</link>
      <description>&lt;P&gt;when I set the timezone to default, the splunk page shows "AttributeError: 'str' object has no attribute 'os_startIndex'"&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 04:08:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49573#M661</guid>
      <dc:creator>sonicant</dc:creator>
      <dc:date>2012-05-14T04:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert failed to execute script on Windows 2008 64-bit</title>
      <link>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49574#M662</link>
      <description>&lt;P&gt;Hi Drainy&lt;/P&gt;

&lt;P&gt;I upgraded splunk to 4.3.2 and the bug gone, thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 09:05:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Splunk-alert-failed-to-execute-script-on-Windows-2008-64-bit/m-p/49574#M662</guid>
      <dc:creator>sonicant</dc:creator>
      <dc:date>2012-05-14T09:05:12Z</dc:date>
    </item>
  </channel>
</rss>

