An error is reported in the Veritas Cluster Server (VCS) engine log (engine_A.log).
VCS ERROR V-16-2-13067 (hostname) Agent is calling clean for resource(resource_name) because the resource became OFFLINE unexpectedly, on its own.
VCS ERROR V-16-2-13073 (hostname) Resource(resource_name) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number n of n) the resource.
This error appears when the monitoring procedure for an agent determines that a monitored resource is no longer running. As the error indicates, the resource stopped outside of VCS, meaning that the offline status was not initiated by the cluster. In this case, the cluster is only detecting that the resource being monitored is offline and is reporting it. Upon detecting an unexpected offline status, the resource will usually fault and the cluster may initiate a service group failover. Whether or not a failover occurs depends on the settings for the service group, whether or not the group is frozen and the status of other nodes.
The reason why a resource stops outside of VCS varies. In some cases, a process that is being monitored may have been intentionally killed by a user, unaware that this will trigger a cluster fault. It may be helpful to review the logs for the operating system to determine the reason why the resource stopped.
What to do when there is the unexpected VIP address unable to fail over with error messages "ERROR V-16-2-13067" ?