README VERSION : 1.1 README CREATION DATE : 2012-10-18 PATCH-ID : PHNE_43152 PATCH NAME : VRTSgab 5.1 SP1RP2 BASE PACKAGE NAME : Veritas Group Membership and Atomic Broadcast by Symantec BASE PACKAGE VERSION : VRTSgab 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : hpux1131 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : HANG , PANIC PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:PHNE_43152 2292291 (2292294) pfiles, lsof, procfiles, or truss commands hang in the gablogd daemon. 2411653 (2411651) GAB: Add check for MAX message size in GAB 2858122 (2831283) System got panic on GAB with below: panic string: BAD TRAP: type=31 rp=2a10d4cf530 addr=28 mmu_fsr=0 occurred in module "gab" due to a NULL pointer dereference SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:PHNE_43152 * INCIDENT NO:2292291 TRACKING ID:2292294 SYMPTOM: When you run tracing commands like pfiles, lsof, procfiles, or truss on the gablogd daemon, the command hangs. DESCRIPTION: When you run tracing commands like pfiles, lsof, procfiles, or truss on the gablogd daemon, a signal is issued to gablogd. This signal is blocked because it has called gab ioctl and is waiting for events with the cv_wait() call, which is not interruptible. As a result, the tracing command hangs. RESOLUTION: When gablogd calls gab ioctl, within ioctl, gab calls interruptible wait cv_wait_sig() for mutex conditional variable in ioctl. This call does not block signals on the process which calls gab ioctl. * INCIDENT NO:2411653 TRACKING ID:2411651 SYMPTOM: In the communication between GAB and GAB clients, GAB drops certain packets due to size restrictions and may cause the cluster to hang. DESCRIPTION: This is an enhancement required to ensure that when GAB drops a packet due to size restrictions, GAB logs an error message. In the absence of such an error message, a hung cluster condition may become difficult to troubleshoot. RESOLUTION: Symantec has modified GAB to log an error message indicating the exceeded packet size. For example, the following error message: ---------------------- GAB ERROR V-15-1-20238 Client message size 66613 greater than GAB maximum allowed message size 66560 * INCIDENT NO:2858122 TRACKING ID:2831283 SYMPTOM: Unconfiguring GAB immediately after a network failure may cause the system to panic. On a system with Solaris operating system you may see the following error message: "BAD TRAP: type=31 rp=2a10d4cf530 addr=28mmu_fsr=0 occurred in module "gab" due to a NULL pointer dereference". On other operating systems, you can find "NULL pointer dereference" as part of the error message. DESCRIPTION: In the event of a network issue in a cluster, GAB needs to close all of its ports that are accessible to user-space and kernel-space clients. The order in which the ports close is not defined. This undefined order means that there is no check to ensure that the last port to be closed is the GAB's internal port. So, there is a possibility that the GAB's internal port may close first. And the last port to be closed is another port that may be left open for a transient period. During this period, if you try to unconfigure GAB, the unconfigure program assumes that GAB's internal port is open instead of the other port and LLT is shut down. The other port remains open. Later, whenever GAB tries to access LLT interfaces on behalf of the port that is open the system panics. RESOLUTION: Symantec has added an additional check in the unconfigure program to verify that last port to be closed is the GAB's internal port. If the last port is any other port, the program returns an error. INCIDENTS FROM OLD PATCHES: --------------------------- NONE