| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The Queue Manager ended for reason 2341977372233826304 '' |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqfan |
 Posted: Fri Feb 20, 2009 4:46 am Post subject: The Queue Manager ended for reason 2341977372233826304 '' |
 |
|
Novice
Joined: 12 Feb 2007
Posts: 11
|
Hello,
I bumped into an issue on AIX Server with MQ V6.0.2.3 and I dont seem to have a solution for it.
I have been told by the application guys that they are not able to connect to a Queue Manager and apparently I could see the Queue Manager ENDED UNEXPECTEDLY. I checked the error logs and found a huge number of channel failures due to sequence number mismatch. No FDCs were generated. So I proceeded and tried to bring up the Queue Manager:
1. Clear shared memory and saw few of them were not getting cleared. (This action generated an FDC with Probe: 5724H7201) - But it was self explanatory and doesnt seem to have been generated while the Queue Manager termination. The comment portion looks like this:
Comment1 :- Failed to Delete File: |
| /var/mqm/qmgrs/QM/@ipcc/shmem/shm.4 [rc=-1 errno=5] There is an input |
| or output error. |)
2. Looked at anymore MQ processes running: (i should have done this beforehand - my fault). Found the amrmppa and then killed it.
3. Cleared the shared memory.
4. strmqm QM and got this error:
WebSphere MQ queue manager 'QM' starting.
The Queue Manager ended for reason 2341977372233826304 ''
Each time I try to start the QM an FDC is generated but the FDC file size will be '0'.
Converted the error to hexa 2341977372233826304=20806003
C:\Documents and Settings>mqrc 0x20806003
545284099 0x20806003 xecF_E_FAIL.
I tried to search in this forum and google with different options - but could find only one relevant link, when searched with xecF_E_FAIL: http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IY85622
I thought this is relevant because I see a lot of channel termination errors in the log, but again we are on version 6.0.2.3
/home/mqm $ dspmqver
Name: WebSphere MQ
Version: 6.0.2.3
CMVC level: p600-203-080123
BuildType: IKAP - (Production)
and
/var/mqm/errors $ oslevel
5.3.0.0
Have anyone of you encountered such a situation? How do I bring up the Queue Manager back?
Let me know if you need more information which might help pin point the issue and resolve it. All your help is appreciated.
Regards.
_________________
Ability is what you're capable of doing.
Motivation determines what you do.
But attitude determines how well you do it. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Fri Feb 20, 2009 5:17 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
what is there in FDC? is it still shows 0 KB
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Feb 20, 2009 5:36 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
| And oslevel -s will give you what you really need to know about the AIX. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Feb 20, 2009 7:54 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
Interesting, the error from /var/mqm/errors/AMQERR01.LOG is:
----- amqxfdcx.c : 813 --------------------------------------------------------
02/20/09 06:30:16 - Process(52858.1) User(mqm) Program(amqzxma0_nd)
AMQ6119: An internal WebSphere MQ error has occurred ('5 - There is an input or
output error.' from open.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 768 --------------------------------------------------------
The FDC with data in it, and there are several that do not have data in them, is:
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tuesday February 17 07:51:18 CST 2009 |
| Host Name :- prxappb (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XY404017 |
| Application Name :- MQM |
| Component :- xstDestroyExtentByName |
| SCCS Info :- lib/cs/unix/amqxstex.c, 1.83.1.9 |
| Line Number :- 2743 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000218 (mqm) |
| Program Name :- dspmq |
| Addressing mode :- 64-bit |
| Process :- 69300 |
| Thread :- 1 |
| ConnId(1) IPCC :- 0 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Failed to Delete File: /var/mqm/qmgrs/QXPR2T/@ipcc/shmem/shm.2 [rc=-1 |
| errno=5] There is an input or output error.) |
| FDCSequenceNumber :- 1 |
| Arith1 :- 5 5 |
| Comment1 :- Failed to Delete File: |
| /var/mqm/qmgrs/QXPR2T/@ipcc/shmem/shm.2 [rc=-1 errno=5] There is an input |
| or output error. |
| Comment2 :- There is an input or output error. |
| |
+-----------------------------------------------------------------------------+ |
I don't see the shm.2 file but I do see what looks like an extraneous directory, PerQUEUE.
Should that directory exist? Note, there's nothing in it. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Feb 22, 2009 5:01 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2498
Location: Melbourne, Australia
|
Unexpected operating system I/O error on shared memory --> Contact your system administrator.
_________________
Glenn |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Mar 02, 2009 1:35 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA
|
| Yes, this was SAN issues. A quick test of creating a file and deleting the file demonstrated to the SA that it really was a UNIX problem and not an MQ problem. They fixed and it fired up. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
