VERITAS Cluster Server nodes status displays as STALE_ADMIN_WAIT.

book

Article ID: 100015384

calendar_today

Updated On:

Cause

STALE_ADMIN_WAIT (Figure 1) indicates the system has a stale configuration and there is no other system in a state of RUNNING from which to retrieve a configuration.

Figure 1
 
 
Possible reasons for this include:
1. Stopping the High Availability Daemon (HAD) service on all nodes without closing the configuration (i.e. using hastop -all -force ), or rebooting all cluster nodes at the same time.
2. An invalid configuration file on all nodes.

Resolution

Check for syntax errors in main.cf using the hacf -verify command.
  1. Cd to the main.cf directory
  2. Run hacf -verify . to show any errors.
  3. Resolve the syntax errors, then use hasys -force SYSTEM_NAME to start VCS on the node where the main.cf syntax error was corrected.
 
If the administrator is confident that a valid configuration exists on a particular node the node can be "forced" to read its own configuration file. It is recommended that the existing configurations on all nodes be backed up using the hagetcf -conf command.
Once a backup exists, execute the following command: hasys -force SYSTEM_NAME (Figure 2).
Note: SYSYEM_NAME must be spelled in all capital letters.
 
Figure 2
 
Node name refers to the system which has the valid configuration file. Ensure that the node name has the same case sensitivity as the actual computer name. This command will force the node specified to read its local configuration file. If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING. All other nodes would then show as REMOTE_BUILD and transition to RUNNING.
 
 

 

Issue/Introduction

VERITAS Cluster Server nodes status displays as STALE_ADMIN_WAIT.
Powered by Wolken Software