ems probe - how to change log size - config key for logsize is not working
search cancel

ems probe - how to change log size - config key for logsize is not working

book

Article ID: 278277

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

In the EMS probe I am unable to change the logsize.

The "logsize" key in Raw Configure is not respected and the log grows beyond what I have configured.

 

Cause

  • In EMS 10.30, this works fine

  • In EMS 10.31, there is a defect which prevents the logsize from changing away from the default 10MB

  • In EMS 10.35+ (shipped with UIM 20.4 CU10) and EMS 23.4.x (shipped with UIM 23.4+) the logsize key does not work but it is possible to use an alternate method

Resolution

If you are using EMS 10.31, upgrade to UIM 23.4 which is available now.  DX UIM 20.4x is no longer supported.

After upgrading, the following steps are needed to change the log size.  By default the logsize will be set to 10MB, and 5 sequential copies will be kept.

1. For the EMS probe go to Raw Configure and check "startup->opt"  for the following string -- add it to the end if it is missing.

  -Dlog4j.configurationFile=file:./log4j2.xml 

2. Now you may edit the log4j2.xml file which is present in the probe folder ($NIM_ROOT\probes\service\ems\log4j2.xml)  and change the value for "SizeBasedTriggeringPolicy" here:

 

Additional Information

Due to the way logs are managed by the probe, if you turn up the "loglevel" key in the ems.cfg, the log may grow beyond the configured limits.  It is recommended to leave the loglevel in ems.cfg set to the default value of 1 to avoid this, and use the settings in the log4j2.xml file to adjust log settings.