- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ERROR script - command="runshellscript", Cannot find script
Hello
I have installed the app http://splunk-base.splunk.com/apps/50967/use-python-mail-for-scripted-alerts and i have made the troubleshooting with this manual http://wiki.splunk.com/Community:TroubleshootingAlertScripts, but whiteout success.
This is the results:
Check that the script itself runs outside of Splunk. --> pass successful
Use the "somesearch here | runshellscript
Test with schedule and elerting in savedsearch --> faild. --> ERROR script - command="runshellscript", Cannot find script at /opt/splunk/bin/scripts/sendmailpython.sh in the splunkd.log.
Any ideas what happen?
Sam
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

It appears that this problem arises due to the user not having the right splunk "capability". I'm not sure which capability is required but when I added the "admin" role to my user, the problem went away.
I would love to know specifically which capability is required so I can make my user minimally enabled to use runshellscript.py
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

It appears that the capability: edit_scripted is required to use "runshellscript"
without this capability, I was getting the error described above, with the capability, it works fine.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also having this problem. I have had a working script in the /opt/splunk/bin/scripts/ directory for several months now, and suddenly it is not firing when my alerts are generated. I checked the splunkd.log and found command="runshellscript" cannot find script at /opt/splunk/bin/scripts/.py.
Anyone know what might cause this behavior? The splunk instance has not be upgraded or altered in many months, so the files shouldn't be changing or randomly fail to find something that has existed for that long.
