| Author |
Message
|
| okiedokie |
 Posted: Wed Apr 12, 2006 8:20 am Post subject: AMQ7880: Error code 20 - My Qmgrs keep shutting down |
 |
|
Newbie
Joined: 12 Oct 2005
Posts: 8
|
We are running version 5.30 on a W2000 machine (service pack 4). I have 2 Qmgrs and they will shutdown from time to time. The only information that I am given is this in the AMQERR01 log:
04/12/2006 10:40:13
AMQ7880: Error code 20 starting XXXXDE.PROD/Command Server WebSphere MQ
service.
EXPLANATION:
The service was unable to start XXXXDE.PROD/Command Server. The error message
reported was as follows: Process could not be started - return code 20
ACTION:
Use WebSphere MQ Services to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover.
-------------------------------------------------------------------------------
04/12/2006 10:40:13
AMQ7880: Error code 20 starting XX1/Command Server WebSphere MQ service.
EXPLANATION:
The service was unable to start XX1/Command Server. The error message reported
was as follows: Process could not be started - return code 20
ACTION:
Use WebSphere MQ Services to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover.
I will go into the MQServices, starts the qmgrs and a few hours later ( or maybe days) they will be down again.
Any ideas of where/how to look for more clues? |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Wed Apr 12, 2006 9:24 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Are there any FFST's in mqm/errors, that is to say .FDC file generated. Have you looked at the Application Event logs?
Have you searched Google or the IBM Support site for know issues related to the AMQ7880 error code?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| okiedokie |
| Posted: Wed Apr 12, 2006 9:54 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2005
Posts: 8
|
There have been a few .FDC files, but not for every shutdown of the qmgrs.
What I have found on the IBM website is a reference to deleting the AMQ_SERVICE_MODULE variable. This is not the case here, since that variable does not exist on our machine. |
|
| Back to top |
|
|
| xxx |
| Posted: Wed Apr 12, 2006 10:23 am Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
First step will be to know what changes have been done recenlty if it was running fine before,
Some times on Windows a reboot should fix the things,
Finally not a bad idea to upgrade to CSD12 |
|
| Back to top |
|
|
| okiedokie |
| Posted: Wed Apr 12, 2006 10:27 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2005
Posts: 8
|
Rebooting may/may not fix things. I rebooted once and the problem reoccured a few hours later.
As far as what changes have happened recently? oy 
This machine has not been heavily used, the AMQERR01 log file actually has info back to 2004! I looked back and this seemed to have started in March of this year, but the SA is unaware of any changes.
How do I find out what CSD I am currently at? |
|
| Back to top |
|
|
| mattfarney |
| Posted: Wed Apr 12, 2006 10:29 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
The only thing we noticed of interest in the FDC files was this behavior:
-} xcsWaitEventSem rc=xecL_W_TIMEOUT
} zcpReceiveOnPipe rc=zrcC_E_TIMEOUT
{ xcsCheckHandle
} xcsCheckHandle rc=OK
{ xllLongLockRequest
} xllLongLockRequest rc=OK
{ xcsCheckProcess
} xcsCheckProcess rc=OK
{ xllLongLockRelease
} xllLongLockRelease rc=OK
{ zapInquireStatus
-{ xllLongLockRequest
-} xllLongLockRequest rc=OK
-{ xllLongLockRelease
-} xllLongLockRelease rc=OK
} zapInquireStatus rc=OK
{ zcpReceiveOnPipe
-{ xcsWaitEventSem
-} xcsWaitEventSem rc=xecL_W_TIMEOUT
} zcpReceiveOnPipe rc=zrcC_E_TIMEOUT
{ xcsCheckHandle
} xcsCheckHandle rc=xecP_E_INVALID_PID
I think this is saying that MQ was waiting for a semaphore, and eventually timed out and gave up.
-mf |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 10:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What's the header block of the most recent FDC file?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| okiedokie |
| Posted: Wed Apr 12, 2006 10:43 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2005
Posts: 8
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tue April 11 17:42:33 Eastern Daylight Time 2006 |
| Host Name :- XXXX01 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZL000010 |
| Application Name :- MQM |
| Component :- zlaMain |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- xxxxxxx |
| Process Name :- E:\MQ\bin\amqzlaa0.exe |
| Process :- 00005912 |
| Thread :- 00000001 |
| QueueManager :- xxxxxx!PROD |
| 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 |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 11:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This is really really fascinating!
You should entirely open a PMR for this. There's no indication of your Probe ID on IBM's website.
There is this: http://www-1.ibm.com/support/docview.wss?uid=swg21115953
But it's old, and it probably doesn't relate.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Apr 12, 2006 11:06 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
It looks like a "unserviced" MQ...did you apply ANY CSDs? (I think not, as your FFST doesn't show anything and other FFST's posted show:
| Quote: |
| | LVLS :- 530.11 CSD11 | |
) Can you show the output of "mqver" ?
In any case, I'd upgrade my CSD level.
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 11:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess I was confused by the earlier comment about "service pack 4" - I had assumed that meant MQ CSD4, rather than Windows Sp4.
Definitely apply CSD12. Or at least 11.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| okiedokie |
| Posted: Wed Apr 12, 2006 11:58 am Post subject: |
|
|
Newbie
Joined: 12 Oct 2005
Posts: 8
|
I have opened up a PMR and it looks like we will be planning on installing some CSDs.
Thanks for the help guys. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 13, 2006 6:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| okiedokie wrote: |
| I have opened up a PMR and it looks like we will be planning on installing some CSDs. |
You only need 1, as they are cummalative. Put the latest on, which is CSD12. 99.99% sure that will solve your problems.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mattfarney |
| Posted: Tue Apr 25, 2006 10:23 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
We applied the CSD and are still getting the same errors. The FDC file is identical (except for the Date/Time, CMVC level, and processId).
I guess the next stop is IBM support...
-mf |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Apr 25, 2006 10:32 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Does mattfarney work with okiedokie? I didn't previously realize we were talking to two different customers.
_________________
-wayne |
|
| Back to top |
|
|
|
|
