Serviceguard
cancel
Showing results for 
Search instead for 
Did you mean: 

ServiceGuard on SLES8, package don't mount VG

peyrol
Occasional Advisor

ServiceGuard on SLES8, package don't mount VG

How i can verify the VG mounted by the package when i start it?

I have a package with 2 VGs:
VG[0]=database
VG[1]=files

LV[0]=/dev/database/LVOL_database; FS[0]=/database; FS_TYPE[0]="reiserfs"; FS_MOUNT_OPT[0]="-o rw";
FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]="";
LV[1]=/dev/files/LVOL_warmbackup; FS[1]=/files/WARMBACKUP; FS_TYPE[1]="reiserfs"; FS_MOUNT_OPT[1]="-o rw";
FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]="";



The package start fine, but no mount point will be created, and i can't have access to it.

In the /var/log/message i see only this:

cmomd[8201]: Request to start package OA_pkg on meditel.
cmcld: Request from root on node 192.168.1.1 connected to tel1 as root via cmomd(pid 8201) to start the package OA_pkg.
cmcld: Request from node tel1 to start package OA_pkg on node tel1.
cmcld: Executing '/opt/cmcluster/conf/OA_pkg/OA_START.sh start' for package OA_pkg, as service PKG*48642.
cmcld: Service PKG*48642 terminated due to an exit(0).
cmcld: Started package OA_pkg on node tel1.
cmomd[8201]: Successfully started package OA_pkg.

Do you have any ideas to solve this issue?

the VG are on a MSA1000 disk array on 2 separate LUN.

Thanks by advance.

Didier
12 REPLIES
melvyn burnard
Honored Contributor

Re: ServiceGuard on SLES8, package don't mount VG

What does the package log say?
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
njia_1
Trusted Contributor

Re: ServiceGuard on SLES8, package don't mount VG

Hi there,

According my understanding, any mount points need to be created first.

I am confused by what you said "package started fine, but no mount point will be created"

thanks
peyrol
Occasional Advisor

Re: ServiceGuard on SLES8, package don't mount VG

Hi,

All mount point is created before start the package.

the package log files say nothing.

Where i can change the level of log files in the package?

thanks by advance.
didier
melvyn burnard
Honored Contributor

Re: ServiceGuard on SLES8, package don't mount VG

What do you mean "package log says nothing" ?

If the package has activated on the node, there will be a pkg.cntl.log file in the package directory.

Do these file systems mount using command line?
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
peyrol
Occasional Advisor

Re: ServiceGuard on SLES8, package don't mount VG

Hi,

i do mount /dev/database/LVOL_database /database

and the result is:

/dev/cciss/c0d0p2 on / type reiserfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/cciss/c0d0p5 on /boot type reiserfs (rw)
/dev/cciss/c0d0p10 on /home type reiserfs (rw)
/dev/cciss/c0d0p6 on /opt type reiserfs (rw)
/dev/cciss/c0d0p11 on /product type reiserfs (rw)
/dev/cciss/c0d0p7 on /tmp type reiserfs (rw)
/dev/cciss/c0d0p8 on /usr type reiserfs (rw)
/dev/cciss/c0d0p9 on /var type reiserfs (rw)
shmfs on /dev/shm type shm (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/database/LVOL_database on /database type reiserfs (rw)


its good.

So in the package folder, i don't have the pkg.cntl.log file.

Where i can specify to the package to create it (version of SG A11.15).

Thanks
melvyn burnard
Honored Contributor

Re: ServiceGuard on SLES8, package don't mount VG

Serviceguard creates the log file automatically in the package subdirectory of the node it is starting on, if not already there, and then continually appends to it every time it starts and stops on that node.
I suggest you provide an ll of the package directory
Also supply the package configuration file.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
peyrol
Occasional Advisor

Re: ServiceGuard on SLES8, package don't mount VG

hi,

sorry for the delay.

ll:

meditel1:/opt/cmcluster/conf/OA_pkg # ll
total 57
drwxr-xr-x 2 root root 208 Dec 21 08:17 .
drwxrwxrwx 10 root root 840 Dec 21 08:15 ..
-rwxr-xr-x 1 root root 52 Dec 20 17:32 OA_START.sh
-rw-rw-rw- 1 root root 41 Dec 21 08:17 OA_START.sh.log
-rwxr-xr-x 1 root root 52 Dec 20 17:32 OA_STOP.sh
-rwxr-xr-x 1 root root 6780 Dec 21 07:46 OA_pkg.config
-rwxr-xr-x 1 root root 36472 Dec 21 07:46 OA_pkg.sh


OA_pkg.config:

# **********************************************************************
# ****** HIGH AVAILABILITY PACKAGE CONFIGURATION FILE (template) *******
# **********************************************************************
# ******* Note: This file MUST be edited before it can be used. ********
# * For complete details about package parameters and how to set them, *
# * consult the MC/ServiceGuard manuals. *******************************
# **********************************************************************

# Enter a name for this package. This name will be used to identify the
# package when viewing or manipulating it. It must be different from
# the other configured package names.

PACKAGE_NAME OA_pkg

# Enter the package type for this package.
# Currently the only valid value for PACKAGE_TYPE is:
#
# FAILOVER package runs on one node at a time and if a failure
# occurs it can switch to an alternate node.
#
# Examples : PACKAGE_TYPE FAILOVER (default)
#

PACKAGE_TYPE FAILOVER


# Enter the failover policy for this package. This policy will be used
# to select an adoptive node whenever the package needs to be started.
# The default policy unless otherwise specified is CONFIGURED_NODE.
# This policy will select nodes in priority order from the list of
# NODE_NAME entries specified below.
#
# The alternative policy is MIN_PACKAGE_NODE. This policy will select
# the node, from the list of NODE_NAME entries below, which is
# running the least number of packages at the time this package needs
# to start.

FAILOVER_POLICY CONFIGURED_NODE


# Enter the failback policy for this package. This policy will be used
# to determine what action to take when a package is not running on
# its primary node and its primary node is capable of running the
# package. The default policy unless otherwise specified is MANUAL.
# The MANUAL policy means no attempt will be made to move the package
# back to its primary node when it is running on an adoptive node.
#
# The alternative policy is AUTOMATIC. This policy will attempt to
# move the package back to its primary node whenever the primary node
# is capable of running the package.

FAILBACK_POLICY MANUAL


# Enter the names of the nodes configured for this package. Repeat
# this line as necessary for additional adoptive nodes.
#
# NOTE: The order is relevant.
# Put the second Adoptive Node after the first one.
#
# Example : NODE_NAME original_node
# NODE_NAME adoptive_node
#
# If all nodes in the cluster are to be specified and order is not
# important, "NODE_NAME *" may be specified.
#
# Example : NODE_NAME *

NODE_NAME meditel1
NODE_NAME meditel4
NODE_NAME meditel3
NODE_NAME meditel2



# Enter the value for AUTO_RUN. Possible values are YES and NO.
# The default for AUTO_RUN is YES. When the cluster is started the
# package will be automatically started. In the event of a failure the
# package will be started on an adoptive node. Adjust as necessary.
#
# AUTO_RUN replaces obsolete PKG_SWITCHING_ENABLED.

AUTO_RUN YES


# Enter the value for NODE_FAIL_FAST_ENABLED.
# Possible values are YES and NO.
# The default for NODE_FAIL_FAST_ENABLED is NO. If set to YES,
# in the event of a failure, the cluster software will halt the node
# on which the package is running. All SYSTEM_MULTI_NODE packages must have
# NODE_FAIL_FAST_ENABLED set to YES. Adjust as necessary.

NODE_FAIL_FAST_ENABLED NO


# Enter the complete path for the run and halt scripts. In most cases
# the run script and halt script specified here will be the same script,
# the package control script generated by the cmmakepkg command. This
# control script handles the run(ning) and halt(ing) of the package.
# Enter the timeout, specified in seconds, for the run and halt scripts.
# If the script has not completed by the specified timeout value,
# it will be terminated. The default for each script timeout is
# NO_TIMEOUT. Adjust the timeouts as necessary to permit full
# execution of each script.
# Note: The HALT_SCRIPT_TIMEOUT should be greater than the sum of
# all SERVICE_HALT_TIMEOUT values specified for all services.

RUN_SCRIPT /opt/cmcluster/conf/OA_pkg/OA_START.sh
RUN_SCRIPT_TIMEOUT NO_TIMEOUT
HALT_SCRIPT /opt/cmcluster/conf/OA_pkg/OA_STOP.sh
HALT_SCRIPT_TIMEOUT NO_TIMEOUT


# Enter the SERVICE_NAME, the SERVICE_FAIL_FAST_ENABLED and the
# SERVICE_HALT_TIMEOUT values for this package. Repeat these
# three lines as necessary for additional service names. All
# service names MUST correspond to the SERVICE_NAME[] entries in
# the package control script.
#
# The value for SERVICE_FAIL_FAST_ENABLED can be either YES or
# NO. If set to YES, in the event of a service failure, the
# cluster software will halt the node on which the service is
# running. If SERVICE_FAIL_FAST_ENABLED is not specified, the
# default will be NO.
#
# SERVICE_HALT_TIMEOUT is represented as a number of seconds.
# This timeout is used to determine the length of time (in
# seconds) the cluster software will wait for the service to
# halt before a SIGKILL signal is sent to force the termination
# of the service. In the event of a service halt, the cluster
# software will first send a SIGTERM signal to terminate the # service. If the service does not halt, after waiting for the
# specified SERVICE_HALT_TIMEOUT, the cluster software will send
# out the SIGKILL signal to the service to force its termination.
# This timeout value should be large enough to allow all cleanup
# processes associated with the service to complete. If the
# SERVICE_HALT_TIMEOUT is not specified, a zero timeout will be
# assumed, meaning the cluster software will not wait at all
# before sending the SIGKILL signal to halt the service.
#
# Example: SERVICE_NAME DB_SERVICE
# SERVICE_FAIL_FAST_ENABLED NO
# SERVICE_HALT_TIMEOUT 300
#
# To configure a service, uncomment the following lines and
# fill in the values for all of the keywords.
#
SERVICE_NAME cmresservice_OA_pkg
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 120


# Enter the network subnet name that is to be monitored for this package.
# Repeat this line as necessary for additional subnet names. If any of
# the subnets defined goes down, the package will be switched to another
# node that is configured for this package and has all the defined subnets
# available.
# The subnet names could be IPv4 or IPv6. The network subnet
# names that are to be monitored for this package could be a mix
# of IPv4 or IPv6 subnet names

SUBNET 192.168.1.0


OA_pkg.sh:

#"(#) A.11.15.01 $Date: 10/14/03 $"
# **********************************************************************
# * *
# * HIGH AVAILABILITY PACKAGE CONTROL SCRIPT (template) *
# * *
# * Note: This file MUST be edited before it can be used. *
# * *
# * You must have bash version 2 installed for this script to work *
# * properly. Also required is the arping utility available in the *
# * iputils package. *
# * *
# **********************************************************************

# The PACKAGE and NODE environment variables are set by
# ServiceGuard at the time the control script is executed.
# Do not set these environment variables yourself!
# The package may fail to start or halt if the values for
# these environment variables are altered.

# Test to see if the shell is POSIX compliant. On RH6.2 /bin/bash (which
# is the default shell, ie. /bin/sh is sym linked to it) is version
# 1.x and does not support some of the features that this control
# script uses (specifically arrays). Bash version 2.x does support
# arrays and is included as /bin/bash2. We will first check to see of
# the shell that invoked us (/bin/bash) will work (in case someone
# changed it, if not we will use /bin/bash2.
#
# At SG installation time we checked to make sure
# that either /bin/bash will work with this control script or
# that /bin/bash2 is installed. The SG rpm would not install unless
# one of these conditions are true. On RH7.x the default /bin/bash
# shell is version 2 and thus will work fine.
sglinux[0]=1 >/dev/null 2>&1
if [ $? -gt 0 ]; then
# not a valid shell
# will invoking /bin/bash2
exec /bin/bash2 -c "$0 $*"
exit 1
fi

. ${SGCONFFILE:=/etc/cmcluster.conf}

# UNCOMMENT the variables as you set them.

# Set PATH to reference the appropriate directories.
PATH=$SGSBIN:/bin:/sbin:/usr/bin:/usr/sbin

#
# REMOTE DATA REPLICATION DEFINITION
# Specify the remote data replication method.
# Leave the default, DATA_REP="none", if remote data replication is not used.
#
# If remote data replication is used for the package application data, set
# the variable DATA_REP to the data replication method. The current supported
# method is "clx".
#
DATA_REP="none"
#

# MD (RAID) CONFIGURATION FILE
# Specify the configuration file that will be used to define
# the md raid devices for this package.
#
# For example:
# RAIDTAB="/usr/local/cmcluster/conf/raidtab.sg"
#
#RAIDTAB="" # MD (RAID) COMMANDS
# Specify the method of activation and deactivation for md.
# Leave the default (RAIDSTART="raidstart", "RAIDSTOP="raidstop") if you want
# md to be started and stopped with default methods.
#
RAIDSTART="raidstart -c ${RAIDTAB}"
RAIDSTOP="raidstop -c ${RAIDTAB}"

# VOLUME GROUP ACTIVATION
# Specify the method of activation for volume groups.
# Leave the default ("VGCHANGE="vgchange -a y") if you want volume
# groups activated in default mode.
#
# VGCHANGE="vgchange -a y"
VGCHANGE="vgchange -a y" # Default

# VOLUME GROUPS
# Specify which volume groups are used by this package. Uncomment VG[0]=""
# and fill in the name of your first volume group. You must begin with
# VG[0], and increment the list in sequence.
#
# For example, if this package uses your volume groups vg01 and vg02, enter:
# VG[0]=vg01
# VG[1]=vg02
#
# The volume group activation method is defined above. The filesystems
# associated with these volume groups are specified below. Ensure all the
# mds in the volume groups are included in the md activation above.
#
VG[0]="database"
VG[1]="files"

# MULTIPLE DEVICES
# Specify which md devices are used by this package. Uncomment MD[0]=""
# and fill in the name of your first multiple device. You must begin
# with MD[0], and increment the list in sequence. The md devices are
# defined in the RAIDTAB file specified above.
#
# For example, if this package uses multiple devices md0 and md1,
# enter:
# MD[0]=/dev/md0
# MD[1]=/dev/md1
#
#MD[0]=""

# FILESYSTEMS
# The filesystems are defined as entries specifying the logical
# volume, the mount point, the file system type, the mount,
# umount and fsck options.
# Each filesystem will be fsck'd prior to being mounted.
# The filesystems will be mounted in the order specified during package
# startup and will be unmounted in reverse order during package
# shutdown. Ensure that volume groups referenced by the logical volume
# definitions below are included in volume group definitions.
#
# Specify the filesystems which are used by this package. Uncomment
# LV[0]=""; FS[0]=""; FS_TYPE[0]=""; FS_MOUNT_OPT[0]="";
# FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]="" and fill in
# the name of your first logical volume, filesystem, type, mount,
# umount and fsck options for the file system.
# You must begin with LV[0], FS[0],
# FS_TYPE[0], FS_MOUNT_OPT[0], FS_UMOUNT_OPT[0], FS_FSCK_OPT[0]
# and increment the list in sequence.
#
# Valid types for FS_TYPE are 'ext2' and 'reiserfs'.
#
# For example, if this package uses the following:
# logical volume: /dev/vg01/lvol1 /dev/vg01/lvol2
# mount point: /pkg1a /pkg1b
# filesystem type: ext2 reiserfs
# mount options: read/write read/write
#
# Then the following would be entered:
# LV[0]=/dev/vg01/lvol1; FS[0]=/pkg1a; FS_TYPE[0]="ext2";
# FS_MOUNT_OPT[0]="-o rw"; FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]="";
#
# LV[1]=/dev/vg01/lvol2; FS[1]=/pkg1b; FS_TYPE[1]="reiserfs";
# FS_MOUNT_OPT[1]="-o rw"; FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]="";
#
LV[0]="/dev/database/LVOL_database"; FS[0]="/database"; FS_TYPE[0]="reiserfs"; FS_MOUNT_OPT[0]="-o rw";
FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]="";
LV[1]="/dev/files/LVOL_warmbackup"; FS[1]="/files/WARMBACKUP"; FS_TYPE[1]="reiserfs"; FS_MOUNT_OPT[1]="-o rw";
FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]="";

# FILESYSTEM UNMOUNT COUNT
# Specify the number of unmount attempts for each filesystem during package
# shutdown. The default is set to 1.
#
FS_UMOUNT_COUNT=1

# FILESYSTEM MOUNT RETRY COUNT.
# Specify the number of mount retrys for each filesystem.
# The default is 0. During startup, if a mount point is busy
# and FS_MOUNT_RETRY_COUNT is 0, package startup will fail and
# the script will exit with 1. If a mount point is busy and
# FS_MOUNT_RETRY_COUNT is greater than 0, the script will attempt
# to kill the process(s) responsible for the busy mount point
# and then mount the file system. It will attempt to kill user and
# retry mount, for the number of times specified in FS_MOUNT_RETRY_COUNT.
# If the mount still fails after this number of attempts, the script
# will exit with 1.
# NOTE: If the FS_MOUNT_RETRY_COUNT > 0, the script will execute
# "fuser -kuv" to freeup busy mount point.
#
FS_MOUNT_RETRY_COUNT=0

# CONCURRENT FSCK OPERATIONS
# Specify the number of concurrent fsck processes to allow during package
# startup. Setting this value to an appropriate number may improve the
# performance while checking a large number of file systems in the package.
# If the specified value is less than 1, the script defaults it to 1 and
# proceeds with a warning message in the package control script logfile.
CONCURRENT_FSCK_OPERATIONS=1

# CONCURRENT MOUNT AND UMOUNT OPERATIONS
# Specify the number of concurrent mounts and umounts to allow during
# package startup or shutdown.
# Setting this value to an appropriate number may improve the performance
# while mounting or un-mounting a large number of file systems in the package.
# If the specified value is less than 1, the script defaults it to 1 and
# proceeds with a warning message in the package control script logfile.
CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS=1

# IP ADDRESSES
# Specify the IP and Subnet address pairs which are used by this package.
# Uncomment IP[0]="" and SUBNET[0]="" and fill in the name of your first
# IP and subnet address. You must begin with IP[0] and SUBNET[0] and
# increment the list in sequence.
#
# For example, if this package uses an IP of 192.10.25.12 and a subnet of
# 192.10.25.0 enter:
# IP[0]=192.10.25.12
# SUBNET[0]=192.10.25.0 # (netmask=255.255.255.0)
#
# Hint: the subnet can be obtained by AND masking the IP address and the
# netmask values from "ifconfig" command.
#
# IP/Subnet address pairs for each IP address you want to add to a subnet
# interface card. Must be set in pairs, even for IP addresses on the same
# subnet.
#
IP[0]=10.10.166.49
SUBNET[0]=10.10.164.0

# HA APPLICATION SERVER
# Enable or disable a High Availability application server that is used for
# this package. Some examples of the HA Servers are Network File System
# (NFS), Apache Web Server, and SAMBA (CIFS) Server.
#
# If you plan to use one of the HA server toolkits to run an application server,
# you need to set the HA_APP_SERVER value to either "pre-IP" or "post-IP" in
# order to enable this control script to check and run the Toolkit Interface
# Script (toolkit.sh) in the package directory. The interface script will call
# the toolkit main script to verify, start, and stop the server daemons.
#
# If you set the HA_APP_SERVER to "pre-IP", the application will be started
# BEFORE adding the package IP address(es) to the system. Application servers
# such as NFS and SAMBA are better to be started before the system provides
# external connections (activate package IP addresses). Therefore, at the time
# the clients connect to the system, the application server is
# ready for service.
#
# If you set the HA_APP_SERVER to "post-IP", the application will be started
# AFTER adding the package IP address(es) to the system. Application servers
# such as Apache Web Server will check the existing IP when the server starts.
# These applications will not be started if the IP has not been added to the
# system.
#
#Uncomment one the following lines as needed:
#
#HA_APP_SERVER="pre-IP"
#HA_APP_SERVER="post-IP"

# SERVICE NAMES AND COMMANDS.
# Specify the service name, command, and restart parameters which are
# used by this package. Uncomment SERVICE_NAME[0]="", SERVICE_CMD[0]="",
# SERVICE_RESTART[0]="" and fill in the name of the first service, command,
# and restart parameters. You must begin with SERVICE_NAME[0], SERVICE_CMD[0],
# and SERVICE_RESTART[0] and increment the list in sequence.
#
# For example:
# SERVICE_NAME[0]=cmresserviced_pkg1
# SERVICE_CMD[0]="/usr/local/cmcluster/bin/cmresserviced /dev/md0" # SERVICE_RESTART[0]="" # Will not restart the service.
#
# SERVICE_NAME[1]=pkg1a
# SERVICE_CMD[1]="/usr/bin/X11/xclock -display 192.10.25.54:0"
# SERVICE_RESTART[1]="" # Will not restart the service.
#
# SERVICE_NAME[2]=pkg1c
# SERVICE_CMD[2]="/bin/ping 127.0.0.1"
# SERVICE_RESTART[2]="-R" # Will restart the service an infinite
# number of times.
#
# Note: No environmental variables will be passed to the command, this
# includes the PATH variable. Absolute path names are required for the
# service command definition. Default shell is /bin/sh.
#
SERVICE_NAME[0]=cmresservice_ORACLE_pkg
SERVICE_CMD[0]="/usr/local/cmcluster/bin/cmresservice /dev/sda1 /dev/sdb2"
SERVICE_RESTART[0]=""


# START OF CUSTOMER DEFINED FUNCTIONS

# This function is a place holder for customer define functions.
# You should define all actions you want to happen here, before the service is
# started. You can create as many functions as you need.
#
function customer_defined_run_cmds
{
# ADD customer defined run commands.
: # do nothing instruction, because a function must contain some command.
/opt/cmcluster/conf/ORACLe_pkg/ORACLE_START.sh start
test_return 51
}

# This function is a place holder for customer define functions.
# You should define all actions you want to happen here, before the service is
# halted.
#
function customer_defined_halt_cmds
{
# ADD customer defined halt commands.
: # do nothing instruction, because a function must contain some command.
/opt/cmcluster/conf/ORACLe_pkg/ORACLE_STOP.sh stop
test_return 52
}

# END OF CUSTOMER DEFINED FUNCTIONS


melvyn burnard
Honored Contributor

Re: ServiceGuard on SLES8, package don't mount VG

So you DO have a package log:
-rwxr-xr-x 1 root root 52 Dec 20 17:32 OA_START.sh
-rw-rw-rw- 1 root root 41 Dec 21 08:17 OA_START.sh.log <<<<<<<<<<-rwxr-xr-x 1 root root 52 Dec 20 17:32 OA_STOP.sh
-rwxr-xr-x 1 root root 6780 Dec 21 07:46 OA_pkg.config
-rwxr-xr-x 1 root root 36472 Dec 21 07:46 OA_pkg.sh


But this shows the problem!!

You have a package config file: OA_pkg.config
In this file you have the package start/stop script as:

RUN_SCRIPT /opt/cmcluster/conf/OA_pkg/OA_START.sh

HALT_SCRIPT /opt/cmcluster/conf/OA_pkg/OA_STOP.sh


But these are NOT your package start scripts according to what you show above. This SHOULD read:
/opt/cmcluster/conf/OA_pkg/OA_pkg.sh

It is that file you define your package stop and start including mounting the file systems!

But in that script you also have a problem, as you have the following as your user defined run command:
/opt/cmcluster/conf/ORACLe_pkg/ORACLE_START.sh start

This should be /opt/cmcluster/conf/OA_pkg/OA_sh.start I believe.
The same for the halt command.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
peyrol
Occasional Advisor

Re: ServiceGuard on SLES8, package don't mount VG

hi ,

I do the modification, the /var/log/messages:

Dec 21 09:01:20 meditel1 cmcld: Online Config - Successfully modified package OA_pkg with id 63751.
Dec 21 09:01:20 meditel1 cmclconfd[18089]: Updated file /opt/cmcluster/conf/cmclconfig for node meditel1.rnd.gemplus.com (length = 29324).
Dec 21 09:01:31 meditel1 cmomd[18502]: Request to connect as root from root@192.168.1.1.
Dec 21 09:01:32 meditel1 cmomd[18502]: Request to start package OA_pkg on meditel.
Dec 21 09:01:32 meditel1 cmcld: Request from root on node 192.168.1.1 connected to meditel1 as root via cmomd(pid 18502) to start the package OA_pkg.
Dec 21 09:01:32 meditel1 cmcld: Request from node meditel1 to start package OA_pkg on node meditel1.
Dec 21 09:01:32 meditel1 cmcld: Executing '/opt/cmcluster/conf/OA_pkg/OA_pkg.sh start' for package OA_pkg, as service PKG*63751.
Dec 21 09:01:46 meditel1 kernel: reiserfs: found format "3.6" with standard journal
Dec 21 09:01:46 meditel1 kernel: reiserfs: enabling write barrier flush mode
Dec 21 09:01:46 meditel1 kernel: reiserfs: using ordered data mode
Dec 21 09:01:46 meditel1 kernel: reiserfs: checking transaction log (device lvm(58,0)) ...
Dec 21 09:01:46 meditel1 kernel: for (lvm(58,0))
Dec 21 09:01:46 meditel1 kernel: Using r5 hash to sort names
Dec 21 09:01:46 meditel1 kernel: reiserfs: found format "3.6" with standard journal
Dec 21 09:01:46 meditel1 kernel: reiserfs: enabling write barrier flush mode
Dec 21 09:01:46 meditel1 kernel: reiserfs: using ordered data mode
Dec 21 09:01:46 meditel1 kernel: reiserfs: checking transaction log (device lvm(58,1)) ...
Dec 21 09:01:46 meditel1 kernel: for (lvm(58,1))
Dec 21 09:01:46 meditel1 kernel: Using r5 hash to sort names
Dec 21 09:01:46 meditel1 CM-OA_pkg[18619]: cmmodnet -a -i 10.10.166.49 10.10.164.0
Dec 21 09:01:46 meditel1 cmclconfd[18087]: The ServiceGuard daemon, /opt/cmcluster/bin/cmcld[18088], died upon receiving signal number 11.
Dec 21 09:01:47 meditel1 cmsrvassistd[18111]: The cluster daemon aborted our connection.
Dec 21 09:01:47 meditel1 cmsrvassistd[18111]: Lost connection with ServiceGuard cluster daemon (cmcld): Software caused connection abort
Dec 21 09:01:47 meditel1 cmomd[18502]: Failed to start package OA_pkg on meditel.
Dec 21 09:01:52 meditel1 CM-OA_pkg[18752]: cmmodnet -a -i 10.10.166.49 10.10.164.0
Dec 21 09:01:56 meditel1 CM-OA_pkg[18882]: cmmodnet -a -i 10.10.166.49 10.10.164.0
Dec 21 09:02:00 meditel1 CM-OA_pkg[19012]: cmmodnet -a -i 10.10.166.49 10.10.164.0
Dec 21 09:02:05 meditel1 CM-OA_pkg[19142]: cmmodnet -a -i 10.10.166.49 10.10.164.0


And the server stop completly with lost connection.

John Bigg
Esteemed Contributor

Re: ServiceGuard on SLES8, package don't mount VG

The main Serviceguard daemon cmcld failed with a SIGSEGV. At this point I suggest you contact HP support since I doubt we will be able to solve this here. You may like to provide a stack trace from the core file by doing:

# echo bt | gdb /opt/cmcluster/bin/cmcld /opt/cmcluster/run/core*

*note: you may need to replace the core* with the real name of the core file from the $SGRUN directory.

It may be worth while ensuring you have the latest 11.15 patch loaded which for 32 bit SLES8 is SGLX_00049 although this does not report fixing any issues resulting in a cmcld core.
peyrol
Occasional Advisor

Re: ServiceGuard on SLES8, package don't mount VG

hi,

In the OA_pkg.sh, i modify the FS_MOUNT_OPT="-o ro" instead of -o rw for passing the fsck.

in the log OA_pkg.sh.log:

###### Node "meditel1": Starting package at Wed Dec 21 14:12:21 CET 2005 ######
Dec 21 14:12:21 - Node "meditel1": Activating volume group database .
Dec 21 14:12:23 - Node "meditel1": Activating volume group files .
je suis dans check_and_mount
Dec 21 14:12:25 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Replaying journal..
0 transactions replayed
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
fsck 1.28 (31-Aug-2002)
Replaying journal..
0 transactions replayed
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
fsck 1.28 (31-Aug-2002)
Dec 21 14:12:35 - Node "meditel1": Mounting /dev/database/LVOL_database at /database
Dec 21 14:12:37 - Node "meditel1": Mounting /dev/files/LVOL_warmbackup at /files/WARMBACKUP
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
Dec 21 14:12:37 - Node "meditel1": Adding IP address 10.10.166.42 to subnet 10.10.164.0
WARNING: IP 10.10.166.42 is already configured on the subnet 10.10.164.0

###### Node "meditel1": Starting package at Wed Dec 21 14:12:37 CET 2005 ######
Dec 21 14:12:37 - Node "meditel1": Activating volume group database .
Dec 21 14:12:39 - Node "meditel1": Activating volume group files .
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
je suis dans check_and_mount
Dec 21 14:12:41 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Filesystem seems mounted read-only. Skipping journal replay.
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
fsck 1.28 (31-Aug-2002)
Filesystem seems mounted read-only. Skipping journal replay.
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
fsck 1.28 (31-Aug-2002)
Dec 21 14:12:42 - Node "meditel1": WARNING: File system "/database" was already mounted.
Dec 21 14:12:42 - Node "meditel1": WARNING: File system "/files/WARMBACKUP" was already mounted.
Dec 21 14:12:42 - Node "meditel1": Adding IP address 10.10.166.42 to subnet 10.10.164.0
WARNING: IP 10.10.166.42 is already configured on the subnet 10.10.164.0

###### Node "meditel1": Starting package at Wed Dec 21 14:12:42 CET 2005 ######
Dec 21 14:12:42 - Node "meditel1": Activating volume group database .
Dec 21 14:12:44 - Node "meditel1": Activating volume group files .
je suis dans check_and_mount
Dec 21 14:12:46 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
fsck 1.28 (31-Aug-2002)
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
fsck 1.28 (31-Aug-2002)
Dec 21 14:12:47 - Node "meditel1": WARNING: File system "/database" was already mounted.
Dec 21 14:12:47 - Node "meditel1": WARNING: File system "/files/WARMBACKUP" was already mounted.
Dec 21 14:12:47 - Node "meditel1": Adding IP address 10.10.166.42 to subnet 10.10.164.0
WARNING: IP 10.10.166.42 is already configured on the subnet 10.10.164.0

###### Node "meditel1": Starting package at Wed Dec 21 14:12:47 CET 2005 ######
Dec 21 14:12:47 - Node "meditel1": Activating volume group database .
Dec 21 14:12:49 - Node "meditel1": Activating volume group files .
je suis dans check_and_mount
Dec 21 14:12:51 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
fsck 1.28 (31-Aug-2002)
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
fsck 1.28 (31-Aug-2002)
Dec 21 14:12:52 - Node "meditel1": WARNING: File system "/database" was already mounted.
Dec 21 14:12:52 - Node "meditel1": WARNING: File system "/files/WARMBACKUP" was already mounted.
Dec 21 14:12:52 - Node "meditel1": Adding IP address 10.10.166.42 to subnet 10.10.164.0
WARNING: IP 10.10.166.42 is already configured on the subnet 10.10.164.0

###### Node "meditel1": Starting package at Wed Dec 21 14:12:52 CET 2005 ######
Dec 21 14:12:52 - Node "meditel1": Activating volume group database .
Dec 21 14:12:54 - Node "meditel1": Activating volume group files .
je suis dans check_and_mount
Dec 21 14:12:56 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
Blocks (total/free): 53346304/53336465 by 4096 bytes
Filesystem is clean
fsck 1.28 (31-Aug-2002)
Filesystem seems mounted read-only. Skipping journal replay.
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
Checking internal tree..finished
Reiserfs super block in block 16 on 0x3a01 of format 3.6 with standard journal
Blocks (total/free): 23592960/23584029 by 4096 bytes
Filesystem is NOT clean
fsck 1.28 (31-Aug-2002)
Dec 21 14:12:57 - Node "meditel1": WARNING: File system "/database" was already mounted.
Dec 21 14:12:57 - Node "meditel1": WARNING: File system "/files/WARMBACKUP" was already mounted.
Dec 21 14:12:57 - Node "meditel1": Adding IP address 10.10.166.42 to subnet 10.10.164.0
WARNING: IP 10.10.166.42 is already configured on the subnet 10.10.164.0

###### Node "meditel1": Starting package at Wed Dec 21 14:12:57 CET 2005 ######
Dec 21 14:12:57 - Node "meditel1": Activating volume group database .
Dec 21 14:12:59 - Node "meditel1": Activating volume group files .
je suis dans check_and_mount
Dec 21 14:13:01 - Node "meditel1": Checking filesystems:
/dev/database/LVOL_database
/dev/files/LVOL_warmbackup
Filesystem seems mounted read-only. Skipping journal replay.


Any idea?

thanks
Didier

John Bigg
Esteemed Contributor

Re: ServiceGuard on SLES8, package don't mount VG

I'm not sure what you question is now. Are you saying that when you mount the filesystems read write the fsck fails? And is this your real problem? If so maybe you can provide the package log file when -o rw is used so we can see the errors.