Linux Access Gateway Not Responding - Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE Manual

Proxy Hang Core
To analyze the proxy hang and create a core file:
1 Enter the following command to change the root environment:
chroot /chroot/lag
2 Enter the following command to attach the ics_dyn process to the debugger:
gdb /opt/novell/bin/ics_dyn <pid>
Where <pid> refers to the Process ID of the ics_dyn process.
3 At the GDB prompt, enter the following command:
set logging on <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 collect a stack trace of all threads:
thread apply all bt
5 Enter the following command to turn off logging:
set logging off
6 Enter the following command to save the core dump in the
gcore
The core dump is saved as
7 Tar or zip this file and send it to Novell Support.
Packet Capture
The utility allows you to capture network trace packets.
tcpdump
1 Log in as the
root
2 Enter the following command:
tcpdump -s0 -n -t -p -i 'any' -w filename.cap
3 Tar or zip this file and send it to Novell Support.

7.6.5 Linux Access Gateway Not Responding

If the Linux Access Gateway is not responding, do the following:
1 Enter the following command to change the root environment:
chroot /chroot/lag
2 Enter the following command to attach the ics_dyn process to the debugger:
gdb /opt/novell/bin/ics_dyn <pid>
Where <pid> refers to 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>
.
core.<pid>
user.
directory.
/chroot/lag
Troubleshooting the Linux Access Gateway 199