Deployment Architecture

Missing /sbin in PATH and troubleshoting *nix scripts not functioning

jhallman
Explorer

/sbin was not in the path so things like ifconfig used in *nix apps

$SPLUNK_HOME/etc/apps/unix/bin/interfaces.sh is not reporting throughpout data.

I tried Manager » Server controls Restart Splunk.

Will I have to restart the process itself to get it to recognize /sbin is now in the PATH?

Also, how can I more easily figure out when some *nix script is not working properly?

Thanks

Tags (1)
0 Karma

jhallman
Explorer

So each script calls common.sh

In common.sh we added

if [ $# -ge 1 -a "x$1" = "x--debug" ] ; then
        DEBUG=1
        TEE_DEST=`dirname $0`/debug--`basename $0`--`date | sed 's/ /_/g;s/:/-/g'`
else
        DEBUG=0
        TEE_DEST=/dev/null
fi
####Add this
    DEBUG=1
    TEE_DEST=`dirname $0`/debug--`basename $0`--`date | sed 's/ /_/g;s/:/-/g'`
####End Add

which created a debug file (for each script being run) and within
debug--interfaces.sh--* we saw ifconfig command not found.

We ultimately stopped/restarted the splunk service and the new PATH got picked up.

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...