Arctera

Cluster goes into STALE_ADMIN_WAIT state during upgrade from VCS 5.1 to 6.1 or later [2850921]

While performing a manual upgrade from VCS 5.1 to VCS 6.1 or later, cluster goes in STALE_ADMIN_WAIT state if there is an entry of DB2udbTypes.cf in main.cf.

Installation of VRTSvcsea package in VCS 5.1 creates a symbolic link for Db2udbTypes.cf file inside /etc/VRTSvcs/conf/config directory which points to /etc/VRTSagents/ha/conf/Db2udb/Db2udbTypes.cf. During manual upgrade, the VRTSvcsea package for VCS 5.1 gets removed, which in turn removes the symbolic link for file Db2udbTypes.cf inside /etc/VRTSvcs/conf/config directory. After the complete installation of VRTSvcsea for VCS 6.1 or later versions, because of absence of file Db2udbTypes.cf inside /etc/VRTSvcs/conf/config, cluster goes into STALE ADMIN WAIT state.

Workaround: Manually copy DB2udbTypes.cf from /etc/VRTSagents/ha/conf/Db2udb directory to the /etc/VRTSvcs/conf/config directory after the manual upgrade before starting HAD.

Cluster goes into STALE_ADMIN_WAIT state during upgrade from VCS 5.1 to 6.1 or later [2850921]

In this article