Proxy Service of Access Gateway Service is built on top of Apache as an Apache application. This module handles browser requests for access to resources and is responsible for sending authorized requests to the web servers. Entries for these events are logged to Apache log files.
/var/log/novell-apache2/
For more information, see Ignoring Some Standard Messages and Managing Access Gateway Logs.
Apache cannot detect the proper use of domain-based multi-homing with wildcard certificates, which allows multiple proxy services to share the same SSL port. If you create reverse proxy services that are configured for domain-based multi-homing with SSL, Apache considers this a possible port conflict and logs it as a warning in the error.log file.
The error messages look similar to the following:
[<time and date stamp>] [warn] Init: SSL server IP/port conflict: dbmhnsnetid.dsm.cit.novell.com:443 (C:/Program Files/Novell/apache/conf/vhosts.d/dbmhNS-NetID.conf:18) vs. magwin1430external.dsm.cit.novell.com:443 (C:/Program Files/Novell/apache/conf/vhosts.d/magMaster.conf:18) [<time and date stamp>] [warn] Init: SSL server IP/port conflict: magdbmheguide.dsm.cit.novell.com:443 (C:/Program Files/Novell/apache/conf/vhosts.d/dbmhMagEguide.conf:18) vs. magwin1430external.dsm.cit.novell.com:443 (C:/Program Files/Novell/apache/conf/vhosts.d/magMaster.conf:18)
Ignore these errors because Access Gateway Service knows how to handle the traffic and sends the packets to the correct proxy service. For more information about Apache log files, see “Log Files”.
If the Apache error log file does not contain enough information, you can modify the log level and the types of messages written to the file.
WARNING:If you set the log level to debug, the size of the file can grow quickly, consume all available disk space, and crash the system. If you change the log level, you need to carefully monitor available disk space and the size of the error log file.
To modify what is written to the Apache error log file, perform the following steps:
Modify the httpd.conf file.
For information about how to modify a file, see Modifying Configurations.
Find the LogLevel directive and set it to one of the following:
debug, info, notice, warn, error, crit, alert, emerg
(Optional) If you set the level to debug and the log file still does not supply enough information, see Section 32.2.4, Enabling Debug Mode and Core Dumps.