The page displays the location of the files that the Access Manager components use for logging system messages. There are some exceptions:
J2EE Agent:
The J2EE Agent uses the J2EE global logger, and the location of this file is customizable. For information about J2EE agent log files, see Viewing Log Files
in the Novell Access Manager 3.1 SP2 J2EE Agent Guide.
Default Auditing File: If you have configured Novell Audit to send events to the default audit file (on Linux, this is/var/opt/novell/naudit/logs/auditlog), this file does not appear in the list. (On a Windows machine that has different security restraints, the file appears in the list.)
If you want this file to appear in this list on a Linux machine, you must make this file readable by the novlwww user. It is a breach of Novell Audit security for Access Manager code to change the permissions on this file. You must decide whether changing its permissions and displaying the file in this list compromises your security.
To have it appear in the list of files for the Administration Console, configure the following:
Use commands similar to the following to grant the novlwww user executable permissions to the naudit directories:
chmod o+x /var/opt/novell/naudit chmod o+x /var/opt/novell/naudit/logs
Use a command similar to the following to grant the novlwww user read access to the auditlog file:
chmod o+r /var/opt/novell/naudit/logs/auditlog
Proxy Service Log Files:
If you enable proxy service logging, these files are not available for downloading from this page because there could be potentially hundreds of these files. If this type of logging has been enabled, the directory where they are located is displayed. For more information about this type of logging, see Configuring Logging for a Proxy Service
in the Novell Access Manager 3.1 SP2 Access Gateway Guide.
To view or download the log file:
In the Administration Console, click > .
Select one or more log files, click , then open it or save it to disk.
You can use any text editor to view the file.
Each Access Manager component generates multiple log files. The following tables lists these files and the types of messages they contain.
|
Filename |
Description |
|---|---|
|
/var/opt/novell/tomcat5/logs/catalina.out |
Logging to this file only occurs if you have selected the option from the > > > page. Check this file for entries tracing the evaluation of authorization, identity injection, and form fill policies. |
|
/var/log/novell/reverse/<name> |
If logging is enabled on one or more reverse proxies, this directory contains the log files. To enable this type of logging, see A directory is listed for each reverse proxy on which you have enabled logging. |
|
/var/log/ics_dyn.log |
Contains all log entries generated by the Linux Access Gateway Appliance. Use syslog to control file rolling and log file distribution. |
|
/opt/novell/devman/jcc/logs/jcc-0.log.0 |
Contains the log entries for the server communications module related to interaction of the Access Gateway with the Administration Console, such as imports, certificates, health checks, and configuration. |
|
/var/log/lagsoapmessages |
Logs all the SOAP messages between the Linux Access Gateway and the Embedded Service Provider. |
|
/var/log/laghttpheaders |
Contains a log of the HTTP headers to and from the Linux Access Gateway. |
|
Filename |
Description |
|---|---|
|
/var/log/novell-apache2 |
If logging is enabled on one or more reverse proxies, this directory contains the log files. To enable this type of logging, see This directory also contains the Apache generated log files such as the error_log file. |
|
/var/opt/novell/amlogging/logs |
If you have enabled log profiles, this directory contains these log files. To enable this type of logging, see |
|
/var/opt/novell/amlogging/logs/ags_error.log |
Contains the messages generated for configuration, device imports, health, and statistics. It also contains entries for the policy evaluation processes done by the Gateway Service Manager module. |
|
/var/opt/novell/tomcat5/logs/catalina.out |
Contains the log messages generated by the Embedded Service Provider. Logging to this file occurs only if you have selected the option from the > > > page. Check this file for entries tracing the evaluation of authorization, identity injection, and form fill policies. |
|
Filename |
Description |
|---|---|
|
\Program Files\Novell\amlogging\logs\ ags_error.log |
Contains the messages generated for configuration, device imports, health, and statistics. It also contains entries for the policy evaluation processes done by the Gateway Service Manager module. |
|
\Program Files\Novell\amlogging\logs\ |
If you have enabled log profiles, this directory contains these log files. To enable this type of logging, see |
|
\Program Files\Novell\Apache\logs\ <name> |
If logging is enabled on one or more reverse proxies, this directory contains the log files. To enable this type of logging, see This directory also contains the Apache generated log files such as the error_log file. |
|
\Program Files\Novell\Tomcat\logs\ stdout.log |
Contains the log messages generated by the Embedded Service Provider. Logging to this file only occurs if you have selected the option from the > > > page. Check this file for entries tracing the evaluation of authorization, identity injection, and form fill policies. This file is reset whenever Tomcat is restarted. |