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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...