topic Re: "Couldn't determine $SPLUNK_HOME, perhaps it should be set in environment" in Monitoring Splunk

"Couldn't determine $SPLUNK_HOME, perhaps it should be set in environment"

madhanbaskar — Fri, 07 Jul 2017 11:53:50 GMT

$ cd /opt/splunkforwarder/bin
$ ./splunk status
Couldn't determine $SPLUNK_HOME, perhaps it should be set in environment

When ./splunk status command is executed in Splunk Forwarder's bin folder, the above mentioned splunk home error is getting displayed.

Please suggest me a way to resolve this issue.

Thanks

adonio — Fri, 07 Jul 2017 12:19:44 GMT

check the splunk-launch.conf at .../splunkforwarder/etc/

niketn — Fri, 07 Jul 2017 12:43:20 GMT

On the server where you are trying to run ./splunk status set the environment variable using export.

cpetterborg — Fri, 07 Jul 2017 15:01:02 GMT

Please note the addition of the line in the middle:

$ cd /opt/splunkforwarder/bin
$ . setSplunkEnv
$ ./splunk status

woodcock — Sat, 08 Jul 2017 22:05:17 GMT

The environment variable is not set by default anywhere. In *NIX bash shell, you can put this in ~/.bash_profile:

export SPLUNK_HOME="/opt/splunk"

ddrillic — Sun, 09 Jul 2017 00:40:58 GMT

It might be related to permissions to run the splunk binary. It says -