Splunk Search

Scripted Input failing, runs fine when run manually

kholleran
Communicator

Hello,

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.

Kevin

0 Karma

kholleran
Communicator

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"

jrodman
Splunk Employee
Splunk Employee

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, %SPLUNK_HOME%\etc\apps\myapp\bin\foo.py

0 Karma

Brian_Osburn
Builder

Doh! I've had that happen too..

0 Karma

Brian_Osburn
Builder

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..

Brian

Get Updates on the Splunk Community!

Raise Your Skills at the .conf25 Builder Bar: Your Splunk Developer Destination

Calling all Splunk developers, custom SPL builders, dashboarders, and Splunkbase app creators – the Builder ...

Hunt Smarter, Not Harder: Discover New SPL “Recipes” in Our Threat Hunting Webinar

Are you ready to take your threat hunting skills to the next level? As Splunk community members, you know the ...

Splunk ITSI & Correlated Network Visibility

  Now On Demand   Take Your Network Visibility to the Next Level In today’s complex IT environments, ...