ERROR V-292-2-149 AND ERROR V-292-1-88 logged during CFSMount resource offline

Problem

Veritas Cluster Server (VCS) Asynchronous Monitoring Framework (AMF) modules logs ERROR V-292-2-149 and ERROR V-292-1-88 logged during CFSMount resource offline

Error Message

In syslog:

kernel: AMF ERROR V-292-1-88 Cannot delete event (rid 11) in reaper 'CFSMount'. The event not found.

In VCS engine log (/var/VRTSvcs/log/engine_A.log):

VCS NOTICE V-16-1-10300 Initiating Offline of Resource CFS_test (Owner: Unspecified, Group: testsg) on System testsys01
VCS INFO V-16-1-10305 Resource CFS_test (Owner: Unspecified, Group: testsg) is offline on testsys01 (VCS initiated)
VCS INFO V-16-10031-20903 (testsys01)CFSMount:CFS_test:imf_register: /opt/VRTSamf/bin/amfregister -u -r CFSMount -g CFS_test
VCS INFO V-16-2-13716 (testsys01) Resource(CFS_test): Output of the completed operation (imf_register)
==============================================
AMF amfregister ERROR V-292-2-149 Cannot unregister event: no rid -1 found
==============================================

Cause

During resource online, the agent does an online registration for the resource with AMF.  When this resource is offlined by VCS, it executes appropriate commands to offline the resource along with the commands to unregister the corresponding AMF event, so that the data structures in AMF are cleaned up. 

The error is caused due to the sequence of events. An AMF event gets triggered once the commands that brings the resource offline gets completed. Later when the unregister command reaches AMF, it throws an error saying event is not in Active state and hence cannot delete the event (AMF ERROR V-292-1-88), thus failing the unregister command from agent (AMF amfregister ERROR V-292-2-149).

Solution

These messages can be safely ignored as it doesn't affect the agent behaviour. The unregister commands are used for cleaning up the AMF data structures, which has already been initiated by event trigger.

This issue is being tracked through incident Symantec internal incident e2521908 and is planned to be addressed in 6.1 version.

Terms of use for this information are found in Legal Notices.