VCS ERROR V-16-1-10600 Cannot connect to VCS engine reported for Veritas Cluster Server for Windows
Article ID: 100001133
Updated On:
Description
Error Message
Upon running the command "hasys -state" would report below error
VCS ERROR V-16-1-10600 Cannot connect to VCS engine
Resolution
1. Check the Services Control Panel to see if "Veritas High Availability Engine Startup" service is in the "Starting" state.
2. Check Application Event Viewer for event ID 11306 or Event with message as "Did not receive cluster membership, manual intervention may be needed for seeding"
3. Use the following command to determine the status of the cluster:
C:\>hastatus -sum or
C:\>hasys -state
By default, the Global Atomic Broadcast (GAB) is configured to seed the cluster after all nodes in the cluster have joined the cluster. If all nodes go down for any reason and one node does not come online, the cluster will not start.
The minimum number of nodes required to allow HAD to be started is defined in gabtab.txt. The file is located under the following path: \Program Files\VERITAS\comms\gab\gabtab.txt
Note: This file contains a line that defines the "seeding" requirement, which is the number of nodes for this cluster that must be available before HAD will start.
If the "Veritas High Availability Engine Startup" service is in the "Starting" state, the following command can be used to manually seed GAB after killing the had.exe from the Tasks list.
From the Command Line, type:
C:\>gabconfig -c -x
C:\>hastart
C:\>hasys -state
If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING.
Issue/Introduction
For a Veritas Cluster Server (VCS) on Windows platform, there may be instances when trying to start the "Veritas High Availability Daemon (HAD)" service, it would fail to start or get stuck in "Starting" phase
Was this article helpful?
Yes
No
Powered by
