VCS Error Message "V-16-10021-5119 LVMLogicalVolume:<resource>:monitor:Specified Volume Group <VG> is not activated" is continuously displayed in the system and agent logs

book

Article ID: 100033536

calendar_today

Updated On:

Description

Error Message

From the System log (/var/adm/syslog/syslog.log):
 
Jan 24 12:34:56  AgentFramework[3045]: VCS ERROR V-16-10021-5119 LVMLogicalVolume::monitor:Specified Volume Group <VG> is not activated


VCS agent log (/var/VRTSvcs/log/LVMLogicalVolume_A.log):
 
2017/01/24 12:34:56 VCS ERROR V-16-10021-5119 LVMLogicalVolume::monitor:Specified Volume Group <VG> is not activated

Cause

This error message was introduced in VCS version 6.0 to inform users of possible LVMLogicalVolume resource misconfigurations. This includes situations when the mandatory attribute "LogicalVolume" is not set correctly. The same message is also reported when the resource is properly configured, but simply offline. This is because the target volume group would not be activated on offline nodes.

These messages do not always indicate an actual problem, and will not affect the cluster functionality in any meaningful way. They may confuse users by flooding the logs, and consuming unnecessary file system space, if there are many LVMLogicalVolume resources configured in the cluster.

Resolution

The VCS LVMLogicalVolume agent behavior has been modified so that the messages regarding non-active volume groups are now tagged as DEBUG rather than ERROR, thereby appearing in the logs only while agent debug logging is enabled.

This change will be included in all future releases of VCS Bundled Agent packages. Contact Veritas Support if a hot fix patch for an existing version is required.

Issue/Introduction

On HP-UX systems running Veritas Cluster Server (VCS) version 6.0, or later, the VCS error message "V-16-10021-5119 LVMLogicalVolume:<resource>:monitor:Specified Volume Group <VG> is not activated" is reported for each offline LVMLogicalVolume resource, per every monitoring cycle, in the system log as well as the agent log.

Additional Information

ETrack: 3907040