If the log files do not generate enough information to identify the cause of a problem, run Access Gateway Service in the debug mode. Use the debug mode only when you try to isolate a problem because running Access Gateway Service in the debug mode can have the following effects:
Debug mode increases the size of the log files quickly. The size can increase enough to consume all available disk space and crash the system. When running in the debug mode, monitor the available disk space and the size of the log files.
In a highly loaded system, debug mode can lead to request or connection timeout and can slow down the response time.
IMPORTANT:When you enable the logging in the debug mode, it enables most of the log levels, which may not be required for troubleshooting. Hence, during high load period, perform the following steps to reduce the impact on Access Gateway’s performance.
Click Devices > Access Gateways > Edit > Advanced Options.
Add the following options:
LogLevel error LogLevel novell_ag_module:debug LogLevel ssl:warn mpm_worker:warn core:warn LogLevel proxy:warn proxy_balancer:warn proxy_ajp:warn proxy_http:warn
Click OK.
Adding these options enable only error, debug, and warn levels for specific components.
Debug mode enables core dumps, X-Mag headers in LAN traces, and increases log levels by enabling advanced option in Access Gateway configuration. For example LogLevel debug. This will set apache log level to debug in the error_log file.
You can generate core dumps in the following two ways:
Start /etc/init.d/novell-apache2 in debug mode. When there is a crash, core file will be created as /var/cache/novell-apache2/core.
Without starting novell-apache2 in debug mode, perform the following:
Set ulimit -c unlimited in /etc/init.d/novell-apache2 startup script.
You can create the core directory under /tmp. Choose the file path based on the availability of disk space. Give the following command to create a directory in Access Gateway component:
# mkdir -p /tmp/apache2-gdb-dump
Set permission as follows:
# chown novlwww:www /tmp/apache2-gdb-dump
# chmod 0777 /tmp/apache2-gdb-dump
Add the following advanced option in Access Gateway configuration as follows:
CoreDumpDirectory /tmp/apache2-gdb-dump
Apply changes to Access Gateway.
Whenever there is a crash, core file will be created as/tmp/apache2-gdb-dump/core.
For some crashes, the /tmp/debug000.log file is created. For more information about the log, see TID 7011804.
This section describes the following tasks:
Use the following commands to start debug mode:
/etc/init.d/novell-apache2 stop OR rcnovell-apache2 stop
/etc/init.d/novell-apache2 start debug OR rcnovell-apache2 start debug
Examine the Apache error log file or copy it so you can send it to NetIQ Technical Support:
/var/log/novell-apache2
View the information at the local URLs or copy the pages to send to NetIQ Support:
http://127.0.0.1:8181/server-status
This page displays debug information about caching, SSL, workers, and proxy information.
http://127.0.0.1:8181/server-info
This page displays module and configuration information.
If a crash occurred, examine the core dump file or copy it so you can send it to NetIQ Technical Support.
/var/cache/novell-apache2
Use the following commands to disable debug mode:
/etc/init.d/novell-apache2 stop OR rcnovell-apache2 stop
/etc/init.d/novell-apache2 start nodebug OR rcnovell-apache2 start nodebug