topic Re: Not able to start a package in a node in cluster in Operating System - HP-UX

Not able to start a package in a node in cluster

Shahrukh Ahamed — Thu, 13 Aug 2009 13:03:16 GMT

Hi experts...

I have NNMi 8.10 installed in cluster. When i try to run nnmpkg in a node it says.
Unable to run the Package.The node is not eligible.

can you help me on the same.

Re: Not able to start a package in a node in cluster

Sunny123_1 — Thu, 13 Aug 2009 13:06:04 GMT

Hi

Check the configuration file also post more details about cluster.

Regards
sunny

Re: Not able to start a package in a node in cluster

Shahrukh Ahamed — Thu, 13 Aug 2009 13:08:35 GMT

Hi.. thanks for your reply.

I have SG cluster in HP UX.
where there are two packages nnmpkg and orannmpkg. One for NNM and one for the oracle process.

Can you tell me which config file you are referring to. The cluster files and ascii files are fine. ANything specific i should look??

Re: Not able to start a package in a node in cluster

Sunny123_1 — Thu, 13 Aug 2009 13:12:45 GMT

Hi

look out for pkg conf file also can you post what error exactly you got during you try to run the pkg.Also look log file of pkg for more details which is located in pkg directory.

Regards
sunny

Re: Not able to start a package in a node in cluster

Shahrukh Ahamed — Thu, 13 Aug 2009 13:22:31 GMT

this is the error

Hi sunny,

root@ap3g-ch2-nms01:/var/adm/syslog # cmrunpkg nnmpkg
Unable to run package nnmpkg on node ap3g-ch2-nms01. Node is not eligible.
cmrunpkg: Unable to start some package or package instances

There is no logging in either /etc/cmcluster/nnmpkg/nnmpkg.cntl.log nor
/var/cmcluster/log/nnmpkg.log.

Last updates are on august 6th which says about shutting down the package and no error.

Re: Not able to start a package in a node in cluster

Sunny123_1 — Thu, 13 Aug 2009 14:17:28 GMT

Hi

Try

cmrunpkg -n pkg name

Regards
Sunny

Re: Not able to start a package in a node in cluster

melvyn burnard — Thu, 13 Aug 2009 14:37:06 GMT

cmviewcl -v -p nnmpkg

Does that show disabled or enabled for the nodes?

Re: Not able to start a package in a node in cluster

Roopesh Francis_1 — Thu, 13 Aug 2009 14:54:28 GMT

you may try
cmmodpkg -e

Thanks

Re: Not able to start a package in a node in cluster

melvyn burnard — Thu, 13 Aug 2009 15:05:23 GMT

>you may try
cmmodpkg -e

All that will do is enable Global package switching. If the node (Local ) switching is not enabled, then he will not be able to run the package on the node.

Re: Not able to start a package in a node in cluster

Shahrukh Ahamed — Thu, 13 Aug 2009 15:29:45 GMT

here are my investiogations..

cmrunpkg -n ap3g-ch2-nms01 nnmpkg
Unable to run package nnmpkg on node ap3g-ch2-nms01. Node is not eligible.
cmrunpkg: Unable to start some package or package instances

cmviewcl -v -p nnmpkg

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
nnmpkg down halted disabled unowned

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS NODE_NAME NAME
Subnet down ap3g-ch2-nms01 10.130.42.128
Subnet up ap3g-ch2-nms02 10.130.42.128

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ap3g-ch2-nms01
Alternate up enabled ap3g-ch2-nms02

Other_Attributes:
ATTRIBUTE_NAME ATTRIBUTE_VALUE
Style legacy
Priority 500

this shows subnet down... how can i check ???

cmmodpkg -e nnmpkg runs the package on the other node...

Re: Not able to start a package in a node in cluster

melvyn burnard — Thu, 13 Aug 2009 16:42:26 GMT

you have a subnet down?
And you did not notice that?
well you need to go onto that node and see why the subnet is down.
Maybe a failed card/port/cable
You will ned to fix that.

Re: Not able to start a package in a node in cluster

Mr Zer0 — Tue, 18 Aug 2009 06:13:35 GMT

Also whenever a cluster/package is being started/stopped it will be logged in the syslog.log check that too, it might help.

Re: Not able to start a package in a node in cluster

Vijaykumar_1 — Thu, 20 Aug 2009 11:20:48 GMT

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ap3g-ch2-nms01
Alternate up enabled ap3g-ch2-nms02

This displays that your package switching is enabled and the node is capable of running the package..

Running cmmodpkg -e nodenames and then trying cmrunpkg would be the best options which you have tried already..

Now need to analyze the logs from the package control file..

Re: Not able to start a package in a node in cluster

Shahrukh Ahamed — Thu, 20 Aug 2009 11:36:11 GMT

Thanks for the comments...
I rebooted the node and then brought the node to the cluster.

This helped the package moving also.The logs didn say any error that became more difficult as it said only some net interface change.

Re: Not able to start a package in a node in cluster

polo_zz — Thu, 20 Aug 2009 14:20:24 GMT

I config the MC-SG 11.19 on HPUX 11.31.there are 2 pkg in the cluster.But,When i try to run pkg1 in a node it says:Unable to run the Package.The node is not eligible. same to the "Shahrukh Ahamed ".
HOW can I make it right?
the log :

HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#ls
monitor pkg_hsmagt.cntl pkg_hsmagt.cntl.log pkg_hsmagt.conf start_hsm.sh stop_hsm.sh
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#vi *conf
"pkg_hsmagt.conf" 799 lines, 34495 characters
# **********************************************************************
# ****** 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 Serviceguard manual.
# **********************************************************************
#
# "PACKAGE_NAME" is the name that is used to identify the package.
#
# This name will be used to identify the package when viewing or
# manipulating it. Package names must be unique within a cluster.
#
#
# Legal values for PACKAGE_NAME:
# Any string that starts and ends with an alphanumeric character, and
# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in between.
# Maximum length is 39 characters.
#

PACKAGE_NAME pkg_hsmagt

# "PACKAGE_TYPE" is the type of package.
#
# The PACKAGE_TYPE attribute specifies the desired behavior for this
# package. Legal values and their meaning are described below:
#
# FAILOVER package runs on one node at a time and if a failure
# occurs it can switch to an alternate node.
#
# MULTI_NODE package runs on multiple nodes at the same time and
# can be independently started and halted on
# individual nodes. Failures of package components such
/hsm_
# SERVICE_FAIL_FAST_ENABLED no
# SERVICE_HALT_TIMEOUT 300
#
# Note: No environmental variables will be passed to the service command, this
# includes the PATH variable. Absolute path names are required for the
# service command definition. Default shell is /usr/bin/sh.
#
# Legal values for SERVICE_NAME:
# Any string that starts and ends with an alphanumeric character, and
# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in between.
# Maximum string length is 39 characters.
#
# Legal values for SERVICE_FAIL_FAST_ENABLED: yes, no.
# Legal values for SERVICE_HALT_TIMEOUT: (value >= 0).

SERVICE_NAME hsm_service
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300

# Event Monitoring Service Resource Dependencies
#
# Event monitoring service resource dependencies are specified with the
# following parameters: "RESOURCE_NAME", "RESOURCE_POLLING_INTERVAL",
# "RESOURCE_START" and "RESOURCE_UP_VALUE".
#
# To define a package resource dependency, a "RESOURCE_NAME" line with
# a fully qualified resource path name, and one or more
# "RESOURCE_UP_VALUE" lines are required. "RESOURCE_POLLING_INTERVAL" and
# the "RESOURCE_START" are optional, and will default as described
# below if not specified.
#
# The "RESOURCE_POLLING_INTERVAL" indicates how often, in seconds, the
# resource is to be monitored. The default is 60 seconds.
:q!
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#ls
monitor pkg_hsmagt.cntl pkg_hsmagt.cntl.log pkg_hsmagt.conf start_hsm.sh stop_hsm.sh
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#vi *cntl
"pkg_hsmagt.cntl" 2085 lines, 64673 characters
# @(#) A.11.19.00 Date: 12/09/08 $
# **********************************************************************
# * *
# * HIGH AVAILABILITY PACKAGE CONTROL SCRIPT (template) *
# * *
# * Note: This file MUST be edited before it can be used. *
# * *
# **********************************************************************

# The environment variables PACKAGE, NODE, SG_PACKAGE,
# SG_NODE and SG_SCRIPT_LOG_FILE 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.

# NOTE: Starting from 11.17, all environment variables set by
# Serviceguard implicitly at the time the control script is
# executed will contain the prefix "SG_". Do not set any variable
# with the defined prefix, or the control script may not
# function as it should.

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

# UNCOMMENT the variables as you set them.

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

# VOLUME GROUP ACTIVATION:
# Specify the method of activation for volume groups.
# Leave the default (VGCHANGE="vgchange -a e") if you want volume
# groups activated in exclusive mode. This assumes the volume groups have
# been initialized with 'vgchange -c y' at the time of creation.
/hsm_
# SERVICE_NAME[1]=pkg1b
# SERVICE_CMD[1]="/usr/bin/X11/xload -display 192.10.25.54:0"
# SERVICE_RESTART[1]="-r 2" # Will restart the service twice.
#
# SERVICE_NAME[2]=pkg1c
# SERVICE_CMD[2]="/usr/sbin/ping"
# 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 /usr/bin/sh.
#
SERVICE_NAME[0]="hsm_service"
SERVICE_CMD[0]="/etc/cmcluster/pkg_hsmagt/monitor"
SERVICE_RESTART[0]=""

# DEFERRED_RESOURCE NAME
# Specify the full path name of the 'DEFERRED' resources configured for
# this package. Uncomment DEFERRED_RESOURCE_NAME[0]="" and fill in the
# full path name of the resource.
#
#DEFERRED_RESOURCE_NAME[0]=""

# DTC manager information for each DTC.
# Example: DTC[0]=dtc_20
#DTC_NAME[0]=

# HA_NFS_SCRIPT_EXTENSION
# If the package uses HA NFS, this variable can be used to alter the
# name of the HA NFS script. If not set, the name of this script is
# assumed to be "hanfs.sh". If set, the "sh" portion of the default
# script name is replaced by the value of this variable. So if
# HA_NFS_SCRIPT_EXTENSION is set to "package1.sh", for example, the name
"pkg_hsmagt.cntl" 2082 lines, 64611 characters
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#ii -P /etc/cmcluster/pkg_hsmagt/pkg_hsmagt.conf <
Begin cluster verification...
Checking cluster file: /etc/cmcluster/cluster.ascii
Defaulting MAX_CONFIGURED_PACKAGES to 300.
Checking nodes ... Done
Checking existing configuration ... Done
Defaulting MAX_CONFIGURED_PACKAGES to 300.
Gathering storage information
Found 29 devices on node HHNRXZZ1
Found 29 devices on node HHNRXZZ2
Analysis of 58 devices should take approximately 6 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 6 volume groups on node HHNRXZZ1
Found 6 volume groups on node HHNRXZZ2
Analysis of 12 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Gathering network information
Beginning network probing (this may take a while)
Completed network probing
Gathering polling target information
Cluster switch is an existing cluster
Parsing package file: /etc/cmcluster/pkg_hsmagt/pkg_hsmagt.conf.
/etc/cmcluster/pkg_hsmagt/pkg_hsmagt.conf: A legacy package is being used.
Package pkg_hsmagt already exists. It will be modified.
WARNING: Incorrect permissions for /etc/cmcluster/pkg_hsmagt (40777). Directory must be executable for owner, and not writable by group and others on node HHNRXZZ1.
WARNING: Incorrect permissions for /etc/cmcluster/pkg_hsmagt (40777). Directory must be executable for owner, and not writable by group and others on node HHNRXZZ2.
Cluster switch is an existing cluster
Checking for inconsistencies
Run script /etc/cmcluster/pkg_switch/pkg_switch.cntl for package pkg_switch
does not have execute access on node HHNRXZZ1.
Maximum configured packages parameter is 4.
Configuring 2 package(s).
2 package(s) can be added to this cluster.
199 access control policies can be added to this cluster.
Modifying configuration on node HHNRXZZ1
Modifying configuration on node HHNRXZZ2
Modifying the cluster configuration for cluster switch
Modifying node HHNRXZZ1 in cluster switch
Modifying node HHNRXZZ2 in cluster switch
Modifying the package configuration for package pkg_hsmagt.

Modify the cluster configuration ([y]/n)? y
Marking/unmarking volume groups for use in the cluster

Completed the cluster creation
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmruncl -v
cmruncl: Validating network configuration...
Gathering network information
Beginning network probing (this may take a while)
Completed network probing
Gathering polling target information
cmruncl: Network validation complete
cmruncl: Validating cluster lock disk .... Done
Waiting for cluster to form .... done
Cluster successfully formed.
Check the syslog files on all nodes in the cluster to verify that no warnings occurred during startup.
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmviewcl

CLUSTER STATUS
switch up

NODE STATUS STATE
HHNRXZZ1 up running
HHNRXZZ2 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_switch starting starting enabled HHNRXZZ2

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_hsmagt down failed enabled unowned
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmviewcl

CLUSTER STATUS
switch up

NODE STATUS STATE
HHNRXZZ1 up running
HHNRXZZ2 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_switch starting starting enabled HHNRXZZ2

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_hsmagt down failed enabled unowned
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmrunpkg pkg_hsmagt
Unable to run package pkg_hsmagt on node HHNRXZZ1. Node is not eligible.
cmrunpkg: Unable to start some package or package instances
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmviewcl

CLUSTER STATUS
switch up

NODE STATUS STATE
HHNRXZZ1 up running
HHNRXZZ2 up running

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_switch starting starting enabled HHNRXZZ2

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
pkg_hsmagt down failed enabled unowned
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmrunpkg pkg_hsmagt -n HHNRXZZ2
cmrunpkg: Package -n not found
cmrunpkg: Unable to start some package or package instances
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmrunpkg -n HHNRXZZ2 pkg_hsmagt
Unable to run package pkg_hsmagt on node HHNRXZZ2. Node is not eligible.
cmrunpkg: Unable to start some package or package instances
HHNRXZZ1:[/etc/cmcluster/pkg_hsmagt]#cmrunpkg -n HHNRXZZ1 pkg_hsmagt
Unable to run package pkg_hsmagt on node HHNRXZZ1. Node is not eligible.
cmrunpkg: Unable to start some package or package instances

Re: Not able to start a package in a node in cluster

sg222 — Fri, 04 Dec 2009 15:32:22 GMT

I had the same error and checked everything:
- package conf
- package cntl
- cluster ascii conf

It was as simple as stupid, the vg was still activated (to test it) on one of the cluster nodes and could not be activated in exclusive mode by the new cluster node.

A simple
vgchange -a n vgXX

solved the problem, the package could start.

Check the /var/adm/syslog/syslog file for information like:
Dec 4 16:18:07 NODE cmcld[8438]: Executing '/etc/cmcluster/PACKAGE/PACKAGE.cntl start' for package PACKAGE, as service PKG*85254.
Dec 4 16:18:07 NODE cmserviced[8442]: Request to perform run service PKG*85254
Dec 4 16:18:07 NODE LVM[16258]: vgchange -a n vgXX
Dec 4 16:18:07 NODE cmserviced[8442]: Service PKG*85254 terminated due to an exit(1).
Dec 4 16:18:07 NODE cmcld[8438]: Package PACKAGE run script exited with NO_RESTART.
Dec 4 16:18:07 NODE cmcld[8438]: Examine the file /etc/cmcluster/PACKAGE/PACKAGE.cntl.log for more details.
####

Maybe this could help.

Re: Not able to start a package in a node in cluster

sujit kumar singh — Sat, 05 Dec 2009 13:33:32 GMT

Hi

you can first see by enabling the package to run on the desired node.

cmmodpkg -v -n
wehn done
run the package

cmrunpkg -v -n

try to capture the syslog and also the package control file

that is

/var/adm/syslog/syslog.log
and

/etc/cmcluster//.cntl.log
and psot both the O/ps

regards
sujit

Re: Not able to start a package in a node in cluster

thrubovc — Tue, 22 Jan 2013 19:50:32 GMT

Hi there,

I just had the same problem. What I (and probably you too) need to do is cmmodpkg -e -n nodename pkgname. This website saved me.

cmmodpkg -e did not help:

hydrogen[root]:/root:>cmmodpkg -e pm30pkg2
Package pm30pkg2 is already enabled
cmmodpkg: Completed successfully on all packages specified

but this one did:

hydrogen[root]:/root:>cmmodpkg -v -e -n hydrogen pm30pkg2
Enabling node hydrogen for switching of package pm30pkg2
Successfully enabled package pm30pkg2 to run on node hydrogen
cmmodpkg: Completed successfully on all packages specified

what's funny is that it's a one-node cluster.

hope this helps someone in the future!

Re: Not able to start a package in a node in cluster

MahboobEllath — Mon, 18 Feb 2013 10:04:08 GMT

Have you fixed your subnet problems...?? If not disable the SUBNET monitoring and start the package..