Log size change setting in logs.cfg not working

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

Log size modification not working in NCM 10.1.6, NCM 10.1.8 and NCM 10.1.11
When logs.cfg file located under $VOYENCE_HOME/conf is modified, changes do not take effect after restart of vcmaster service.

Environment

NCM - 10.1.x

Cause

Line #Copyright © [2019] VMware, Inc. All rights reserved. This product is protected by copyright and intellectual property laws in the United States and other countries as well as by international treaties. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. is occupying multiple characters hence change in log size is not taken into consideration in java hibernate.

Resolution

• source /etc/voyence.conf
• Take backup of logs.cfg located at $VOYENCE_HOME/conf
• Open logs.cfg, reduce line #Copyright © [2019] VMware, Inc. All rights reserved. This product is protected by copyright and intellectual property laws in the United States and other countries as well as by international treaties. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents as much as possible.

Example: Recommended to keep line #Copyright © [2019] VMware, Inc. All rights reserved, remove remaining sentences.

• Save and close the file.
• Restart vcmaster service as service vcmaster restart. 
• Make modification to log size and verify.

P.S: Issue is fixed in NCM 10.1.13 version onwards.

Additional Information

Impact/Risks:

Log size cannot be modified hence by default 10 files with 500k size logs will be created in NCM.