Splunk Dev

Getting Execprocessor error with bash script

matthewhasty
Explorer

I am getting this error when running my script as a scripted input:

05-07-2018 10:28:00.177 -0500 ERROR ExecProcessor - message from "/opt/splunk/bin/scripts/pingdomtest" \r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100 723 0 723 0 0 842 0 --:--:-- --:--:-- --:--:-- 842\r100 8666 0 8666 0 0 8345 0 --:--:-- 0:00:01 --:--:-- 8348

My inputs .conf looks like this:
[script://$SPLUNK_HOME/bin/scripts/pingdomtest]
disabled = false
index = test
interval = 120
source = ./pingdomtest
sourcetype = json_no_timestamp

I have run the script by itself and it is working and getting the data down from pingdom.

Thanks!

Tags (1)
0 Karma
1 Solution

jconger
Splunk Employee
Splunk Employee

Try running the script from the command line as Splunk like so:

/opt/splunk/bin/splunk cmd /opt/splunk/bin/scripts/pingdomtest

View solution in original post

0 Karma

jconger
Splunk Employee
Splunk Employee

Try running the script from the command line as Splunk like so:

/opt/splunk/bin/splunk cmd /opt/splunk/bin/scripts/pingdomtest
0 Karma

matthewhasty
Explorer

Had to fix the script, it is working now, thanks!

0 Karma
Get Updates on the Splunk Community!

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...