README VERSION : 1.1 README CREATION DATE : 2012-09-20 PATCH-ID : 5.1.133.000 PATCH NAME : VRTSvcsag 5.1 SP1RP3 BASE PACKAGE NAME : Veritas Cluster Server Bundled Agents by Symantec BASE PACKAGE VERSION : VRTSvcsag 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : rhel5_x86_64,rhel6_x86_64,sles10_x86_64,sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER 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 INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 1787018 (1919382) Mount agent fails to detect the mounted file system with trailing "/". 2619254 (2593173) DiskGroup agent do not detect serial split-brain situation. 2728805 (2728802) Apache agent should work correctly even if Mountpoint for httpd directory is not present on the failover node. 2788082 (2788059) System did not panic when "PanicSystemOnDGLoss" is set. 2818051 (2731133) When NFSRestart resource is brought offline, it forcefully stops automountd process. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:5.1.133.000 * INCIDENT NO:1787018 TRACKING ID:1919382 SYMPTOM: The Mount agent fails to detect the mounted file system if either the BlockDevice or MountPoint attribute contains a trailing forward slash ("/"). DESCRIPTION: If the value configured in either the BlockDevice or MountPoint attribute contains a trailing forward slash, the Mount agent online entry point does not remove it. The monitor entry point fails to record the entry in the mount table because the monitor entry point removes the trailing forward slash before searching the mount table. RESOLUTION: Symantec has modified the Mount agent code to remove the trailing forward slash while mounting the file system. * INCIDENT NO:2619254 TRACKING ID:2593173 SYMPTOM: Online entry point of DiskGroup agent do not detect the serial split-brain situation and fail to log warning about it. DESCRIPTION: Diskgroup agent check for incorrect return code of the vxdg import command expected during serial split-brain situation and thus do not recognize the serial split-brain situation. RESOLUTION: Symantec has now modified the DiskGroup agent to look for correct return code of vxdg import command during serial split-brain situation. * INCIDENT NO:2728805 TRACKING ID:2728802 SYMPTOM: If the directory or filename specified as part of 'httpdDir' attribute does not exist on the cluster node, the Apache agent cannot monitor the HTTP server correctly. And Apache agent logs error with following message id V-16-10061-20495. DESCRIPTION: As part of validations Apache agent checks existence of file or directory specified as part of 'httpdDir' attribute. However on a node where apache resource is offline, it is possible that even the mountpoint for httpd directory may not be present, in such a case Apache agent should report the resource state as offline instead of logging an error message. RESOLUTION: Symantec has update the Apache agent to report the resource state as offline when the directory or file specified as part of 'httpdDir' attribute is not present on the system. In such an event, during process level monitoring agent looks for the Apache processes assuming the value specified as part of 'httpdDir' attribute in following ways: 1 A directory name containing 'httpd' binary 2 Complete path to the binary name itself * INCIDENT NO:2788082 TRACKING ID:2788059 SYMPTOM: System did not panic on loss of storage connectivity, even after the PanicSystemOnDGLoss attribute of DiskGroup resource is set to 1. DESCRIPTION: If a resource other than DiskGroup in a service group detects loss of storage connectivity, then that resource faults and the DiskGroup resource is brought offline. The offline entry point of DiskGroup agent does not check the state of the underlying disk group before deporting it. RESOLUTION: Symantec has modified the DiskGroup agent code to check the state of the underlying disk group before deporting. This ensures that if the offline entry point is called for DiskGroup resource due to loss of storage connectivity and PanicSystemOnDGLoss attribute of DiskGroup resource is set to 1, then the system will panic. * INCIDENT NO:2818051 TRACKING ID:2731133 SYMPTOM: When NFSRestart resource is brought offline, it forcefully stops automountd process. DESCRIPTION: When NFSRestart resource is brought offline, it terminates NFS daemons. It looks for 'mountd' daemon in running processes and stops the matching ones. It also matches 'automountd' process and subsequently forcefully stops it. RESOLUTION: The NFSRestart Agent behaviour is updated in VCS to do a strict matching for process name, which means only stop 'mountd' process. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::5.1.132.000 * Incident no::2253441 Tracking ID ::2253345 Symptom::The IP agent fails to go offline when NetMask is changed outside of VCS control for an online VCS IP resource. Description::The IP agent makes use of IP address and Netmask value pair to perform online and offline operations. When the Netmask value on the interface is changed outside of VCS control, the VCS expected value of Netmask mismatches with the netmask value present on the device and hence offline operation fails. Resolution::Symantec has modified the VCS IP agent to log a warning which prompts to update the NetMask attribute value if the Netmask value is changed outside of VCS control. * Incident no::2330045 Tracking ID ::2195569 Symptom::If you set the ControlMode attribute of a RemoteGroup resource to OnlineOnly or MonitorOnly, then the resource fails to go offline when it loses connectivity with the remote cluster. Description::The RemoteGroup resource tries to connect to the remote cluster even after the agent has invoked its offline entry point. If the connection to the remote cluster is not available, the resource goes into the UNKNOWN state and prevents the service group from going offline. Resolution::Symantec has modified the RemoteGroup resource to check for the remote cluster connection only when the resource is ONLINE. This fix is valid only if you set the ControlMode attribute of a RemoteGroup resource to OnlineOnly or MonitorOnly. * Incident no::2330047 Tracking ID ::2313917 Symptom::The monitor entry point used to return offline if the systems configured in the "Client" and "OtherClients" attribute has upper case letters, and the exports configured correctly. Description::The monitor entry point of the Share resource used to perform case sensitive compare the systems configured as "Client" or "OtherClients". This used to return the resource state as offline if the systems have upper case letters. Resolution::The monitor entry point of the Share resource now performs case insensitive compare of systems, so that even if the systems have upper case/lower case letters, they do not matter. * Incident no::2330055 Tracking ID ::2275514 Symptom::The VCS Mount agent does not support the file system type 'xfs'. Description::This is an enhancement requirement, not a bug. Resolution::Symantec has modified the Mount agent to support the file system type 'xfs'. As a result, when you create a Mount resource, you can now set the FSType attribute to 'xfs'. * Incident no::2366701 Tracking ID ::2371667 Symptom::1. The Application agent returns the resource state as UNKNOWN if: a. You store the Monitor program on shared disks and a VCS node is unable to access the shared disks, then the Application agent cannot monitor an application on that node. Moreover, VCS cannot fail-over applications on such a node. b. The Monitor program returns UNIX style values, that is, "0" in case of success and "1" in case of failure. The Application agent does not handle these values. 2. The Application agent does not validate the user. If a configured user is not present on the system, the Application agent does not work properly. 3. The Application agent does not check whether the home directory for a configured user is set or not. Description::1. The Application agent checks for the existence of the Monitor program on a node. On nodes that cannot access the shared disk, this check fails. As a result, the agent marks the status of the application as UNKNOWN, on such nodes. Moreover, if an application goes down on an active node, then the application cannot fail over to nodes where the status of the application is UNKNOWN. 2. The Application agent can handle only the following set of values returned by the monitor program: 100 --> OFFLINE 101 to 110 --> ONLINE Any other value --> UNKNOWN. If a monitor program returns "0" as success and "1" as failure, the Application agent returns the resource state as UNKNOWN. 3. If an invalid user is configured in the "User" attribute of an application resource (that is, the user is not present on the system), the Application agent fails to handle such a user, and may terminate abruptly. 4. Linux does not allow a user to be created without specifying the home directory. The Application agent does not validate such a user for the home directory. If any such user is configured as the "User" attribute for an application resource, the Application agent fails to monitor the configured application. Resolution::Symantec has done following modifications in the Application agent: 1. Instead of checking for the existence of the Monitor program, the Application agent checks for non-null values of the attributes associated with the Start/Stop/Monitor programs. As a result, for nodes that cannot access the shared disks, the agent now reports the application as OFFLINE, only if the previous state of the application was OFFLINE, and the application was not waiting for a state change. In all other cases, for nodes that cannot access the shared disks, the agent reports the state of the application as UNKNOWN. 2. The Application agent validates the user for their existence and the home directory. If the configured user is not valid, or the home directory is not set for a user, the Application agent reports the resource state as UNKNOWN. 3. The Application agent handles the standard UNIX style return values, that is, "0" for success and "1" for failure, and now reports the resource state based on the following set of values: 100 or 1 --> OFFLINE 101 to 110 or 0 --> ONLINE Any other value --> UNKNOWN. * Incident no::2372483 Tracking ID ::2372481 Symptom::SambaServer agent dumps core on VCS 5.1SP1RP1 Description::SambaServer agent tries to close an open file pointer twice in a particular code path which leads to a core dump. This is a rare issue which can be reproduced by overwriting the samba pid file (/var/run/smbd.pid or /var/run/samba/smbd.pid) with a pid of any other running process. Resolution::Symantec has modified the VCS SambaServer agent to remove the extra call to close an open file pointer. * Incident no::2381083 Tracking ID ::2274275 Symptom::When a VCS IP or IPMultiNIC resource comes online, broadcast address of 0.0.0.0 gets set for the respective virtual interface if no broadcast option is configured in Options or IPOptions attribute. Description::When no broadcast address is configured as a part of Options or IPOptions attribute in VCS IP or IPMultiNIC resource configuration, the agent does not pass any broadcast argument to ip command while plumbing the IP address. A default broadcast of 0.0.0.0 gets set for the virtual interface in this case. Resolution::Symantec has modified the IP and IPMultiNIC agents to check if a broadcast option is specified in Options or IPOptions attribute. If not, IP and IPMultiNIC agents set the default broadcast value on the interface. * Incident no::2383495 Tracking ID ::2283125 Symptom::The VCS Mount agent does not support the file system type 'ext4'. Description::This is an enhancement requirement, not a bug. Resolution::Symantec has modified the Mount agent to support the file system type 'ext4'. As a result, when you create a Mount resource, you can now set the FSType attribute to 'ext4'. * Incident no::2405780 Tracking ID ::2405788 Symptom::The NIC resource in VCS 5.1SP1RP1 fails to fault when Mii is set to 0 and broadcast replies from localhost are enabled on the machine. Description::The NIC agent monitor function performs a broadcast ping if Mii attribute is set to 0 and no value is configured in the NetworkHosts attribute. It checks the return code of this broadcast ping command and returns Online in case of success. This fails to report the correct state in case of cable pull if the broadcast is enabled on the node. In this case, the command succeeds and the agent returns the state as Online. Resolution::Symantec has modified the VCS NIC agent to not report the resource state based on the return code of the broadcast ping command. It now proceeds directly to packet count test after the broadcast ping command to decide the resource state. * Incident no::2423990 Tracking ID ::2423984 Symptom::In a VCS Application agent configuration, if the administrator specifies a user name that is invalid on a system, then the agent may not correctly function on that system. Description::In the above case, the agent may display error messages or abruptly terminate. Resolution::Symantec has modified the Application agent to validate the user name configured as an User attribute. If the user name is not valid on a system, the agent reports the state of a configured resource on that system as UNKNOWN. * Incident no::2483964 Tracking ID ::2199045 Symptom::Even if a configured process is running correctly, the process agent monitor entry point may report the related resource to be offline. Description::The process agent monitor entry point executes the ps command to determine the status of a configured process and verify the process arguments. The output of the command is written in a thread-specific file. Meanwhile, VCS also redirects the process output to the same thread-specific file. As a result the agent framework receives a garbled output and the monitor entry point incorrectly reports the process resource to be offline. Resolution::As a workaround, Symantec has modified the process agent online entry point to redirect the process output to /dev/null. This ensures that the monitor entry point reports the correct status. * Incident no::2509515 Tracking ID ::2511463 Symptom::The IP agent offline entry point fails to remove the IP address from the interface when (1) No NetMask attribute is specified, (2) Options attribute is configured and none of IPOptions and IPRoouteOptions is configured, and (3) a Class B or class C IP adress is configured in the Address attribute. Description::The agent uses the ifconfig command to plumb the ip address in the above conditions. In this case, depending on the class of the Address - A ,B or C, the ifconfig command plumbs address with netmask value of 255.0.0.0, 255.255.0.0 and 255.255.255.0 respectively. But the offline EP always uses ip command and netmask values of 255.0.0.0 if no NetMask attribute value is configured. This leads to failure of offline and clean EPs for class B and C addresses. Resolution::Symantec has modified the IP agent offline and clean entry points to derive the default netmask value configured by ifconfig command in online entry point and use the same value in offline and clean operations. * Incident no::2528475 Tracking ID ::2528470 Symptom::The preonline_ipc trigger functionality of VCS, that performs certain checks before bringing a group online, does not work for resources other than IP resources. Description::This is a known limitation. There is an enhancement requirement to extend preonline_ipc trigger support to other resources types. Resolution::Symantec has enhanced the preonline_ipc trigger to support the following types of resources on a system: IP and IPMultiNIC. * Incident no::2514514 Tracking ID ::2523471 Symptom::If the 'httpd' binary or the 'ab' binary is not present at the location that you specified in the 'httpdDir' attribute, the Apache agent cannot perform detail monitoring or start the HTTP server. Description::To start the HTTP server, the Apache agent uses the 'httpd' binary from the location specified in the 'httpdDir' attribute. To perform detail monitoring, the agent uses the Apache Benchmarking utility or 'ab' binary from the same location. If the binaries in that location use a slightly different name, such as say 'httpd2', the agent does not recognize the binary, and therefore cannot perform the desired actions. Resolution::Symantec has enhanced the 'httpdDir' attribute such that you can specify the full path of the binary (including the binary name). If you specify only the directory name, the agent assumes the default binary name 'httpd'. If the Apache Benchmarking binary in the specified directory does not use the default name, then the agent recognizes the alternative binary name 'ab2', and performs detail monitoring.