The Access Gateway Crashes When Log Files Are Removed; Troubleshooting A Failed Access Gateway Configuration; Troubleshooting A Access Gateway Crash - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

For more information about the
www.novell.com/documentation/nsureaudit/nsureaudit/data/al36zjk.html#alibmyw).
7.6.3 The Access Gateway Crashes When Log Files Are
Removed
If you have enabled the debug level of logging for the
log files and these files grow to be over 200 MB, manually deleting these files can cause the Access
Gateway to crash.
To solve the problem, restart the Access Gateway after manually deleting the files.

7.6.4 Troubleshooting a Failed Access Gateway Configuration

If the IP address and other network configurations are not reflected in the installed Access Gateway,
log in as a user and run the following commands:
root
rm /opt/novell/legacy/etc/proxy/.novell_lag_lock
/etc/init.d/novell-vmc stop
/etc/init.d/novell-vmc start

7.6.5 Troubleshooting a Access Gateway Crash

The Access Gateway might crash 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.
"Access Gateway Logs" on page 229
"Event Log" on page 230
"Core Dump" on page 231
"Proxy Hang Core" on page 232
"Packet Capture" on page 232
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
tar file is located in the
laglogs.tgz
3 Send this tar file to Novell Support.
file and these parameters, see
logevent
laghttpheaders
/var/log
Logevent (http://
and the
lagsoapmessages
directory.
Troubleshooting the Access Gateway Appliance 229