Controlling wrapper.log file size and rotation in CA Performance Manager installations

Document ID : KB000032449
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Each of the four CA Performance Manager (CAPM) services have a wrapper.log file that contains a great deal of logging information. These are critical to the proper operation of CAPM as well as for use in trouble shooting problems with the system or its services.

The wrapper.log file(s) in CA Performance Manager (CAPM) can potentially grow to a size that is going to impact the systems functionality. This could potentially cause a down system situation due to a full disk if left unchecked and not managed in some way.

The following instructions provide configuration details to customize the size the logs can grow to before they are rotated, as well as how many logs are stored before old ones are deleted to make space for new ones.

 

Solution:

The four services involved are:

  • caperfcenter_console
  • caperfcenter_devicemanager
  • caperfcenter_eventmanager
  • caperfcenter_sso

Each writes to its own unique wrapper.log file that can be found in the location:

$CAPM_HOME/CA/PerformanceCenter/<service>/logs

Assuming a default install path of /opt is in use, the four directories that store the wrapper.log are:

  • /opt/CA/PerformanceCenter/PC/logs (represents the caperfcenter_console service)
  • /opt/CA/PerformanceCenter/DM/logs (represents the caperfcenter_devicemanager service)
  • /opt/CA/PerformanceCenter/EM/logs (represents the caperfcenter_eventmanager service)
  • /opt/CA/PerformanceCenter/sso/logs (represents the caperfcenter_sso service)

The wrapper.log file size and rotation (count of logs stored) for each service is defined in the wrapper.conf file present for each service. This file is found in:

$CAPM_HOME/CA/PerformanceCenter/<service>/conf

Assuming a default install path of /opt is in use, the four directories that store the wrapper.conf are:

  • /opt/CA/PerformanceCenter/PC/conf(represents the caperfcenter_console service)
  • /opt/CA/PerformanceCenter/DM/conf (represents the caperfcenter_devicemanager service)
  • /opt/CA/PerformanceCenter/EM/conf (represents the caperfcenter_eventmanager service)
  • /opt/CA/PerformanceCenter/sso/conf (represents the caperfcenter_sso service)

Within the wrapper.conf file we are able to edit to configuration properties found in the section titled:

#********************************************************************

# Wrapper Logging Properties

#********************************************************************

Within that section these are the properties that control file size and rotation:

 # Maximum size that the log file will be allowed to grow to before

#  the log is rolled. Size is specified in bytes.  The default value

#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or

#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=0

 

# Maximum number of rolled log files which will be allowed before old

#  files are deleted.  The default value of 0 implies no limit.

wrapper.logfile.maxfiles=0

NOTE: It is recommended that no other properties be modified without the direction of CA Support.

We recommend setting wrapper.logfile.maxfiles value to a maximum of 5 to keep 5 rotated logs available for review if needed.

Additional Note: As of the r2.7 release the default configuration for the wrapper.logfile.maxfiles is set to 5. To configure the log rollup strategy the same as the r2.7 release set that value to 5.

The wrapper.logfile.maxsize setting is something determined by the end user. If we're keeping the recommended 5 logs keep in mind that setting will be multiplied by 5. If you set it to 10 megabytes, and 5 files, you will have five 10 megabyte files present. Determine the size of the files in relation to available disk space to ensure they aren't set to keep so much logging that the disk becomes full.

Make the changes to the necessary wrapper.log file(s) and save the changes. Ensure ONLY those settings are changed. If other settings are mistakenly edited, the service may not continue to function as designed.

After saving the changes to the wrapper.conf file the service tied to the edited file will need to be restarted to read the wrapper.conf changes into memory. To restart the services run these commands as the root or sudo root user that owns the installation.

Stop the services:

service <serviceName> stop

Start the services:

service <serviceName> start

The full commands for each service stop would be:

service caperfcenter_console stop

service caperfcenter_devicemanager stop

service caperfcenter_eventmanager stop

service caperfcenter_sso stop

The full commands for each service start would be:

service caperfcenter_console stop

service caperfcenter_devicemanager stop

service caperfcenter_eventmanager stop

service caperfcenter_sso stop

If editing just one wrapper.conf for one service, stop and restart only that service as needed.

If editing wrapper.conf files for all four services at once, make sure to stop and restart the four services in the proper order. That order is as follows:

Stop Order

  1. caperfcenter_console
  2. caperfcenter_devicemanager
  3. caperfcenter_eventmanager
  4. caperfcenter_sso

Start Order

  1. caperfcenter_sso
  2. caperfcenter_eventmanager
  3. caperfcenter_devicemanager
  4. caperfcenter_console