Author |
Message
|
EB |
Posted: Thu Sep 22, 2005 1:26 am Post subject: Monitoring MQ processes |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Hi
We would like to monitor the prosesses nescescary for mq to run. Question is which process are nescesary and why. Any ideas? Or tips on where I could find the answer?
Regards
EB |
|
Back to top |
|
 |
Nigelg |
Posted: Thu Sep 22, 2005 1:42 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
System Admin manual, appendix D (5.3) _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
hopsala |
Posted: Thu Sep 22, 2005 2:53 am Post subject: |
|
|
 Guardian
Joined: 24 Sep 2004 Posts: 960
|
In addition to what nigelg said:
1. Check out topic MQ Master Process list (could've found this yourself with a bit of effort...)
2. I wouldn't recommend monitoring MQ yourself, it's a lot of work and it's already be done; if possible, use some out of the box product such as HP OpenView, CCC, CA Unicenter, Patrol or others. If cost is the issue, there's QFlex that just got out, though I haven't tried it, and a few other products for monitoring which only cost ~100$ (CapitalWare). Some of these products monitor the said processes.
3. To learn more on each of those processes, look them up on this forum, you'll find a lot of real-world info on these shifty little buggers. Interestingly enough, a search for "amqzllp0" yielded a topic called Monitoring MQ Processes, Sounds familiar?  |
|
Back to top |
|
 |
EB |
Posted: Thu Sep 22, 2005 3:56 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Thanks alot for your help guys.
Anyone know about the Process list, has it been published yet?
Regards
EB |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Sep 22, 2005 3:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
EB wrote: |
Thanks alot for your help guys.
Anyone know about the Process list, has it been published yet? |
Did you look at neither the documentation Nigel told you to, or the link that Hopsala posted?
If not, why not? If so, what did you miss? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EB |
Posted: Thu Sep 22, 2005 4:06 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Actually that is what I did. In the link to MQ Master process list, Peter Potkay says the list published there is incomplete and that he tried to post it for download after updating it. So I was wondering if that was done, I couldnt find it in the repository.
Regards
EB |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Sep 22, 2005 4:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Yeah. That thread says that it never got into the repository, and includes instructions on how to get a copy of the excel spreadsheet version.
It's not necessarily very useful to monitor MQ at the process level.
Some of the processes start and stop during normal activity, some do not have to be running in order for the system to function (like the command server), some run a variable number of copies of themselves...
It's not necessarily a bad idea to include some of the basic processes in an "overall health" monitor - to let you know that MQ did or did not start up after reboot or whatever. But it's not much more helpful than that. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EB |
Posted: Thu Sep 22, 2005 4:27 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Yes I agree, but I have someone at our monitoring center that wants to monitor those processes that are nescesarry for MQ to run. Do you have any suggestions for what basic processes are sensible to monitor?
Regards
EB |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Sep 22, 2005 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
EB wrote: |
Yes I agree, but I have someone at our monitoring center that wants to monitor those processes that are nescesarry for MQ to run. Do you have any suggestions for what basic processes are sensible to monitor? |
Queue manager agents, maybe. Listener, probably. Channel Initiator, maybe. Command Server, if you're using a pcf based monitoring/admin solution.
Depends a lot on what you're trying to monitor for - general health, general availability, particular types of availability, uptime... - and why. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
markt |
Posted: Thu Sep 22, 2005 5:38 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
If processes are not running (in particular amqzxma0) then you know MQ is not running.
If processes are running, you cannot infer anything about the state of the system. For example, it might be hung.
So it's really not worth checking. Use dspmq or MQSC PING instead. Or put some dummy work through the qmgr. |
|
Back to top |
|
 |
hopsala |
Posted: Thu Sep 22, 2005 7:54 am Post subject: |
|
|
 Guardian
Joined: 24 Sep 2004 Posts: 960
|
Or monitor the error logs, or simply try to MQCONN, or send commands to command server, or or or .... The list is infinite.
I have a suggestion, if you do not wish to buy a product (though this is still the best idea in my opinion, notwithstanding there's a FREE product that does this - QFlex) do the following: download two or three trial versions of leading monitoring products, install them and see how they monitor MQ; this will give you a much better idea of what's the best way to monitor WMQ activity and status. Why re-invent the duck when it's already up and quacking? |
|
Back to top |
|
 |
csmith28 |
Posted: Thu Sep 22, 2005 8:45 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Here is a script that I run every 5 minutes from the crontab on a AIX Server with one MQManager on it. I call qmgrmon.ksh
Code: |
#!/bin/ksh
set -A PROCESS `cat /home/mqm/process.lst`
fileCount=${#PROCESS[*]}
integer errorPreset=0
for processName in ${PROCESS[@]}
do
# echo $processName
checkProcess=`ps -ef | grep -v grep | grep $processName`
# echo $?
if [ $? -eq "1" ] ; then
errorPreset=1
if [ ! -a /home/mqm/error ]; then
echo "PAX06 MQManager Down on host hostname, ${processName} is not running." | mailx individual@domain.com, pager@domain.com
fi
fi
# echo $checkProcess
done
if [ errorPreset -eq 1 ]; then
touch /home/mqm/error
else
rm -rf /home/mqm/error
fi |
Here are the processes listed in process.txt
Code: |
runmqchi
runmqlsr
amqpcsea
amqhasmx
amqzlaa0
amqzxma0 |
Note this will only alert if the MQManager is stopped or ends abnormally. If the MQManager hangs up and none of the processes listed dies it will not alert. If there is a Network issue or the server itself PANIC's and reboots or crashes it will likely not generate an alert.
I hope this helps. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
EB |
Posted: Sun Sep 25, 2005 2:52 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Thanks for all your help guys, you helped me alot...
Regards
EB |
|
Back to top |
|
 |
|