| Author |
Message
|
| matuwe |
 Posted: Mon Dec 08, 2008 1:57 am Post subject: MQ crash (Not responding) |
 |
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Please help. I seem to have a wiered problem. Some how MQ is not responding at all. I killed all the mq processes and I am now trying to restart the MQ server without restarting the the physical box. MQ is running on Linux. I had this problem before and it was resolved by restrtng the server, but I cannot do it right now as I have other service running on this machine. It has been working perfectly for 3 months. Version 6.0.2.4
How can I start MQ SERVER without rebooting the machine.
FDC file created
| Code: |
-bash-3.2$ more AMQ11146.0.FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday December 08 10:29:06 SAST 2008 |
| Host Name :- jprod (Linux 2.6.18-92.el5PAE) |
| PIDS :- 5724H7204 |
| LVLS :- 6.0.2.4 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- MQ000010 |
| Application Name :- MQM |
| Component :- Unknown |
| SCCS Info :- cmd/lqm/amqzlaa0.c, 1.173.1.10 |
| Line Number :- 615 |
| Build Date :- May 12 2008 |
| CMVC level :- p600-204-080509 |
| Build Type :- IKAP - (Production) |
| UserID :- 00001008 (wbisb) |
| Program Name :- amqzlaa0 |
| Addressing mode :- 32-bit |
| Process :- 11146 |
| Thread-Process :- 11146 |
| Thread :- 1 |
| ThreadingModel :- PosixThreads |
| QueueManager :- PROD_QMGR |
| ConnId(1) IPCC :- 223 |
| ConnId(2) QM :- 86 |
| Last HQC :- 1.0.0-691356 |
| Last HSHMEMB :- 2.1.1-53416 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecP_E_INVALID_PID |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806105) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545284357 20806105 |
| |
+-----------------------------------------------------------------------------+
|
|
|
| Back to top |
|
 |
| matuwe |
| Posted: Mon Dec 08, 2008 4:55 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Please help  All the MQ commands are not responding.. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Dec 08, 2008 7:52 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| Try clearing all the ipcs resources that belong to mqm as well as killing the processes. ProbeID indicate broken handles so be sure the listener is not running. |
|
| Back to top |
|
|
| matuwe |
| Posted: Tue Dec 09, 2008 2:19 am Post subject: AMQ7017: Log not available. |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Thanks for the response, I finally had the server restarted. Now my problem is when I try to start my MQ manager I get
strmqm PROD_QMGR
WebSphere MQ queue manager 'PROD_QMGR' starting.
AMQ7017: Log not available.
But the server doesn't really start. I also had this problem before and I found something on google that say I need to create a new Queue manager and copy the ..log/../active/ files to from the new queue manager to my old. Which worked, but now it doesn't wanna work |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 09, 2008 2:30 am Post subject: Re: AMQ7017: Log not available. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matuwe wrote: |
| now it doesn't wanna work |
Yes, well, I don't wanna work but I still have to.
Is there actually an error, or just a blind tantrum?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| matuwe |
| Posted: Tue Dec 09, 2008 2:41 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 09, 2008 3:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matuwe wrote: |
| it seems like my mistake was to create any queue manager and not use the same name. |
The name is kinda key to matching up log with queue manager.
Well done you, and thank you for posting your eventual solution for the benefit of the next reader.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
I followed this link