| Author |
Message
|
| dutchman |
 Posted: Wed Jun 07, 2006 4:25 am Post subject: MQ v5.3.1 CSD12 Linux - strmqm fails probe RM185002 |
 |
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Hi all,
Has anyone seen this issue before? Also, it would be nice if an IBMer could actually explain what the problem appears to be.
Env: Redhat linux AS3, MQ V5.3.1 CSD12
On a regular bais a 'strmqm' fails giving this FDC:
Date/Time :- Wednesday June 07 12:06:28 BST 2006
Host Name :- xldn0691dap (Linux 2.4.21-27.0.2.ELsmp)
PIDS :- 5724B4104
LVLS :- 530.12 CSD12
Product Long Name :- WebSphere MQ for Linux for Intel
Vendor :- IBM
Probe Id :- RM185002
Application Name :- MQM
Component :- rrmInitRepos
Build Date :- Dec 8 2005
CMVC level :- p530-12-L051208
Build Type :- IKAP - (Production)
UserID :- 00029398 (vanzunru)
Program Name :- amqrrmfa
Thread-Process :- 00027136
Thread :- 00000001
QueueManager :- QIUKSKC
ThreadingModel :- LinuxThreads
LD_ASSUME_KERNEL :- 2.4.19
Major Errorcode :- rrcE_MQCONN_FAILED
Minor Errorcode :- OK
Probe Type :- MSGAMQ9508
Probe Severity :- 2
Probe Description :- AMQ9508: Program cannot connect to the queue manager.
FDCSequenceNumber :- 0
Arith1 :- 2 2
Arith2 :- 2059 80b
Comment1 :- QIUKSKC
Comment2 :- MQRC_Q_MGR_NOT_AVAILABLE
Regards ... Ruud |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Wed Jun 07, 2006 5:43 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
Probe Description :- AMQ9508: Program cannot connect to the queue manager.
|
Have you got the queue manager running? Have you spelled the name correctly (remember the case is important too)
IBM have told you what the problem is, who do you think wrote the error message? 
The reason code is here
| Quote: |
Arith2 :- 2059 80b
|
Reason code 2059 is Queue manager not available and there are several reasons for this.
Hope this helps |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 07, 2006 6:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kevinf2349 wrote: |
| Reason code 2059 is Queue manager not available and there are several reasons for this. |
| dutchman wrote: |
| On a regular bais a 'strmqm' fails giving this FDC: |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Jun 07, 2006 6:28 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Hmmmm missed that.
Is this a clustered queue manager by any chance? |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jun 07, 2006 7:58 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are there any other FDC's being generated at the same timeframe?
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jun 07, 2006 8:36 am Post subject: Re: MQ v5.3.1 CSD12 Linux - strmqm fails probe RM185002 |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| dutchman wrote: |
| Has anyone seen this issue before? |
I've seen one (apparently) similar problem - it turned out to be caused by a corrupted installation of MQ. Re-installing fixed the problem.
| Quote: |
| Also, it would be nice if an IBMer could actually explain what the problem appears to be. |
If the MQ installation looks complete, and/or you have tried un-installing and re-installing but this doesn't help, I think you have a strong case for raising a call with IBM Support, and they should be able to provide answers if you supply the full .FDC file and other details they may require (see eg. http://www.ibm.com/support/docview.wss?rs=171&uid=swg21229861 ). |
|
| Back to top |
|
|
| dutchman |
| Posted: Wed Jun 07, 2006 11:52 pm Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Thx all who responded - some were even useful 
Come on you guys, do you really think I can't sort out what a 'standard' mq return code 2059 means? .
Anyway, let me answer the various questions posed:
---
Have you got the queue manager running? Have you spelled the name correctly (remember the case is important too)
Answer: no, the queue manager is NOT running. Have I spelled the queue manager name correctly? This question reminds me of the joke that the helpdesk person asks the novice user "have you switched on the pc"? - yes, the name was correct - if not, the start would have failed straight away with code 2058. Thx anyway
---
IBM have told you what the problem is, who do you think wrote the error message?
Answer: very funny
---
Is this a clustered queue manager by any chance?
Answer: no, and so the question is why does it appear to have failed in code related to clustering - apparently.
---
Are there any other FDC's being generated at the same timeframe?
Answer: yes, but only afterwards - the next FDC complains that an important process is not available - ie died
---
I've seen one (apparently) similar problem - it turned out to be caused by a corrupted installation of MQ. Re-installing fixed the problem.
Answer: interesting thought. About 3 weeks ago I applied CSD12. I might just take off CSD12 and revert back to CSD11.
---
Quote:
Also, it would be nice if an IBMer could actually explain what the problem appears to be.
If the MQ installation looks complete, and/or you have tried un-installing and re-installing but this doesn't help, I think you have a strong case for raising a call with IBM Support, and they should be able to provide answers if you supply the full .FDC file and other details they may require
Answer: I've got 13 queue manager running on this system, most of which are being used - but, it's an option - thx
---
I have now opened a PMR with IBM, but would welcome further feedback.
Cheers ... Ruud |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Jun 08, 2006 4:56 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Dutchman
Sorry about the reply yesterday, I misread when it was you were getting the error. 
| Quote: |
| Answer: I've got 13 queue manager running on this system, most of which are being used - but, it's an option |
I seem to recall some discussion about the number of queue managers that were able to be run on a single box sometime ago, but can't recall the full discussion. It could be worth a search, if you haven't already. |
|
| Back to top |
|
|
| dutchman |
| Posted: Thu Jun 08, 2006 6:12 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
| Hi Kevin - no problem - I'll keep you posted with progress ... cheers ... Ruud |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 08, 2006 6:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There isn't a fixed number of queue managers that can run on a machine.
It's entirely dependant on the resources of the box.
Things to check are disk space, memory utilization, kernel tuning, ulimits, etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dutchman |
| Posted: Thu Jun 08, 2006 6:27 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Indeed - all good things to check - and in 'most' cases if you run out of a particular resource, mq kindly tells you - but not always.
All the other queue managers seem to running fine anyway - but what is different about the 'problem' queue manager is that I am constantly stopping and starting it. I have, in fact, resorted to deleting an redefining it but to no avail.
But as I said in a previous post, I am considering uninstalling CSD12 - also still waiting for an IBM reply.
Cheers ... Ruud |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 08, 2006 6:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you can, try stoppping all the queue managers, and starting the problem one up first.
If that succeeds, then it's pretty indicative of a resource issue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Jun 08, 2006 11:46 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
The fdc is basically saying that the repository manager (process kicked off during the startup of the qmgr) cant connect to the qmgr for some reason. If I had to guess, I'd consider some level of o/s resource shortage, but without looking through a trace it may be hard to identify.
Jeff's suggestion of stopping others and starting this one is a very good one, as stopping one qmgr should free up some resources
Just double check there are no other FDC files before the 2059, as this could be a symptom of another problem. Check the qmgr and global error logs as well |
|
| Back to top |
|
|
|
|
