VERITAS Cluster Server command "haconf -makerw" hangs, unable to make cluster configuration writable.
In the event you are unable to make your cluster configuration writable as a result of the "haconf -makerw" command, verify that the cluster is in ReadOnly mode:
# haclus -display | grep ReadReadOnly 1
If you make the cluster configuration writable, the ReadOnly value will be set to "0":
# haconf -makerw
# haclus -display | grep ReadReadOnly 0
GLOBALCOUNTER CHECKGlobalCounter: this counter increases incrementally by one for each counter interval. Verify that the GlobalCounter value is increasing every 5 seconds on all nodes in the cluster:
# while true> do
> haclus -display | grep GlobalCounter
> sleep 5
> done
Sample output:
GlobalCounter 73
GlobalCounter 74
GlobalCounter 75
GLOBALCOUNTER NOT INCREASINGImportant: A loss of service may occur, if you are unable to switch the critical ServiceGroups to another node.
In the event that the GlobalCounter value is not increasing, try to fail all critical ServiceGroups to another node in the cluster.
Once the required ServiceGroups have been switched, kill the "had" process on an idle node in the cluster:
# ps -ef | grep had
# kill The "hashadow" process should attempt to respawn the "had" daemon again.
If related to this incident, "had" will not restart and eventually the system may panic and crash; this is intentional.
Following the reboot of the panicked node, the GlobalCounter value should start to increment on all the other nodes in the cluster.
GlobalCounter InformationVERITAS Cluster Server uses the GlobalCounter attribute to measure the time it takes to shut down a system.
By default, the GlobalCounter attribute is updated every five seconds. This default value, combined with the 60-second default value of ShutdownTimeout, means that if system goes down within twelve increments of GlobalCounter, it will be treated as a fault.
The default value of GlobalCounter increment can be modified by changing the CounterInterval attribute. If you increase the CounterInterval attribute to exceed five seconds, consider increasing the default value of the ShutdownTimeout attribute as well.