Access Gateway Not Responding; Access Gateway Dumps Core After 10 Minutes When Non-Redirected Login Is Enabled - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

7.6.6 Access Gateway Not Responding

1 Enter the following command to change to the
chroot /chroot/lag
2 Enter the following command to attach the ics_dyn process to the debugger:
gdb /opt/novell/bin/ics_dyn <pid>
Replace <pid> with the process ID of the ics_dyn process. You can get the process ID by
entering the following command:
pgrep ics_dyn
3 At the GDB prompt, enter the following command:
set logging file <filename>
Where <filename> specifies the name of the file that will store the output of the executed
debugger commands.
4 Enter the following command to start logging:
set logging on
5 Enter the following command to collect a stack trace of all threads:
thread apply all bt full
6 Enter the following command to turn off logging:
set logging off
7 Enter the following command to save the core dump in the
gcore
The core dump is saved as
8 Tar or zip this file and send it to Novell Support.
7.6.7 Access Gateway Dumps Core After 10 Minutes When
Non-Redirected Login Is Enabled
In a clustered Novell Access Manager deployment setup, if non-redirected login is enabled, equal
load balancing across the Identity Servers might not happen. This might result in Access Gateway
dumping core after approximately 10 minutes.
This happens because browsers connect to the Identity Server through an L4 switch and not directly.
For example:
If you have four Access Gateways in a cluster, then the L4 switch in front of the Identity Server
receives connections from four Access Gateways.
If you have configured the sticky bit for the L4 switch based on the client IP address, then all
the connections from one Access Gateway go to one Identity Server. You must configure the
sticky bit based on your requirement.
root
.
core.<pid>
environment:
directory.
/chroot/lag
Troubleshooting the Access Gateway Appliance 233