STALE_ADMIN_WAIT
Article ID: 100019342
Updated On:
Resolution
This customer has a 2-node cluster which will not start, the master node enters STALE_ADMIN_WAIT. The customer shut down this newly created cluster node to investigate.
The STALE_ADMIN_WAIT condition is entered after one, or all of the following occurs:
hastart is executed on the master node
hacf finds a .stale in the /etc/VRTSvcs/conf/config directory, or discovers no valid configration to pass to HAD in order to start cluster.
The customer removed the .stale file in their /etc/VRTSvcs/conf/config directory, ran hacf -verify to verify the syntax of main.cf. When hacf -verify returned no error messages, the customer executed hastart on the master node, and the cluster was able to start without incident.
The STALE_ADMIN_WAIT condition is entered after one, or all of the following occurs:
hastart is executed on the master node
hacf finds a .stale in the /etc/VRTSvcs/conf/config directory, or discovers no valid configration to pass to HAD in order to start cluster.
The customer removed the .stale file in their /etc/VRTSvcs/conf/config directory, ran hacf -verify to verify the syntax of main.cf. When hacf -verify returned no error messages, the customer executed hastart on the master node, and the cluster was able to start without incident.
Issue/Introduction
STALE_ADMIN_WAIT
Was this article helpful?
Yes
No
Powered by
