Skip to content

Evidian WAM Logs

There are 4 types of files for all WAM servers.

  • access and errors: generated by Apache process related to the server.

  • lpfError and lpfTrace: generated by WAM

These four log files are always generated, nevertheless, to have more logged pieces of information in lpfError and lpfTrace files, set LpfLogLevel to "3" in the $LPF_ROOT_DIR/sg/proxy-main/config/pxphttpd_main.conf file.

Log Rotations

Evidian Web Access Manager (WAM) provides a log file rotation facility to manage and archive log files efficiently, ensuring that disk space usage is minimized and system overhead is reduced. Here’s how it works.

  • Purpose: The log rotation feature is designed to archive log files to prevent excessive disk space usage and to reduce system overhead.

  • Files Managed: The facility manages several types of files, including: Access and error files. Internal error and trace files located in the directory $LPF_ROOT_DIR/sg/proxy-/logs.

  • Configuration Parameters: To configure log file rotation, you can set values for the following parameters:

Maximum number of log files: By default, this is set to 5. Maximum size of log files (MB): By default, this is set to 10 MB. Time between two rotations (minutes): By default, this is set to 0, meaning log files are rotated only when the maximum log file size is reached.

  • Archiving Process: A log file is archived when its size reaches the maximum size value or when the specified time period expires. The archiving process involves renaming and deleting files as follows:

The oldest archive file (e.g., file.2) is deleted. The next oldest file (e.g., file.1) is renamed to the next in sequence (e.g., file.2). The current log file is renamed to file.1. A new log file is created empty.

  • Viewing Logs: Log and error files can be viewed through the gateway object's edition window in the Administration Console or with a text editor.

This log rotation mechanism helps in maintaining the efficiency and performance of the Web Access Manager by ensuring that log files do not consume excessive disk space.

[root@oracle bin]# ls
ab            apu-1-config  dbmmanage    fcgistarter   htdigest  httxt2dbm           rotatelogs
apachectl     apxs          envvars      htcacheclean  htpasswd  logresolve          xmlwf
apr-1-config  checkgid      envvars-std  htdbm         httpd     pxp_env_rotatelogs
[root@oracle bin]# pwd
/usr/evidian/lpf2/ap2/bin
[root@oracle bin]#


[root@oracle bin]# ./pxp_env_rotatelogs -h

 Usage: ./pxp_env_rotatelogs <logfile> <rotation time in minutes> <maxsize MB> <archive nb> <manage portal and gateway rotation 0|1>

Add this:

TransferLog "|./pxp_env_rotatelogs <logfile> <rotation time> <maxsize> <archive nb> <manage portal and gateway rotation 0|1> "

to httpd.conf. The generated name will be <logfile>.n (with n <archivenb)

 [root@oracle bin]#
How shall understand log rotations are working fine?

Proxy-Main Logs

A lpfError file common to all the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfError

A lpfTrace file common to all the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfTrace

Portal Logs

A Web Access Manager portal writes in several log files:

An access file that records information about requests to the portal and responses from the portal:
$LPF_ROOT_DIR/sg/proxy-<Portal-ID>/logs/access
This access file can be visualized through the WAM console.

An errors file that lists internal errors related to the portal:
$LPF_ROOT_DIR/sg/proxy-<Portal-ID>/logs/errors
This errors file can be visualized through the WAM console.

Where $LPF_ROOT_DIR is the Web Access Manager server installation directory.
The <Portal-ID> value (like lpfportal_<nb>) is returned by the command:

$LPF_ROOT_DIR/bin/lpfgateway -list_local -v

WebAgent Logs

A Web agent writes in several log files:

An access file that records information about requests to the web agent and responses from the web agent:
$LPF_ROOT_DIR/sg/proxy-<WEBAgent-ID>/logs/access
This access file can be visualized through the WAM console.
An errors file that lists internal errors related to the Web agent:
$LPF_ROOT_DIR/sg/proxy-<WEBAgent-ID>/logs/errors
This errors file can be visualized through the WAM console.
A lpfError file common to all the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfError
A lpfTrace file common to all the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfTrace
Where $LPF_ROOT_DIR is the Web Access Manager server installation directory.

The <WEBAgent-ID> value (like lpfwebagent_<nb>) is returned by the command:

$LPF_ROOT_DIR/bin/lpfgateway -list_local -v

AuthServer Logs

A Web Access Manager authentication server generates several log files: 

An access file that records information about requests to the authentication server and responses from the authentication server:
$LPF_ROOT_DIR/authsrv/server/logs/access
An errors file that lists internal errors related to the authentication server:
$LPF_ROOT_DIR/authsrv/server/logs/errors
A lpfError file that lists all errors encountered by the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfError
A lpfTrace file that gives some debug information about the WAM components:
$LPF_ROOT_DIR/sg/proxy-main/logs/lpfTrace
Where $LPF_ROOT_DIR is the Web Access Manager server installation directory.

EUAServer Logs

A Web Access Manager EUA server generates several log files

An access file that records information about requests to the EUA server and responses from the EUA server:
$LPF_ROOT_DIR/eua/server/logs/access.
An error file that lists internal errors related to the EUA server:
$LPF_ROOT_DIR/eua/server/logs/errors
A lpfError file that lists all errors encountered by the EUA server:
LPF_ROOT_DIR/eua/server/logs/lpfError
A lpfTrace file that gives some debug information about the EUA server:
$LPF_ROOT_DIR/eua/server/logs/lpfTrace
Where $LPF_ROOT_DIR is the Web Access Manager server installation directory.

Administration Server Logs

A Web Access Manager administration server generates several log files:

An access file that records information about requests to the administration server and responses from the administration server:
$LPF_ROOT_DIR/sg/admin-serv/logs/access.
An error file that lists internal errors related to the administration server:
$LPF_ROOT_DIR/sg/admin-serv/logs/errors
A lpfError file that lists all errors encountered by the administration server:
$LPF_ROOT_DIR/sg/admin-serv/logs/lpfError
A lpfTrace file that gives some debug information about the administration server:
$LPF_ROOT_DIR/sg/admin-serv/logs/lpfTrace
Where $LPF_ROOT_DIR is the Web Access Manager server installation directory.

WAM GUI Logs

WAM GUI Traces

GUI Traces (Tools)

GUI Audit Traces (Tools)

IGA Provisioning Logs

E-SSO Interace & Audit

$LPF_ROOT_DIR/wgsw/var/

HAR Logs

SAML Traces

Tomcat Logs