| Author |
Message
|
| somsayan |
 Posted: Thu Aug 05, 2010 9:15 pm Post subject: AMQ6109, AMQ6183 and AMQ6184 messages on AIX (Solved) |
 |
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
Hi, I need urgent help please....
We have MQ 5.3 running on AIX
sysb /var/mqm/qmgrs>dspmqver
Name: WebSphere MQ
Version: 530.12 CSD12
CMVC level: p530-12-L051208
BuildType: IKAP - (Production)
sysb /var/mqm/qmgrs>uname -a
AIX sysb 3 4 0003AC9F4C00
The system has two queue managers. We can't get one of the queue manager to start. It fails with the following errors.
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- ±Ý¿äÀÏ 8¿ù 06 10:17:49 KORST 2010
Host Name :- sysb (AIX 4.3)
PIDS :- 5724B4101
LVLS :- 530.12 CSD12
Product Long Name :- WebSphere MQ for AIX
Vendor :- IBM
Probe Id :- XC338001
Application Name :- MQM
Component :- xehAsySignalHandler
Build Date :- Dec 8 2005
CMVC level :- p530-12-L051208
Build Type :- IKAP - (Production)
UserID :- 00000516 (mqm)
Program Name :- strmqm
Process :- 00086446
Thread :- 00000002
Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL
Minor Errorcode :- OK
Probe Type :- MSGAMQ6209
Probe Severity :- 3
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
FDCSequenceNumber :- 1
Arith1 :- 2 2
Comment1 :- SIGINT
===============================================
While the other queue manager can be started properly.
Please advice
Last edited by somsayan on Fri Aug 06, 2010 10:37 pm; edited 1 time in total |
|
| Back to top |
|
 |
| zonko |
| Posted: Thu Aug 05, 2010 9:56 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
The FFST you have posted is a report that the UNIX signal SIGINT has been sent to strmqm and it has been ignored. It has nothing to do with whether the qmgr can start or not.
Are there any more FFSTs?
What do the error logs say?
What happened on the machine between the time the qmgr last ran and you stopped it, and this attempt to start it? It seems unlikely that you stopped the qmgr and then it just would not start, without something else happening.
What does it do when you try to start it?
Display something, display an error msg, just sit there, what?
I expect it just sits there, and the XC338001 FFST is written when you press CTRL-C to stop it starting.
You are in a bit of trouble now, since IBM will not help you because your WMQ version is unsupported. |
|
| Back to top |
|
|
| somsayan |
| Posted: Thu Aug 05, 2010 10:24 pm Post subject: |
|
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
The other FFST is this
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- ±Ý¿äÀÏ 8¿ù 06 12:39:54 KORST 2010
Host Name :- sysb (AIX 4.3)
PIDS :- 5724B4101
LVLS :- 530.12 CSD12
Product Long Name :- WebSphere MQ for AIX
Vendor :- IBM
Probe Id :- XC130003
Application Name :- MQM
Component :- xehExceptionHandler
Build Date :- Dec 8 2005
CMVC level :- p530-12-L051208
Build Type :- IKAP - (Production)
UserID :- 00000516 (mqm)
Program Name :- amqhasmx
Process :- 00071652
Thread :- 00000001
QueueManager :- AS300D002
Major Errorcode :- STOP
Minor Errorcode :- OK
Probe Type :- HALT6109
Probe Severity :- 1
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
FDCSequenceNumber :- 0
Arith1 :- 11 b
Comment1 :- SIGSEGV
===============================================
When I try to start the queue manager, it just sits there.
And the server was restarted by the admin team and after that the queue manager refused to start. The admin team claims to have made no change. [ i doubt them though]
The queue manager error log says
============================================
10/08/06 15:10:00
AMQ6184: An internal WebSphere MQ error has occurred on queue manager AS300D002.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been
called. The failing process is process 34846.
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.
============================================
But I can't seem to find the PID mentioned in the logs. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 05, 2010 11:40 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
amqhasmx is the logger process and the PID would have disappeared by the time you tried to find it. Check you have sufficient log space.
_________________
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 |
|
|
| somsayan |
| Posted: Fri Aug 06, 2010 12:13 am Post subject: |
|
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
| The disk space usage is just 20%. And the user is also not limited in disk usage. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 06, 2010 12:40 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
A faster way is probably to delete it and recreate it...
However it seems that you're still on AIX 4.3?
| Quote: |
| AIX sysb 3 4 0003AC9F4C00 |
I doubt very much that the hardware / OS is still supported.
My best bet: Upgrade the hardware, upgrade the software. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| somsayan |
| Posted: Fri Aug 06, 2010 12:50 am Post subject: |
|
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
We are having a new server upgrade and MQ 7.0.1.1 installed on it. But that's going to take some time. So in the mean time we are having the old setup.
Last night the queue manager went down and till now we are not able to get the queue manager up.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 06, 2010 1:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| somsayan wrote: |
We are having a new server upgrade and MQ 7.0.1.1 installed on it. But that's going to take some time. So in the mean time we are having the old setup.
Last night the queue manager went down and till now we are not able to get the queue manager up. |
If you plan on using java and JMS you really want to go to 7.0.1.2. Check the number of bugs fixed in between and you really want to go to 7.0.1.2
As a VERY UNSUPPORTED try ==> attempt it first in a DEV environment, you could try following:
- archive /var/mqm/qmgrs/<badqmgr>
- Delete the qmgr.
- Recreate the qmgr.
- If you do not need the data, just restore from the last saveqmgr backup.
- If you need the data (messages), UNSUPPORTED hack here -- at your own risk!
- start up the qmgr.
- shut down the qmgr.
- Restore /var/mqm/qmgrs/<thisqmgr> from the badqmgr backup.
- Make sure file permissions match rw-rw-r mqm:mqm (directories also need execute)...
- try to restart...
You might also want to verify the contents of /var/mqm/mqs.ini and /var/mqm/qmgrs/<badqmgr>/qm.ini
Of course this needs to happen on the same version of MQ, preferably same OS too.
However if a file got corrupted you might get the same response as you currently have...
Have fun
_________________
MQ & Broker admin
Last edited by fjb_saper on Fri Aug 06, 2010 1:41 am; edited 4 times in total |
|
| Back to top |
|
|
| somsayan |
| Posted: Fri Aug 06, 2010 1:24 am Post subject: |
|
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
| Nope, we don't use java or JMS. We basically use the C programs and MQ to transfer files from one server to the other. |
|
| Back to top |
|
|
| somsayan |
| Posted: Fri Aug 06, 2010 10:35 pm Post subject: |
|
|
Apprentice
Joined: 06 Apr 2007
Posts: 49
|
| fjb_saper wrote: |
As a VERY UNSUPPORTED try ==> attempt it first in a DEV environment, you could try following:
- archive /var/mqm/qmgrs/<badqmgr>
- Delete the qmgr.
- Recreate the qmgr.
- If you do not need the data, just restore from the last saveqmgr backup.
|
Thank you very much. this seemed to work like magic. The difference in the qm.ini file was the log buffer size ( LogBufferPages) . The buffer size, someone set it to 4096, which is not compatible for MQ 5.3 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Aug 07, 2010 2:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| somsayan wrote: |
| fjb_saper wrote: |
As a VERY UNSUPPORTED try ==> attempt it first in a DEV environment, you could try following:
- archive /var/mqm/qmgrs/<badqmgr>
- Delete the qmgr.
- Recreate the qmgr.
- If you do not need the data, just restore from the last saveqmgr backup.
|
Thank you very much. this seemed to work like magic. The difference in the qm.ini file was the log buffer size ( LogBufferPages) . The buffer size, someone set it to 4096, which is not compatible for MQ 5.3 |
Find the culprit and  him/her. I guess this is already done if you were the one...
Seriously you have a lesson learned here... do not allow access to the qm.ini to non MQAdmins... and revert to previous value if after a change the qmgr refuses to start...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
