Getting error "AMQ8101: WebSphere MQ error (10806228) has occurred" when trying to start the command server in MQ

Question

I'm Getting error AMQ8101: WebSphere MQ error (10806228) has occurred when trying to start the command server in MQ.

The MQ version which we are using is 7.1.0.6 and the environment is SunOS.

Please need your suggestions.

Below is the FDC file created:

+-----------------------------------------------------------------------------+
|                                                                             |
| WebSphere MQ First Failure Symptom Report                                   |
| =========================================                                   |
|                                                                             |
| Date/Time         :- Sun July 09 2017 15:15:37 MEST                         |
| UTC Time          :- 1499606137.840536                                      |
| UTC Time Offset   :- 120 (MET)                                              |
| Host Name         :- abcd                                             |
| Operating System  :- SunOS 5.10                                             |
| PIDS              :- 5724H7223                                              |
| LVLS              :- 7.1.0.6                                                |
| Product Long Name :- WebSphere MQ for Solaris (SPARC platform)              |
| Vendor            :- IBM                                                    |
| Installation Path :- /opt/mqm                                               |
| Installation Name :- Installation1    (1)                                   |
| Probe Id          :- ZT160001                                               |
| Application Name  :- MQM                                                    |
| Component         :- zusStartManager                                        |
| SCCS Info         :- lib/zu/amqzupt0.c, 1.54.1.2                            |
| Line Number       :- 1887                                                   |
| Build Date        :- Nov 14 2014                                            |
| CMVC level        :- p710-006-141112                                        |
| Build Type        :- IKAP - (Production)                                    |
| Effective UserID  :- 325 (mqm)                                              |
| Real UserID       :- 0 (root)                                               |
| ProjectID         :- 0                                                      |
| Program Name      :- strmqcsv                                               |
| Arguments         :- QM.XYZ.                                             |
| Addressing mode   :- 64-bit                                                 |
| LANG              :-                                                        |
| Process           :- 9398                                                   |
| Thread            :- 1                                                      |
| QueueManager      :- QM.XYZ                                             |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 280898                                                 |
| ConnId(3) QM-P    :- 72653                                                  |
| Last HQC          :- 3.0.0-18240                                            |
| Last HSHMEMB      :- 1.0.0-4454576                                          |
| Major Errorcode   :- xecX_W_DAEMON_UNAVAILABLE                              |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- INCORROUT                                              |
| Probe Severity    :- 3                                                      |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred.  |
| FDCSequenceNumber :- 0                                                      |
| Arith1            :- 9495 (0x2517)                                          |
| Arith2            :- 50 (0x32)                                              |
| Comment1          :- Timed-out waiting for process manager to start.        |
|                                                                             |
+-----------------------------------------------------------------------------+

Answer 1

I'll start off by mentioning that IBM MQ v7.1 went out of support on April 30th 2017. I would recommend that you move to a supported level of IBM MQ. Keep in mind that IBM MQ v7.5 goes out of support on April 30th 2018. Dates have not been announced for v8 or v9 yet, but IBM commits to at least 5 years of support which would give them support until at least June 2019 for v8 and June 2021 for v9.

---

The IBM MQ Technote "Common WebSphere MQ messages and most likely causes " indicates a FDC may be created in /var/mqm/errors when a AMQ8101 is returned. If a FDC is created can you please edit your question and add the top portion of the FDC file?

---

If you run mqrc against that error code as a hex error code it comes back with the following:

$ mqrc 0x10806228

 276849192  0x10806228  xecX_W_DAEMON_UNAVAILABLE

IBM has stated to me in past PMRs that IBM MQ "... traditionally dumps out the hex value for return codes that it does not know about. When this happens then it normally means we have hit an error path that we didn't expect and so we should try to fix this by adding a new message."

In APAR IT16270 they described a different unexpected error being returned as "a coding error resulted in an internal undocumented error code ... being returned to the application."

Based on this if it reproducible in a supported version of IBM MQ or if you have a extended support contract for v7.1 I would suggest opening a PMR with IBM to troubleshoot the issue.

---

UPDATE 2017-07-10

Based on the FDC indicating Timed-out waiting for process manager to start and further information from the OP that a restart of the queue manager solved the problem, I believe the amqzmur0 process was hung and not responding, this is the "Restartable process manager". Restarting the queue manager would have restarted this process.