Troubleshooting A Failed Linux Access Gateway Configuration; Troubleshooting A Linux Access Gateway Crash - Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE Manual

7.6.3 Troubleshooting a Failed Linux Access Gateway
Configuration
If the IP address and other network configurations are not reflected in the installed Linux Access
Gateway, log in as a
rm /opt/novell/legacy/etc/proxy/.novell_lag_lock
/etc/init.d/novell-vmc stop
/etc/init.d/novell-vmc start

7.6.4 Troubleshooting a Linux Access Gateway Crash

The Linux Access Gateway might have crashed because of the following reasons:
SIGSEGV
ASSERT (for a debug build only)
The following sections explain how to gather the files that need to be sent to Novell for a resolution
of the problem.
"Linux Access Gateway Logs" on page 196
"Event Log" on page 196
"Core Dump" on page 198
"Proxy Hang Core" on page 199
"Packet Capture" on page 199
Linux Access Gateway Logs
1 Enter the following command from the bash shell to collect the debug log files that are
generated:
/chroot/lag/opt/novell/bin/getlaglogs.sh
2 The
laglogs.tgz
3 Send this tar file to Novell
Event Log
By default the event log size is 15 MB. The size of event log can be controlled by configuring the
required event log size in the
directory. For example, if you specify 350 in the file, you can configure an event log of size
novell
350 MB. This file should contain only the file size information. This file should not contain any
other characters or new lines.
The procedure for obtaining the event log depends upon the build type:
"Event Log for a Production Build" on page 197
"Event Log for a Debug Build" on page 197
196 Novell Access Manager 3.1 SP1 Access Gateway Guide
user and run the following commands:
root
tar file is located in the
®
Support.
eventlogsize.cfg
directory.
/var/log
file, located at the
/chroot/lag/etc/opt/