Monitoring Splunk
×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
Ask a Question

OPSEC LEA 2.0.1 setup issues

rudyw
New Member
‎04-06-2013 12:27 PM

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
Reply

sjscott
Explorer
‎03-26-2015 05:40 AM

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.

Reply

araitz
Splunk Employee
Splunk Employee
‎04-09-2013 11:01 AM

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

Reply
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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...