STALE_ADMIN_WAIT is reported by Veritas Cluster Server

book

Article ID: 100032216

calendar_today

Updated On:

Description

Error Message

STALE_ADMIN_WAIT

Cause

Possible reasons for this include:

1. Stopping the 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

If the administrator is confident that a valid configuration exists on a particular node, that 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 > (Figure 2).

Note: refers to the system which has the valid configuration file. 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.
 

Figure 2

Screenshot of using hasys -force <system_name> 

 

 

 

Issue/Introduction

VCS (Veritas Cluster Server) node status is reported as "STALE_ADMIN_WAIT" (Figure 1).
  Figure 1

Screenshot of STALE_ADMIN_WAIT error