Log Files

User Manager and Web Server Logs

Log files for the User Manager and Web Server logs are created in the logs folders:

<install path>\UserManager\logs

<install path>\WebServer\logs

Logging configuration can be modified using logback.xml or container.conf, depending on which log you want to modify. Instructions are provided in these files.

Note: Edits you make to logback.xml and container.conf need to be repeated each time you apply a hotfix or upgrade your Reflection for Secure IT software.

The files are located in the conf folders:

<install path>\UserManager\conf

<install path>\WebServer\conf

The following log files are available for both the Web Server and the User Manager:

server.log
server.yyyymmdd.log

The server log includes primary server logging. This file rolls over daily. The file called server.log captures log information for the current day. By default rolled-over log files include the date in year-month-date format, and logs are deleted after three days. Only the first 15 lines of an exception are shown.

To modify the server log settings, use logback.xml.

 

console.yyyymmdd.log

The console log has startup and runtime details. By default console logs roll over daily and include the date in year-month-date format. These files are not deleted.

To modify console log rollover, logging levels, and log deletion, use container.conf.

 

debug.log

Debug logging is not enabled by default. A debug.log file is created by default, but is not used unless you enable debug logging.

To enable debug logging, edit logback.xml. The lines to edit and for instructions for making the change are under LOG SET UP.

 

The following additional log is available for the User Manager:

directory.log

 

The directory log contains logging related to LDAP directory transactions. Rollover configuration is the same as the server log, however rolled over logs are usually not present. Rollover is triggered when messages are written to the log files, and this log is rarely used.

To modify the directory log settings, use logback.xml.

 

 

Note: By default, the server log files and debug log files (when debug logging is enabled) roll over daily and are deleted after three days. This helps ensure that disk space is not used up by large, accumulating log files. If you alter the configuration to keep these files for a longer period, you should monitor the files and/or move them to another server to ensure that sufficient disk space is always available.

Reflection for Secure IT Server Logs

The Reflection for Secure IT server supports two methods of logging: to the Windows Event Viewer and/or to a text log file. To configure logging, use the Reflection for Secure IT console (Attachmate Reflection > Reflection SSH Server Configuration).

Windows Event Viewer

Logging to the Event Viewer is enabled by default.

To view the Event Viewer log from the Reflection for Secure IT console, click the toolbar button, or go to View > Event Viewer.

To modify the Event Viewer log level, go to Configuration > Logging > Event logging.

 

Text file logs

Logging to text files is not enabled by default.

To enable logging to a text file, set the log level, specify a log file directory, and configure rollover, go to Configuration > Logging > Debug logging.

To view the log file from the Reflection for Secure IT console, click the toolbar button, or go to View > Event Latest Debug Log File.