Error Message

2012/05/15 00:00:53 VCS WARNING V-16-1-10485 Excessive delay between successive
calls to GAB heartbeat (8 seconds)

SYMPTOM:
GAB terminates the HAD process.

 

DESCRIPTION:
HAD maintains a periodic heartbeat with GAB. HAD also does a
periodic self-test to check to control the interval between successive
heartbeats. The self-test is perfomed using the Unix alarm mechanism which
sends SIGALRM to the HAD process. The SIGALRM handler invokes the syslog()
system call which can cause the HAD process to go into an infinite sleep. Thus,
HAD stops to heartbeat with GAB and GAB terminates the HAD process.

 

RESOLUTION:
Veritas has removed the syslog() system call and changed the
signal handler function of HAD such that it writes a message to
had_hb_delay.txt file in the log directory.
 

This refers to Incident 2811722.

Please download the patch 'Veritas Cluster Server 5.1 RP2 Hot Fix 1' from

 https://sort.Veritas.com/patch/detail/4139

                          * * * READ ME * * *
               * * * Veritas Cluster Server 5.1 RP2 * * *
                         * * * Hot Fix 1 * * *
                         Patch Date: 2012-07-06


This document provides the following information:

   * PATCH NAME
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Cluster Server 5.1 RP2 Hot Fix 1


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvcs


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 5.1
   * Veritas Storage Foundation Cluster File System 5.1
   * Veritas Storage Foundation High Availability 5.1
   * Veritas Storage Foundation Cluster File System for Oracle RAC 5.1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL5 i686
RHEL5 x86-64


INCIDENTS FIXED BY THE PATCH
----------------------------
This patch fixes the following Veritas incidents:

Patch ID: 5.1.002.001

* 2811722 (Tracking ID: 2746816)
 

INSTALLING THE PATCH
--------------------
To install the patch perform the following steps on all nodes in the
VCS cluster:

1. Stop VCS on the cluster node.
2. Install the patch.
3. Restart VCS on the node.

Stopping VCS on the cluster node
--------------------------------
To stop VCS on the cluster node:

1. Ensure that the "/opt/VRTS/bin" directory is included in your PATH environment variable so that you can execute all the VCS commands. For more information, refer to the Veritas Cluster Server Installation Guide.

2. Verify that the version of VRTSvcs is 5.1RP2.

3. Persistently freeze all the service groups:
   # haconf -makerw
   # hagrp -freeze [group] -persistent
   # haconf -dump -makero

4. Stop the cluster on all nodes. If the cluster is writable, you may close the configuration before stopping the cluster.

   On any node, run the following command to stop the cluster:
   # hastop -all -force

5. Verify that the cluster is stopped :
   # hasys -state

6. make sure that both the had and hashadow processes are stopped.

7. Stop the VCS CmdServer :
   # CmdServer -stop

8. Copy the /etc/VRTSvcs/conf/config/types.cf file to
   /etc/VRTSvcs/conf/config/types.cf.orig.

9. Copy the /etc/VRTSvcs/conf/config/main.cf file to
   /etc/VRTSvcs/conf/config/main.cf.orig.


Installing the patch
--------------------
To install the patch:

1. Log in as superuser on the system where you are installing the patch.

2. Uncompress the patch that you downloaded from Veritas.

3. Change the directory to the uncompressed patch location.

4. Install the patch:
   # rpm -Uvh VRTSvcs-5.1.002.001-RP2HF1_RHEL5.i686.rpm

5. After the installtion completes, verify that the patch is installed.
   # rpm -q VRTSvcs
   You will find the following output on display with the patch installed properly:
    VRTSvcs-5.1.002.001-RP2HF1_RHEL5   

Restarting VCS on the cluster node
----------------------------------
To restart VCS on the cluster node:

1. Copy the new types.cf file from /etc/VRTSvcs/conf to
   /etc/VRTSvcs/conf/config:
   # cp /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config/types.cf

2. Verify the configuration:
   # hacf -verify config

3. Restore the vcsenv file as it got backed up due to the upgrade
  # mv /opt/VRTSvcs/bin/vcsenv.rpmsave /opt/VRTSvcs/bin/vcsenv

4. Start the cluster services on all cluster nodes.

   First start VCS on the node where you copied the new types.cf file:
   # hastart

   On all the other nodes, start VCS by issuing the hastart command after the first node's state changes to LOCAL_BUILD or RUNNING.

5. Unfreeze all the service groups:
   # haconf -makerw
   # hagrp -unfreeze [group] -persistent
   # haconf -dump -makero


REMOVING THE PATCH
------------------
1. Stop VCS on the node by following the steps in the section "Stopping
   VCS on the cluster node".

2. Remove the patch:
   #  rpm -e VRTSvcs
   
3. After the removal completes, verify that the patch has been removed from all the system in the cluster. On each system type:
   # rpm -qa | grep VRTSvcs
   The package VRTSvcs should not be displayed, which confirms that the package is removed.