| Author |
Message
|
| itsme_001 |
 Posted: Sun Aug 30, 2009 9:30 pm Post subject: Not able to start QM |
 |
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
I'm not able to start my QM's after reboot. There was a prob with the server and it had to be rebooted without stoping the MQ services. After the reboot, I'm not able to start my QM. I'm Getting
[/home/mqm] strmqm QQQ.QMGR
Log not available.
In the logs I'm getting:
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
PROFILEQMGR.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 41792.
How can I start my QM's
Env: MQ 5.3; AIX |
|
| Back to top |
|
 |
| jeevan |
| Posted: Sun Aug 30, 2009 9:55 pm Post subject: Re: Not able to start QM |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| itsme_001 wrote: |
I'm not able to start my QM's after reboot. There was a prob with the server and it had to be rebooted without stoping the MQ services. After the reboot, I'm not able to start my QM. I'm Getting
[/home/mqm] strmqm QQQ.QMGR
Log not available.
In the logs I'm getting:
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
PROFILEQMGR.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 41792.
How can I start my QM's
Env: MQ 5.3; AIX |
which CSD has been applied? Also, paste the error from the error file. Is there any FDC file created?
I assume from your postinng that probably the active log has been corrupted.
It is better to recreate the queue manager or if you can not do that, create a new log as in the url below:
http://www-01.ibm.com/support/docview.wss?uid=swg21179695
Last edited by jeevan on Sun Aug 30, 2009 10:16 pm; edited 2 times in total |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Sun Aug 30, 2009 10:04 pm Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
Name: WebSphere MQ
Version: 530.8 CSD08
Here's the FDC:
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday August 31 10:58:39 IST 2009 |
| Host Name :- vbdc5 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- ZX000001 |
| Application Name :- MQM |
| Component :- ExecCtrlrMain |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (mqm) |
| Program Name :- amqzxma0_nd |
| Process :- 00015732 |
| Thread :- 00000001 |
| QueueManager :- PROFILEQMGR |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- lpiRC_LOG_NOT_AVAILABLE |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (7017) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 28695 7017 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Aug 30, 2009 10:05 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The Original Post says the OS. This is AIX.
The real problem is the Version of WMQ that is being used. To keep it short, V5.3 is out of support and should be upgraded to V6( or V7 if possible) .
I agree that no mention of the CSD level that has been applied. It could be that he is running V5.3 with no patches.
That said, there is no detail in the post to indicate that for example, /home/mqm/... contains the Queue Manager directory tree even exists for the QM he wishes to start and if for some reason, the ownership or access control on those files has been changed.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Aug 30, 2009 10:11 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| itsme_001 wrote: |
Name: WebSphere MQ
Version: 530.8 CSD08
Here's the FDC:
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday August 31 10:58:39 IST 2009 |
| Host Name :- vbdc5 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- ZX000001 |
| Application Name :- MQM |
| Component :- ExecCtrlrMain |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (mqm) |
| Program Name :- amqzxma0_nd |
| Process :- 00015732 |
| Thread :- 00000001 |
| QueueManager :- PROFILEQMGR |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- lpiRC_LOG_NOT_AVAILABLE |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (7017) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 28695 7017 |
mq5.3 is non supported version and CSD 8 and 9 are officially withdrawn from the production. Please change the CSD 14 if you can not upgrade immediately. Once you applied new CSD or upgrade, either create a new queue manager or replace the log as in the url in my previous post. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Aug 30, 2009 10:20 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Are any of the recovery log files missing or the log control file missing for that Queue Manager? (a pretty obvious question really)
_________________
Glenn |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Sun Aug 30, 2009 11:33 pm Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
| gbaddeley wrote: |
| Are any of the recovery log files missing or the log control file missing for that Queue Manager? (a pretty obvious question really) |
yes, all the log files are missing... |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Aug 31, 2009 12:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| itsme_001 wrote: |
| gbaddeley wrote: |
| Are any of the recovery log files missing or the log control file missing for that Queue Manager? (a pretty obvious question really) |
yes, all the log files are missing... |
Then find out who did it, trout them as you explain the error of their ways and the future righteous path. Follow jeevan's advice about how to recover, although be warned that whilst it usually works, it is not guaranteed.
_________________
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 |
|
|
| gbaddeley |
| Posted: Mon Aug 31, 2009 4:27 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| exerk wrote: |
| Then find out who did it, trout them as you explain the error of their ways and the future righteous path. Follow jeevan's advice about how to recover, although be warned that whilst it usually works, it is not guaranteed. |
Exerk, I was going to add a line to my post
"A well-meaning sys admin may have noticed that /var/mqm was getting full, and to free up some space, deleted a bunch of large files that didn't appear to have been accessed in a while, not knowing that the MQ recovery log files are critical to the startup and operation of queue managers."
I have witnessed this happening more than once.
_________________
Glenn |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 31, 2009 7:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| gbaddely wrote: |
"A well-meaning sys admin may have noticed that /var/mqm was getting full, and to free up some space, deleted a bunch of large files that didn't appear to have been accessed in a while, not knowing that the MQ recovery log files are critical to the startup and operation of queue managers."
I have witnessed this happening more than once |
And here I thought that's why we had support packs for managing linear log files... (like MS0L and others). 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Aug 31, 2009 8:56 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| fjb_saper wrote: |
| And here I thought that's why we had support packs for managing linear log files... (like MS0L and others). |
I've seen the "missing logs" problem more with circular logs, where there are a lots of large logs and they take days or weeks to cycle around (as per the modification date/time shown by ls -l).
_________________
Glenn |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 01, 2009 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Maybe that's why we define lots of filespace but only 2 primary log files.
If the secondaries are not used they are not there and nobody will delete them...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Sep 01, 2009 7:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| If the secondaries are not used they are not there and nobody will delete them... |
An odd solution to this problem. As a clue to the clueless, you could name the log filepath /dontdeleteoryouwillbefired/.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Tue Sep 01, 2009 7:19 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| bruce2359 wrote: |
| Quote: |
| If the secondaries are not used they are not there and nobody will delete them... |
An odd solution to this problem. As a clue to the clueless, you could name the log filepath /dontdeleteoryouwillbefired/. |
Ha ha. This is great.
This is also a great form of obfuscation so if you ever get people on the box that shouldnt be there they will have no idea whats what. Brilliant.
Just make sure you password protect your Excel spreadsheet that describes what your quirky names really are. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 01, 2009 7:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WMBDEV1 wrote: |
| Just make sure you password protect your Excel spreadsheet that describes what your quirky names really are. |
I feel this name is perfectly descriptive!
I personally find a training programme based on the same preceipts, i.e. explaining to the sys admins that they will be fired if they mess with "my" stuff (after I've done unspeakable things to them) is effective. And fun.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
