I have a scriped input that is throwing an error:
ERROR ExecProcessor - message from ""MyScript.bat"" python: can't open file 'MyScript.py': [Errno 2] No such file or directory
However, when I log into that server, run the batch file from the command line, it runs just fine. The batch file looks like this:
@echo off "PATH_TO_SPLUNK.EXE\splunk.exe" cmd python MyScript.py
This runs in the etc/apps/myscriptapp/bin
Does anyone know whey the batch file would run just fine when executed from the cmd line and not from within Splunk?
Thanks for any help.
I ended up putting the whole path in the MyScript.py section instead of the relative path.
@echo off "PATH_TO_SPLUNK.EXE\splunk.exe" cmd python "PATH_TO_SCRIPT\MyScript.py"
splunk cmd has special behavior for running executables, (it looks in a particular directory) but python doesn't. Python myscript.py will look in the current directory, wherever that is. I recommend using the environment. For a batch file,
Doh! I've had that happen too..
Is $SPLUNK_HOME/var/log/splunk/splunkd.log reporting any errors when it runs?
I think the script needs to be under $SPLUNK_HOME/bin/scripts..