Getting Data In

Scripted inputs fails on pooled search heads

richnavis
Contributor

I am trying to implement the Cisco IPS App on pooled search heads, but the scripted inputs are failing with the following error: Incorrect path to script: \\Server01\prod\SplunkSharedConfig\etc\apps\Splunk_CiscoIPS\bin\get_ips_feed.py. Script must be in a bin subdirectory in $SPLUNK_HOME.

I've tested the path and it is correct. Anyone have any thoughts?

Tags (1)

Damien_Dallimor
Ultra Champion

It looks as if you have placed your input script in your Search Head pools shared storage path hence the error saying that the script must live within $SPLUNK_HOME , //Server01/prod/SplunkSharedConfig is not your $SPLUNK_HOME

You will need to place the script where Splunk is installed ie: $SPLUNK_HOME/etc/apps/Splunk_CiscoIPS/bin/get_ips_feed.py

Damien_Dallimor
Ultra Champion

You still have the apps shared via shared storage , but what you are doing in a distributed setup is splitting out the various components of the app.In this case you are splitting out the data collection components(get_ips_feed.py), which could possibly live on a Splunk forwarder or indexer, from the data viewing and searching components(views, alerts, saved searches,eventtypes, lookups & various other knowledge objects) which can live on your search head pools shared storage path.

0 Karma

richnavis
Contributor

Makes sense.. but apps in searchhead pools aren't really shared if they are installed locally..

0 Karma
Get Updates on the Splunk Community!

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...