Getting Data In

ExecProcessor - Ignoring my new script

jordans
Path Finder
ERROR ExecProcessor - Ignoring: "\\C:\Program Files\Splunk\etc\apps\test\bin\intodns.py"

This new scripted input I created isn't generating data, but it runs fine from the command line. The only error I can find in Splunk is the above. No other indication of why it is being ignored.

I've tried using a wrapper .bat:

ERROR ExecProcessor - Ignoring: "\\C:\Program Files\Splunk\etc\apps\test\bin\intodns_wrapper.bat"

and moving the script to various locations.

Can someone help with troubleshooting?

Tags (1)
0 Karma
1 Solution

jordans
Path Finder

Thanks, Ayn. It was the slashes. I think I added the script through the UI first, then edited it later and removed the wrong slashes when I changed the script location after I discovered that scripts have to be in certain directories.

View solution in original post

0 Karma

jordans
Path Finder

Thanks, Ayn. It was the slashes. I think I added the script through the UI first, then edited it later and removed the wrong slashes when I changed the script location after I discovered that scripts have to be in certain directories.

0 Karma

Ayn
Legend

Judging by the leading \\ in the error message it seems you are not entering the path to the script correctly. How are you referring to the script in inputs.conf?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...