| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQV7.0.1.1 Monitoring Script on HP-Service Guard |
« View previous topic :: View next topic » |
| Author |
Message
|
| dipinci |
 Posted: Mon May 31, 2010 4:04 am Post subject: MQV7.0.1.1 Monitoring Script on HP-Service Guard |
 |
|
Newbie
Joined: 13 Apr 2009
Posts: 3
|
Hi,
I am configuring active/passive MQ with HP-UX Service Guard, Installed and configured the QMGR as per MQ Infocenter document.
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa70230_.htm
I would like monitor QMGR on HP-UX service guard, for this I have created a script as per above document and configured with mqm.config and mqm.cntl script, But cluster not able to start/failover QMGR once the service is configured. log files are below
Any Help on this appreciated.
Log from HP Cluster
****************
########### Node "qpapp1": Starting package at Mon May 31 11:07:13 WAT 2010 ###########
May 31 11:07:13 - Node "qpapp1": Activating volume group vg01 with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vg01" has been successfully changed.
May 31 11:07:13 - Node "qpapp1": Checking filesystems:
/dev/vg01/lvol1
fsck: /etc/default/fs is used for determining the file system type
file system is clean - log replay is not required
May 31 11:07:13 - Node "qpapp1": Mounting /dev/vg01/lvol1 at /MQHA
May 31 11:07:13 - Node "qpapp1": Adding IP address 172.20.1.13 to subnet 172.20.0.0
WebSphere MQ queue manager 'QPAY' starting.
5 log records accessed on queue manager 'QPAY' during the log replay phase.
Log replay for queue manager 'QPAY' complete.
Transaction manager state recovered for queue manager 'QPAY'.
WebSphere MQ queue manager 'QPAY' started.
May 31 11:07:18 - Node "qpapp1": Starting service MQHA using
"/etc/cmcluster/mqm/mqscripts/mon.sh"
########### Node "qpapp1": Package start completed at Mon May 31 11:07:18 WAT 2010 ###########
Queue manager 'QPAY' is responsive
########### Node "qpapp1": Halting package at Mon May 31 11:07:18 WAT 2010 ###########
May 31 11:07:18 - Node "qpapp1": Halting service MQHA
cmhaltserv : Service name MQHA is not running.
Attempting immediate end of queue manager 'QPAY'
WebSphere MQ queue manager 'QPAY' ending.
Waiting for immediate end of queue manager 'QPAY'
WebSphere MQ queue manager 'QPAY' ended.
May 31 11:07:26 - Node "qpapp1": Remove IP address 172.20.1.13 from subnet 172.20.0.0
May 31 11:07:26 - Node "qpapp1": Unmounting filesystem on /dev/vg01/lvol1
May 31 11:07:26 - Node "qpapp1": Deactivating volume group vg01
Deactivated volume group in Exclusive Mode.
Volume group "vg01" has been successfully changed.
Log from the syslog
****************
May 31 12:01:41 qpapp1 cmcld: Service PKG*19714 terminated due to an exit(0).
May 31 12:01:41 qpapp1 cmcld: Halted package MQHA on node qpapp1. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon May 31, 2010 6:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dipinc wrote: |
May 31 11:07:18 - Node "qpapp1": Starting service MQHA using
"/etc/cmcluster/mqm/mqscripts/mon.sh"
########### Node "qpapp1": Package start completed at Mon May 31 11:07:18 WAT 2010 ###########
Queue manager 'QPAY' is responsive
########### Node "qpapp1": Halting package at Mon May 31 11:07:18 WAT 2010 ###########
May 31 11:07:18 - Node "qpapp1": Halting service MQHA
|
Obviously, something you are not recording is happening in between there. It looks like it makes the cluster believe that something is not running correctly in the service...
What happens if you exit your monitoring script right away with 0 return code? (exit 0)?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dipinci |
| Posted: Mon May 31, 2010 9:39 pm Post subject: |
|
|
Newbie
Joined: 13 Apr 2009
Posts: 3
|
With Exit0 it is trying to failover the pkg to second node with the same result.
Below log are from Syslog. Without service the cluster failover is works fine. Below is the abstract of the script.
QM=$1
if [ -z "$QM" ]
then
echo "ERROR! No queue manager name supplied"
exit 1
fi
# Test the operation of the queue manager. Result is 0 on success, non-zero on error.
echo "ping qmgr" | runmqsc ${QM} > /dev/null 2>&1
pingresult=$?
if [ $pingresult -eq 0 ]
then # ping succeeded
echo "Queue manager '${QM}' is responsive"
result=0
else # ping failed
# Don't condemn the queue manager immediately, it might be starting.
srchstr="( |-m)$QM *.*$"
cnt=`ps -ef | tr "\t" " " | grep strmqm | grep "$srchstr" | grep -v grep \
| awk '{print $2}' | wc -l`
if [ $cnt -gt 0 ]
then
# It appears that the queue manager is still starting up, tolerate
echo "Queue manager '${QM}' is starting"
result=0
else
# There is no sign of the queue manager starting
echo "Queue manager '${QM}' is not responsive"
result=$pingresult
fi
fi
exit $result |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
