All Apps and Add-ons

OPSEC LEA - Cannot look up HOME variable

lagnone_splunk
Splunk Employee
Splunk Employee

I am seeing this message when trying to use the OPSEC LEA app for Splunk -

ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity CMA-008" Could not look up HOME variable. Auth tokens cannot be cached.

How might I workaround this?

1 Solution

lagnone_splunk
Splunk Employee
Splunk Employee

One workaround that has worked for some customers is to manually create a SPLUNK_HOME environmental variable

$ export SPLUNK_HOME=/opt/splunk
verify
$ env

If edited in /etc/profiles, this change can persist across logins

View solution in original post

lagnone_splunk
Splunk Employee
Splunk Employee

One workaround that has worked for some customers is to manually create a SPLUNK_HOME environmental variable

$ export SPLUNK_HOME=/opt/splunk
verify
$ env

If edited in /etc/profiles, this change can persist across logins

mikelanghorst
Motivator

It's not asking about SPLUNK_HOME, but rather $HOME, of the user splunk runs as.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...