Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
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.
- Find Answers
- :
- Splunk Administration
- :
- Monitoring Splunk
- :
- OPSEC LEA 2.0.1 setup issues
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
araitz
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?
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!
Splunk Enterprise Security: An Automated Phishing Response Workflow
Originally posted on Splunk.com.
Key takeaways
The volume of phishing emails can overwhelm even the most ...
Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...
Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...
Data Outage Monitoring and Reporting
We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...
