After upgrade to 5.0 MP3, CFSMountAgent restarts as it is not sending alive messages. CFSMountAgent keeps dumping cores.

Article:TECH65830  |  Created: 2008-01-09  |  Updated: 2010-01-25  |  Article URL http://www.symantec.com/docs/TECH65830
Article Type
Technical Solution

Product(s)

Environment

Problem



After upgrade to 5.0 MP3, CFSMountAgent restarts as it is not sending alive messages. CFSMountAgent keeps dumping cores.

Error



2008/12/03 11:41:45 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/CFSMount/CFSMountAgent for resource type CFSMount successfully started at Wed Dec 03 11:41:45 2008
2008/12/03 11:42:55 VCS NOTICE V-16-1-10024 Agent CFSMount has not sent startup message since Wed Dec 03 11:41:45 2008 .. Restarting

Solution




Changes introduced to CFSMountAgent in VRTScavf 5.0 MP3 is not multi-thread safe, thus causes Agent to core dump.

Symantec Engineering has decided to revert back the changes in upcoming VRTScavf 5.0MP3 patches.

Use the following work-around on each cluster node until VRTScavf 5.0MP3-RP1 patch is applied:

# cd /opt/VRTSvcs/bin/CFSMount
# mv CFSMountAgent CFSMountAgent.orig
# ln -s /opt/VRTSvcs/bin/ScriptAgent CFSMountAgent

Kill the current running CFSMountAgent, and VCS will restart it a few minutes later:

# ps -efa | grep CFSMountAgent
# kill <CFSMountAgent-pid>


If desired, the CFSMount agent can be restarted on each node rather than waiting for VCS.

    # haagent -start CFSMount -sys VCS_Node

This problem is applicable to Linux and Solaris platforms.
Symantec recommends to install 5.0MP3RP1 for Solaris and 5.0MP3RP2 for Linux, or later patch versions, to fix this issue.


Supplemental Materials

SourceETrack
Value1448517
DescriptionCFSMountAgent restarted as it dumped core and not sending alive messages


Legacy ID



316172


Article URL http://www.symantec.com/docs/TECH65830


Terms of use for this information are found in Legal Notices