Setting the size limit on the CATALOGSYNC.LOG file

Products

• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

The NX_ROOT\catalogsync.log file does not appear to adhere to the settings in the LOG4J Properties file

The file keeps growing and does not roll over.

log4j.appender.catalogsynclog.File=D:/PROGRA1/CA/SERVIC1/log/catalogsync.log
log4j.appender.catalogsynclog=org.apache.log4j.RollingFileAppender
log4j.appender.catalogsynclog.MaxBackupIndex=30
log4j.appender.catalogsynclog.MaxFileSize=10MB
log4j.appender.catalogsynclog.layout=org.apache.log4j.PatternLayout
log4j.appender.catalogsynclog.layout.ConversionPattern=%d{MM/dd HH:mm:ss.SSS} [%t] %-5p %c{1} %L %m %n

# Default log level for CatalogSync Daemon
log4j.logger.com.ca.ServicePlus.CatalogSync=INFO, catalogsynclog

This causes the file to keep growing and consume disk space.

Environment

Service Desk Manager 17.3 and 17.4

All Supported Operating Systems

Resolution

Starting with 17.3 RU13, a newer version of the LOG4J2 version is used.

The CATALOGSYNC.LOG file leverages the LOG4J properties.

1. Make a backup of the current NX_ROOT\\site\cfg\log4j.properties file

2. Edit the CATALOGSYNC section of the NX_ROOT\\site\cfg\log4j.properties file so it looks like below

log4j.appender.catalogsynclog.File=D:/PROGRA~1/CA/SERVIC~1/log/new_catalogsync.log
log4j.appender.catalogsynclog.MaxBackupIndex=7
log4j.appender.catalogsynclog.MaxFileSize=10MB

3. Save changes to the file

4. Stop the SDM service

5. Move or delete the current CATALOGSYNC.LOG file

6. Restart the SDM service