Monitoring Splunk

OPSEC LEA 2.0.1 setup issues

rudyw
New Member

I was able to pull the checkpoint cert and verified communication son the checkpoint side.

Log grabber is trying to execute as seen in splunkd.log but is reporting the following prolems:

04-06-2013 14:24:50.718 -0500 INFO  TcpOutputProc - Connected to idx=192.168.120.52:9997
04-06-2013 14:24:56.285 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:24:56.949 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:24:57.853 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:06.813 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:07.646 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:08.582 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:18.484 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:19.352 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:20.628 -0500 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/Splunk_TA_opseclea_linux22/bin/lea-loggrabber.sh --configentity opsec" Could not look up HOME variable.  Auth tokens cannot be cached.
04-06-2013 14:25:20.739 -0500 INFO  TcpOutputProc - Connected to idx=192.168.120.51:9997

Does anyone have any insight?

0 Karma

sjscott
Explorer

The fix for this problem is to create a home directory for the splunk account. Make sure you create it and set the appropriate permissions.

# mkdir /home/splunk
# chown splunk /home/splunk/
# chgrp splunk /home/splunk/

Then restart splunk.

araitz
Splunk Employee
Splunk Employee

Can you verify that the user that Splunk is running as has a home directory and can write to it?

Get Updates on the Splunk Community!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...