| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9213 Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rockstar |
 Posted: Thu Apr 05, 2007 4:25 am Post subject: AMQ9213 Error |
 |
|
Newbie
Joined: 05 Apr 2007
Posts: 3
|
Hello all.
I am a new participant, so I would very much appreciate any assistance anyone can give.
On an AIX server, with newly installed WMQ v5.3 software. I am trying to start up a new series of Qmanagers. I can create the Qmanager and objects fine. However, when I try to start a listener, I get the AMQ9213 error. The listener is not started and I can not connect via my Windows WMQ Explorer, or any other way (mainframe, other WMQ server Qmanagers, etc.)
If anyone has experienced this problem, and has a solution, I would be very grateful.
Below is the information in the error log: 
AMQ9213: A communications error for bind occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the bind(/tmp/MQSeries.303614) call was 13 (X'D'). Record
these values and tell the systems administrator.
----- amqxfdcx.c : 671 --------------------------------------------------------
04/03/07 14:48:31
AMQ9213: A communications error for bind occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
:
Tthese values and tell the systems administrator.0) call was 13 (X'D'). Record |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Apr 05, 2007 4:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Not directly connected to your problem, but why are you doing anything new with v5.3? Go to v6!
Moving to your issue, you say you have a series of queue managers - do they all display this problem? Are they all listening on different ports (obvious I know but seen it tried)? Are you sure the port you've selected is vacant?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Rockstar |
| Posted: Thu Apr 05, 2007 5:32 am Post subject: |
|
|
Newbie
Joined: 05 Apr 2007
Posts: 3
|
I agree with the v6 comment. But, internal issues and project deadlines caused the v5.3 install.
Yes, each Qmanager is going to run on a different port. Right now I only have two running, out of 15 generated. Each of the two as a unique listener port.
I have used the netstat command to verify that nothing else is listening on the ports I have specified.
All indications are that there could very possibly have been something missed on the v5.3 install itself. A separate System Support group loaded the software and these folks are not WMQ experts. Could any parameters on the create have caused this? Are there any parms that should always be modified from the supplied default ones on installation that you would know of? Kinda feels like something like that. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 05, 2007 5:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the install succeeded, then everything necessary to start a listener should have been installed.
Ensure that the mqm user has the necessary permissions, and that the user attempting to start the listener has the necessary permissions, and that nobody has mucked with the file permissions on the install.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Rockstar |
| Posted: Fri Apr 06, 2007 3:29 am Post subject: |
|
|
Newbie
Joined: 05 Apr 2007
Posts: 3
|
We found the problem after contacting IBM WMQ Lvl 1 support:
The permissions for the tmp directory in the root directory were not set correctly on installation and it could not be written to  . Evidentially WMQ uses this directory to store information when it performs tasks. Our AIX Systems Admin set the permissions to 777, and everything now works. Never would have found this.
My thanks to jefflowrey and Vitor for responding. Hopefully I will be able to return the favor one day. |
|
| 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
|
|
|
|
