Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Other Using Splunk
- :
- Alerting
- :
- Splunk alert failed to execute script on Windows 2...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I set up an alert to trigger a script (sample "echo.bat" in $SPLUNK_HOME\bin\scripts\)
The alert fired normal, but the script was not executed.
When I check the splunkd.log, it says:
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.'
I tried to add python.exe path to %PATH, but it didn't help, strange.....
splunk version: 4.3-115073-x64
windows: server 2008 64-bit
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
To test do the following;
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.
If that works then it is that bug that is affecting you.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mario, Yes I tried in search bar "xxxx | runshellscript echo.bat arg1 arg2.....", but it reported the runshellscript returned error 1
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
To test do the following;
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.
If that works then it is that bug that is affecting you.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Drainy
I upgraded splunk to 4.3.2 and the bug gone, thank you!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
when I set the timezone to default, the splunk page shows "AttributeError: 'str' object has no attribute 'os_startIndex'"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Drainy
If I set the timezone to default, the splunk page will report a common error "str object.....", anyway I will try it, thanks!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you try to run it manually from the command line to see if you get an error?
What Is Splunk? Here’s What You Can Do with Splunk
Level Up Your .conf25: Splunk Arcade Comes to Boston
Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...
