Bug in HACMP 5.2

[ferbrown]

Hi,
When preparing a data migration a I configured a new disk with its VG, LV and new file system under smitty lvm commands.

There is a hacmp cluster defined but i didnt touch anything before this issue.

When I tried to umount de the new file system to varyoff and varyon the vg inn the other node I was not able to wait. After two minutes waiting for umounting it I made a CTRL-C and then the cluster went down.
This is the error reported:

LABEL: TS_STOP_ST
IDENTIFIER: 6D19271E
Date/Time: Wed Apr 4 13:24:35 DFT 2007
Sequence Number: 70581
Node Id: SAP2
Class: O
Type: INFO
Resource Name: topsvcs
Description
Topology Services daemon stopped
Probable Causes
Daemon stopped by SRC
Daemon stopped by signal
User Causes
Daemon stopped by user
Recommended Actions
Confirm that this is desirable
Detail Data
DETECTING MODULE
rsct,comm.C,1.139,622
Topology Services daemon stopped by:
Signal SIGTERM
--------------------------------------------
Resource Name: grpsvcs
Description
Group Services daemon stopped
Probable Causes
Daemon stopped by SRC
Daemon stopped by signal
User Causes
Daemon stopped manually by user
Recommended Actions
Check that Group Services daemon is stopped
Detail Data
DETECTING MODULE
RSCT,SRCSocket.C,1.56,454
ERROR ID
6/uIVc.mfs24/muq/FUEd8....................
REFERENCE CODE
DIAGNOSTIC EXPLANATION
Received signal[SIGTERM]. Converted to normal stop


Has anyone experienced this issue?
Why does it have to convert to normal stop if it only was a ctrl-c to stop umounting a new vg, logical volume and filesystem not under hacmp resources or configuration...

 

[khalidaaa]

Opps! I think Something happened to the resource group daemon when you did that! I don't see why this happened but the HACMP cluster is sensitive to changes (but i didn't think that it is that sensitive!)

any way, did you check the /tmp/hacmp.out for errors?

Regards,
Khalid