Error Message

03:03:47 VCS WARNING V-16-1-17053 Notifier:Mail server specified does not support SMTP VRFY command. Email user cannot be verified
00:49:29 VCS WARNING V-16-1-17031 Notifier:activated signal 6

The agent is crashing due to an incorrect attribute defined in the types.cf. This can be caused by a manual edit of types.cf or an issue during an upgrade.

1.) Ensure if the cluster is running and forms a part of the same cluster membership as the other nodes
# gabconfig -a
# hastatus -sum

2.) Freeze all the Service Groups persistently
# hagrp -freeze -persistent

3.) Dump and save the existing configuration
# haconf -dump -makero

4.) Stop the Cluster services with the "-force" option to ensure that the production is not affected
# hastop -all -force

5.) Confirm that the VCS services have stopped
# hastatus -sum
# ps -elf | grep -i had

6.) Compare the types.cf file from the 5.0 MP3 installer with the existing /etc/VRTSvcs/conf/config/types.cf and check the timestamps and cksum:
# diff /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config/types.cf
# ls -l /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config/types.cf
# cksum /etc/VRTSvcs/conf/types.cf
# cksum /etc/VRTSvcs/conf/config/types.cf

The timestamp on the /etc/VRTSvcs/conf/types.cf file should be of the correct version of the upgraded version. This can be confirmed also by quickly looking up and referencing with the Agent definitions in the Bundled Agent Reference Guide for the version of the product that we have upgraded to.

7.) Once verified that the correct file has not been updated to /etc/VRTSvcs/conf/config/types.cf, manually backup the original file and copy the correct file of the version to the config directory
# cd /etc/VRTSvcs/conf/config
# cp types.cf types.cf.orig
# cp /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config/types.cf

8.) Check for syntax errors in the VCS configuration. Only when this step has succeeded without any output error/warning should we proceed to start VCS successfully, or we have to make more changes into /etc/VRTSvcs/conf/config/main.cf or /etc/VRTSvcs/conf/config/types.cf or any other specific /etc/VRTSvcs/conf/config/*.cf for specific agents having a separate *.cf file.

# hacf -verify /etc/VRTSvcs/conf/config