| Author |
Message
|
| sunshine |
 Posted: Mon Dec 08, 2008 12:17 am Post subject: QManager Failed to start |
 |
|
Novice
Joined: 07 Dec 2008
Posts: 13
|
I am pretty new in MQ . Please help me in this problem mentioned below.
In a unix box --we have a Queue Manager . It is in ended unexpecdedly state. When ever I am trying to start that it is showing " Queue Manager is running message "....I am not able delete that queue manager also.
This queue Manager is down for a long time--I remain unable to start it...HELP Required... 
I checked with ps -ef|grep mqm---no mqm process is running...
I am giving the log reference
12/07/2008 11:11:10 PM - Process(22741.1) User(root) Program(amqzxma0)
AMQ6118: An internal WebSphere MQ error has occurred (20806805)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 771 --------------------------------------------------------
12/07/2008 11:11:10 PM - Process(22741.1) User(root) Program(amqzxma0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager TEST.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 22741.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 810 --------------------------------------------------------
12/07/2008 11:13:56 PM - Process(22787.1) User(root) Program(amqzmuc0)
AMQ6004: An error occurred during WebSphere MQ initialization or ending.
EXPLANATION:
An error was detected during initialization or ending of MQ. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 771 --------------------------------------------------------
12/07/2008 11:13:56 PM - Process(22787.1) User(root) Program(amqzmuc0)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 22787.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 08, 2008 12:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Find the FDC file that goes with these errors. Look up the ProbeId in Google.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 08, 2008 12:30 am Post subject: Re: QManager Failed to start |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sunshine wrote: |
| I checked with ps -ef|grep mqm---no mqm process is running... |
There's a list of processes in the System Admin manual. Kill them in the order given.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sunshine |
| Posted: Mon Dec 08, 2008 12:56 am Post subject: |
|
|
Novice
Joined: 07 Dec 2008
Posts: 13
|
Thanks for reply victor---I killed the process but now when i tried to start Qmg I am geeting AMQ6109 error--What does this
1077960969 0x40406109 STOP
1077960969 0x40406109 xecSTOP--mean ? How to trouble shoot that ?
AMQ6109: An internal WebSphere MQ error has occurred.
mqrc AMQ6109
1077960969 0x40406109 STOP
1077960969 0x40406109 xecSTOP
MESSAGE:
An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 08, 2008 1:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sunshine wrote: |
How to trouble shoot that ?
|
Look in the FDC files like I said.
| sunshine wrote: |
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sunshine |
| Posted: Mon Dec 08, 2008 4:52 am Post subject: |
|
|
Novice
Joined: 07 Dec 2008
Posts: 13
|
Please give me a solution for this.....I am too new in MQ field to handle such bombastic errors  |
|
| Back to top |
|
|
| sunshine |
| Posted: Mon Dec 08, 2008 4:55 am Post subject: |
|
|
Novice
Joined: 07 Dec 2008
Posts: 13
|
I am getting this error also..why this error is changing again nd again .I got different error earlier.
Can any one help me in learning to trouble shoot with the help of FDC files ??
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday December 08 05:09:57 MST 2008 |
| Host Name :- WPLIU616d (Linux 2.4.9-e.3) |
| PIDS :- 5724H7204 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- ZX085010 |
| Application Name :- MQM |
| Component :- amqzmuc0 |
| SCCS Info :- cmd/zmain/amqzmut0.c, 1.31 |
| Line Number :- 340 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000000 (root) |
| Program Name :- amqzmuc0 |
| Addressing mode :- 32-bit |
| Process :- 26614 |
| Thread-Process :- 26614 |
| Thread :- 1 |
| ThreadingModel :- LinuxThreads |
| Major Errorcode :- xecI_S_FAIL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6004 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6004: An error occurred during WebSphere MQ |
| initialization or ending. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Dec 08, 2008 5:00 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| sunshine wrote: |
| Please give me a solution for this.....I am too new in MQ field to handle such bombastic errors |
It is not easy to give a solution with such little information, and if you are so new to WMQ that you do not know where FDC files are generated, what they are, and how to read them, then please enlist the help from an experienced WMQ admin at your site.
In the mean time, the FDC files can be found in: /var/mqm/errors
Order by last used, and look in there for a PROBE ID.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Dec 08, 2008 5:04 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Current level is 6.0.2.5, so I suggest that application of the appropriate Fix/Refresh Pack will be beneficial.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 08, 2008 5:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sunshine wrote: |
| Please give me a solution for this.....I am too new in MQ field to handle such bombastic errors |
You'll get used to them.
It's probably worth mentioning to your manager that, if you're this new and this far into the admin role without guidance, a little training might help. WMQ is not an easy product to get to grips with, nor is it supposed to be.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 08, 2008 5:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sunshine wrote: |
Can any one help me in learning to trouble shoot with the help of FDC files ??
|
Please see my previous comment. We're not set up in here to be a training resource. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sunshine |
| Posted: Mon Dec 08, 2008 9:22 pm Post subject: |
|
|
Novice
Joined: 07 Dec 2008
Posts: 13
|
I guess you guys are getting me all wrong...My post was not menat for training I guess.
I have already given the FDC (that means I know the location  ). But really I do not have any clue how to proceed with this Probe ID and Major Error code. I just need a pointer from where I can learn, I donot need a training session here in this BB. I would be highly thankful if I get some pointer from you guys ,who are really experienced in MQ field.
Kindly help.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 09, 2008 1:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sunshine wrote: |
| I do not have any clue how to proceed with this Probe ID and Major Error code. |
Ask Mr Google what they mean. If he doesn't know raise a PMR with IBM.
| sunshine wrote: |
| I just need a pointer from where I can learn |
AFAIK (and I'd be interested to be corrected) there's not a published list of ProbeIds (such as there is for reason codes) because they are intended for internal use only.
In theory, you never get an FDC file because the queue manager never hits an unexpected situation.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 09, 2008 4:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Search the IBM site with the probeID. You usually get directed to known problems and APAR's.
The first thing I would do in your case is stop all qmgrs and qmgr service on your box, clear the shared memory (amqiclen) and upgrade to 6.0.2.5.
Try running your qmgr at that level (6.0.2.5). 6.0.0.0 was not a good level.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
