| Author |
Message
|
| shagam |
 Posted: Mon Dec 15, 2008 5:00 am Post subject: AMQ8101:Unable to start the queue manager |
 |
|
Newbie
Joined: 25 Nov 2008
Posts: 3
|
Hi,
I am getting the below error while starting the queue manager.No FDC files are generated and the error log is not updated.
AMQ8101: WebSphere MQ error (20806021) has occurred.
While trying to delete the queue manager I am getting "WebSphere MQ queue manager running". However, when I grep for mq,mqm,amq* I can't find anything running.
MQ version : 5.3 CSD10
O/S : Linux 2.4.21-32.0.1.ELsmp
LD_ASSUME_KERNEL : 2.4.19 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 15, 2008 5:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Forgive a slightly stupid question, but which Linux is this? It's not obvious to me, and that perhaps has a lot to do with my lack of Linux.
Has this queue manager ever started, i.e. is it now failing, or is this your first queue manager under this configuration?
Have you tried some of the resolution strategies previously posted, e.g. changing or unsetting LD_ASSUME_KERNEL?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shagam |
| Posted: Mon Dec 15, 2008 11:37 pm Post subject: |
|
|
Newbie
Joined: 25 Nov 2008
Posts: 3
|
| Quote: |
| Forgive a slightly stupid question, but which Linux is this? It's not obvious to me, and that perhaps has a lot to do with my lack of Linux. |
Sorry.I have little knowledge on Linux.Below is the ouput from my system
>uname -a
Linux 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 i386 GNU/Linux
The queue manager was working earlier without any issues.No fix pack was applied.The last generated FDC file looks like the below
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday December 03 14:58:38 HKT 2008 |
| Host Name :- (Linux 2.4.21-32.0.1.ELsmp) |
| PIDS :- 5724B4104 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- ZS142005 |
| Application Name :- MQM |
| Component :- zslEnqueue |
| Build Date :- May 12 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000901 (mqm) |
| Program Name :- strmqm |
| Thread-Process :- 00012422 |
| Thread :- 00000001 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.4.19 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- Unknown(D) |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (D) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 13 d |
| |
+-----------------------------------------------------------------------------+
The below link recommends to install the latest fixpack.How to check whether the problem stated above is fixed in the fix pack (How to get the APARS/Problem number)
http://www.mqseries.net/phpBB/viewtopic.php?p=179586&sid=71a43d2b3433cf5661fa33dd53c336be |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 16, 2008 1:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shagam wrote: |
The below link recommends to install the latest fixpack.How to check whether the problem stated above is fixed in the fix pack (How to get the APARS/Problem number)
|
WMQV5.3 fixes are listed here:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27007825
Given that what you've posted is a symptom rather than a root cause you may find it difficult to gain certainty. It's generally held you should be on the latest level of v5.3, and ideally on v6 at this point (v5.3 being out of support).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shagam |
| Posted: Tue Dec 16, 2008 2:24 am Post subject: |
|
|
Newbie
Joined: 25 Nov 2008
Posts: 3
|
The link shows the fix list for MQ 5.3 with APAR & Description. Is it possible to find out the APAR from the FDC or from the error ( APAR description on the page does not have anything related to the error). This is to confirm the team that the issue will be resolved when the latest fixpack (Fixpack 14) is installed. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 16, 2008 2:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shagam wrote: |
| Is it possible to find out the APAR from the FDC or from the error ( APAR description on the page does not have anything related to the error). |
No. You have a symptom not a root cause. If you want this, submit the FDC to IBM via a PMR and ask them.
| shagam wrote: |
| This is to confirm the team that the issue will be resolved when the latest fixpack (Fixpack 14) is installed. |
I did say it would be difficult to gain certainty. You should also be convincing the team to go to v6.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
