Refine your search:

Does anyone know of a good way to debug problems with the checkpoint lea client? I've been having trouble getting my configured.

asked 08 Nov '11, 09:57

jbsplunk's gravatar image

jbsplunk ♦
10.7k1625
accept rate: 49%


One Answer:

Yes! you'll want to add a shell variable that calls OPSEC debugging when the lea_loggrabber client is called. First, set the OPSEC debug level:

OPSEC_DEBUG_LEVEL=3; export OPSEC_DEBUG_LEVEL

Then run the splunk lea_loggrabber.sh script manually:

SPLUNK_HOME=/opt/splunk/ ./lea-loggrabber.sh

The debug output is very verbose so you may want to send the output to a file for splunk support to review.

If you need to dive deeper into the problem, on the Checkpoint Manager you can also enable OPSEC debugging.

% fw debug fwm on OPSEC_DEBUG_LEVEL=9

The debug file is located at $FWDIR/log/fwm.elg

To stop the FWM debug, execute:

% fw debug fwm off OPSEC_DEBUG_LEVEL=1
link

answered 08 Nov '11, 10:21

Chubbybunny's gravatar image

Chubbybunny
1.3k28
accept rate: 69%

edited 08 Nov '11, 10:25

Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×56
×5
×1

Asked: 08 Nov '11, 09:57

Seen: 1,785 times

Last updated: 08 Nov '11, 10:25

Copyright © 2005-2012 Splunk Inc. All rights reserved.