Enportal/5.5/admin/system administration/Log Files - Revision history

imported>Mike.berman: /* enPortal CRS Log Configuration */

2014-11-29T04:43:27Z

enPortal CRS Log Configuration

@@ Line 122: / Line 122: @@
 ** handlers.crsFile.maxSize=1024000
 * Masking controls are also provided for controlling the verbosity of what is written to a number of the log files.  The mask uses bits to turn on/off various information, and can be the sum of any of (0,1,2,4,8).
 ==Submitting Log Files to Technical Support==

imported>Mike.berman at 04:46, 28 July 2014

2014-07-28T04:46:15Z

← Older revision		Revision as of 04:46, 28 July 2014
Line 125:		Line 125:
	==Submitting Log Files to Technical Support==		==Submitting Log Files to Technical Support==

	For information on submitting a support ticket, see the [[~~Technical_Support~~\|Technical Support]] page.		For information on submitting a support ticket, see the [[support/technical_support\|Technical Support]] page.

	For instructions on sending information to the Technical Support team, see the [[~~Submitting_Files_For_Technical_Support~~\|Submitting Files for Technical Support]] page.		For instructions on sending information to the Technical Support team, see the [[support/submitting_files_for_technical_support\|Submitting Files for Technical Support]] page.

imported>Jason.nicholls: 1 revision

2014-07-10T05:08:59Z

1 revision

← Older revision	Revision as of 05:08, 10 July 2014
(No difference)

imported>Jason.nicholls: 1 revision

2013-12-19T15:17:45Z

1 revision

New page

[[Category:enPortal 5.5]]
{{DISPLAYTITLE:enPortal Log Files}}

enPortal provides various log files to assist you with monitoring and troubleshooting. This article details the log files that are provided.

== enPortal Log Files ==

=== Location ===

enPortal maintains log files primarily in the following location:
* <tt>[INSTALL_HOME]/server/logs</tt>

=== Summary ===

The following table summarizes each log file and the information it provides:

{| class="wikitable"
|+ align="bottom" |''enPortal Log Files''
|-
! Log File
! Description
|-
| error.log.[date]
| Subset of appBoard.log, containing only Error messages
|-
| ldap.log.[date]
| Messages related to LDAP
|-
| localhost_access_log.[date].txt
| Detail of all individual user HTTP requests made to the system. Note: enPortal does not log access to specific individual Widgets or Boards, but could enable debugging of all data queries so that those could be audited.
|-
| session.log.[date]
| Detail of all User sessions in the system, including: 
- Timestamp 
- Role 
- Domain 
- Username 
- Transaction Result 
- Session ID 
- Total number of concurrent logins 
- Total number of concurrent logins in the User's Domain 
- IP address
|-
| system.log.[date]
| All errors, warnings, and informational messages related to the enPortal server. including: 
- Expired license errors 
- Items requested by the application that could not be located on the server 
- User session information
|-
| tomcat.log.[day_of_week]
| The standard log file for the Tomcat web application container
|}

=== Rotation ===

Log file rotation is configured in the <tt>config.properties</tt> file under <tt>[INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/</tt>, including settings such as the following:

<code>[ini,N]
# Log cleanup settings
logwatch.error.prefix=${logger.logs.path}/error.log
logwatch.error.numberToKeep=7
logwatch.error.compress=true

logwatch.system.prefix=${logger.logs.path}/system.log
logwatch.system.numberToKeep=7
logwatch.system.compress=true

logwatch.session.prefix=${logger.logs.path}/session.log
logwatch.session.numberToKeep=7
logwatch.session.compress=true

logwatch.ldap.prefix=${logger.logs.path}/ldap.log
logwatch.ldap.numberToKeep=7
logwatch.ldap.compress=true

logwatch.access.prefix=${logger.logs.path}/localhost_access_log
logwatch.access.numberToKeep=7
logwatch.access.compress=true
logwatch.access.skiplast=true

# Log cleanup settings
logwatch.appBoard.prefix=${logger.logs.path}/appBoard.log
logwatch.appBoard.numberToKeep=7
logwatch.appBoard.compress=true
</code>

This background job can be used to clean up any files that always have the same prefix. It assumes either the files are names: (<logname>, <logname><suffix1>, <logname><suffix2>) or (<logname><suffix1>, <logname><suffix2>, and so on). In the first case, the one without the suffix is assumed to be the current log, while in the latter a flag “skiplast” is used to not archive/delete the last (in alpha-numeric ordering). This is only used for the tomcat access log.

<tt>numberToKeep</tt> does not include the current log, and compress will put the old log in a file named the same with ".zip" added. The process runs every 30 minutes to look for old files that need to be processed.

=== Configuration ===

The standard log files above are written using the log4j library and can be configured through the enportal/WEB-INF/classes/log4j.xml file. For information on configuring log4j, please see: http://en.wikipedia.org/wiki/Log4j#Configuration

Of note, the following settings will change the verbosity of the log files and how long each daily log is kept.

<code>[xml,N]
<param name="Threshold" value="INFO"/>
<param name="MaxBackupIndex" value="15"/>
</code>

Threshold can have values from most verbose to least of: TRACE, DEBUG, INFO, WARN, ERROR and FATAL.

The MaxBackupIndex is the number of daily logs to keep for each log file type, which is 15 by default.

=== enPortal CRS Log Configuration ===

The custom CRS log for the enPortal proxy is not handled by log4j. This log should only be enabled when specific CRS debugging is being performed. The log files are not rotated, but there are some controls you can implement to manage the size and content of the CRS log.

* Example: Observe the following lines in [INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/logger-crs.properties:
** handlers.crsFile.class=com.edgetech.util.logger.FileHandler
** handlers.crsFile.fileName=crs.log
* You could add the following line to logger-crs-custom.properties to limit the size of this particular log file to about 1 MB:
** handlers.crsFile.maxSize=1024000
* Masking controls are also provided for controlling the verbosity of what is written to a number of the log files. The mask uses bits to turn on/off various information, and can be the sum of any of (0,1,2,4,8).

==Submitting Log Files to Technical Support==

For information on submitting a support ticket, see the [[Technical_Support|Technical Support]] page.

For instructions on sending information to the Technical Support team, see the [[Submitting_Files_For_Technical_Support|Submitting Files for Technical Support]] page.