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

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...