Re: AMQ9213 & Bind failures on Solaris
Larry, Where would one find these errors documented? Thanks, tonyB. > -Original Message- > From: MQSeries List [mailto:[EMAIL PROTECTED] On > Behalf Of Larry Hendersen > Sent: Thursday, January 22, 2004 11:46 AM > To: [EMAIL PROTECTED] > Subject: Re: AMQ9213 & Bind failures on Solaris > > There was an error 13 in the FDC. errno 13 is EACCESS, > permission denied. > > >From: Antony Boggis <[EMAIL PROTECTED]> > >Reply-To: MQSeries List <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: AMQ9213 & Bind failures on Solaris > >Date: Wed, 21 Jan 2004 21:44:05 -0800 > > > >Some good suggestions. > > > >However, for future reference to all this turned out to be a Solaris > >permissions issue. Somehow permissions on /tmp had been reset and no > >userID (except root) was able to write files there. > > > >At one point I had a sev 1 PMR open on this. what finally > clued me in > >(I can be slow sometimes) was that the logs were reporting > files like > >/tmp/MQSeries.xxx.xxx and there was nothing in /tmp. Hope this helps > >someone else out. Even IBM support missed this one. > > > >Regards, > > > >tonyB. > > > > > > > > > > From: MQSeries List > [mailto:[EMAIL PROTECTED] On Behalf > >Of Dhavala > > Sent: Wednesday, January 21, 2004 4:45 PM > > To: [EMAIL PROTECTED] > > Subject: Re: AMQ9213 & Bind failures on Solaris > > > > > > > >From the FFST it looks like the program is "runmqlsr" and > which would > >mean that even though you believe your listener is starting > and binding > >the port you asked for, fine enough, it sure seems to have > some issues. > >Try using some other port or find out who is using that particular > >port(1414, if it is so). > > > >Cheers > >Kumar > > > > > > > > _ > There are now three new levels of MSN Hotmail Extra Storage! > Learn more. > http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1 > > Instructions for managing your mailing list subscription are > provided in the Listserv General Users Guide available at > http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: AMQ9213 & Bind failures on Solaris
There was an error 13 in the FDC. errno 13 is EACCESS, permission denied.
From: Antony Boggis <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: AMQ9213 & Bind failures on Solaris
Date: Wed, 21 Jan 2004 21:44:05 -0800
Some good suggestions.
However, for future reference to all this turned out to be a Solaris
permissions issue. Somehow permissions on /tmp had been reset and no
userID (except root) was able to write files there.
At one point I had a sev 1 PMR open on this. what finally clued me in (I
can be slow sometimes) was that the logs were reporting files like
/tmp/MQSeries.xxx.xxx and there was nothing in /tmp. Hope this helps
someone else out. Even IBM support missed this one.
Regards,
tonyB.
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf
Of Dhavala
Sent: Wednesday, January 21, 2004 4:45 PM
To: [EMAIL PROTECTED]
Subject: Re: AMQ9213 & Bind failures on Solaris
From the FFST it looks like the program is "runmqlsr" and which would
mean that even though you believe your listener is starting and binding
the port you asked for, fine enough, it sure seems to have some issues.
Try using some other port or find out who is using that particular
port(1414, if it is so).
Cheers
Kumar
_
There are now three new levels of MSN Hotmail Extra Storage! Learn more.
http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: AMQ9213 & Bind failures on Solaris
Some good suggestions. However, for future reference to all this turned out to be a Solaris permissions issue. Somehow permissions on /tmp had been reset and no userID (except root) was able to write files there. At one point I had a sev 1 PMR open on this. what finally clued me in (I can be slow sometimes) was that the logs were reporting files like /tmp/MQSeries.xxx.xxx and there was nothing in /tmp. Hope this helps someone else out. Even IBM support missed this one. Regards, tonyB. From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of DhavalaSent: Wednesday, January 21, 2004 4:45 PMTo: [EMAIL PROTECTED]Subject: Re: AMQ9213 & Bind failures on Solaris From the FFST it looks like the program is "runmqlsr" and which would mean that even though you believe your listener is starting and binding the port you asked for, fine enough, it sure seems to have some issues. Try using some other port or find out who is using that particular port(1414, if it is so). Cheers Kumar
Re: AMQ9213 & Bind failures on Solaris
You may need to double check that you or someone didn't accidentally
configure the listener within the inetd.conf and services file. Then if
you are trying to run runmqlsr it will complain that someone has that port.
Another recommendation for UNIX is to actually use the top end port numbers
(1+), especially when you have multiple QMGRs. It's not required, but
could resolve some headaches later on. Plus you can scream at the
developers if they try to use those ports ;-)
Chris
|-+>
| | Dhavala |
| | <[EMAIL PROTECTED]|
| | .NET>|
| | Sent by: |
| | "MQSeries List" |
| | <[EMAIL PROTECTED]|
| | n.AC.AT> |
| ||
| ||
| | 01/21/2004 04:16 |
| | PM |
| | Please respond to|
| | "MQSeries List" |
| ||
|-+>
>--|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: AMQ9213 & Bind failures on Solaris
|
|
|
>--|
From the FFST it looks like the program is "runmqlsr" and which would mean
that even though you believe your listener is starting and binding the
port you asked for, fine enough, it sure seems to have some issues. Try
using some other port or find out who is using that particular port(1414,
if it is so).
Cheers
Kumar
---Original Message---
From: MQSeries List
Date: Wednesday, January 21, 2004 00:56:19
To: [EMAIL PROTECTED]
Subject: AMQ9213 & Bind failures on Solaris
Env: Solaris 5.8, WMQ 5.3 CSD05
I have a clustered queue manager that is reporting bind errors.
Specifically:
AMQ9213: A communications error for bind occurred.
In the error log, I am getting bind error 13.
Along with the error log reports, I am getting generated FDC files:
+---
--+
|
|
| WebSphere MQ First Failure Symptom Report
|
| =
|
|
|
| Date/Time :- Tuesday January 20 20:42:09 PST 2004
|
| Host Name :- vdpsusptas02 (SunOS 5.8)
|
| PIDS :- 5724B4103
|
| LVLS :- 530.5 CSD05
|
| Product Long Name :- WebSphere MQ for Sun Solaris
|
| Vendor:- IBM
|
| Probe Id :- RM07
|
| Application Name :- MQM
|
| Component :- cccJobMonitor
|
| Build Date:- Sep 27 2003
|
| CMVC level:- p530-05-L030926
|
| Build Type:- IKAP - (Production)
|
| UserID:- 1002 (jlee)
|
| Program Name :- runmqlsr_nd
|
| Process :- 1437
|
| Thread:- 0003
|
| Major Errorcode :- rrcE_COMMUNICATIONS_ERROR
|
| Minor Errorcode :- OK
|
| Probe Type:- MSGAMQ9213
|
| Probe Severity:- 2
|
| Probe Description :- AMQ9213: A communications error for bind
occurred. |
| FDCSequenceNumber :- 0
|
| Arith1:- 13 d
|
| Arith2:- 13 d
|
| Comment1 :-
|
|
|
| Comment2 :- bind
|
|
|
| Comment3 :- (/tmp/MQSeries.1437)
|
|
|
|
|
+---
--+
.
.
.
Consequently, all the other cluster queue managers that are trying to
communicate to this manager are failing (the cluster sender channel on
these remote queue managers go to a BINDING or
Re: AMQ9213 & Bind failures on Solaris
> Given that the earth's magnetic field is starting to shift You mean 12.000 years have past already??? phew ... time flies :-) Michael -Oorspronkelijk bericht- Van: MQSeries List [mailto:[EMAIL PROTECTED] Rick Tsujimoto Verzonden: woensdag 21 januari 2004 21:26 Aan: [EMAIL PROTECTED] Onderwerp: Re: AMQ9213 & Bind failures on Solaris Given that the earth's magnetic field is starting to shift, it could very well mean north one day. Larry Hendersen <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Re: AMQ9213 & Bind failures on Solaris List <[EMAIL PROTECTED] n.AC.AT> 01/21/2004 10:52 AM Please respond to MQSeries List South? You mean North no doubt. :-) >From: Rick Tsujimoto <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: AMQ9213 & Bind failures on Solaris >Date: Wed, 21 Jan 2004 09:28:52 -0500 > >There's something broken along your comm path to the cluster, e.g. router, >firewall, etc. Get your comm person to check it out. I typically get this >sort of problem when my VPN tunnel between two queue managers goes south. > > > > > Antony Boggis > <[EMAIL PROTECTED]> To: >[EMAIL PROTECTED] > Sent by: cc: > MQSeries ListSubject: AMQ9213 & Bind >failures on Solaris > <[EMAIL PROTECTED] > en.AC.AT> > > > 01/21/2004 12:52 > AM > Please respond > to MQSeries List > > > > > >Env: Solaris 5.8, WMQ 5.3 CSD05 > > >I have a clustered queue manager that is reporting bind errors. >Specifically: > > >AMQ9213: A communications error for bind occurred. > > >In the error log, I am getting bind error 13. > > >Along with the error log reports, I am getting generated FDC files: > > > >+-- ---+ > > | > | > | WebSphere MQ First Failure Symptom Report > | > | = > | > | > | > | Date/Time :- Tuesday January 20 20:42:09 PST 2004 > | > | Host Name :- vdpsusptas02 (SunOS 5.8) > | > | PIDS :- 5724B4103 > | > | LVLS :- 530.5 CSD05 > | > | Product Long Name :- WebSphere MQ for Sun Solaris > | > | Vendor:- IBM > | > | Probe Id :- RM07 > | > | Application Name :- MQM > | > | Component :- cccJobMonitor > | > | Build Date:- Sep 27 2003 > | > | CMVC level:- p530-05-L030926 > | > | Build Type:- IKAP - (Production) > | > | UserID:- 1002 (jlee) > | > | Program Name :- runmqlsr_nd > | > | Process :- 1437 > | > | Thread:- 0003 > | > | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR > | > | Minor Errorcode :- OK > | > | Probe Type:- MSGAMQ9213 > | > | Probe Severity:- 2 > | > | Probe Description :- AMQ9213: A communications error for bind > occurred. | > | FDCSequenceNumber :- 0 > | > | Arith1:- 13 d > | > | Arith2:- 13 d > | > | Comment1 :- > | > | > | > | Comment2 :- bind > | > | > | > | Comment3 :- (/tmp/MQSeries.1437) > | > | > | > | > | > >+-- ---+ > > . > . > . > > >Consequently, all the other cluster queue managers that are trying to >communicate to this manager are failing (the cluster sender channel on >these remote queue managers go to a BINDING or RETRYING state). > > >I don't see anything also binding to the port (1414). The listener (not >using inetd) process starts fine (it terminates if it can't bin
Re: AMQ9213 & Bind failures on Solaris
If the listener is running properly you can telnet to it and get a blank screen, if not running you get a connection broken from telnet... Michael -Oorspronkelijk bericht-Van: MQSeries List [mailto:[EMAIL PROTECTED]Namens DhavalaVerzonden: woensdag 21 januari 2004 23:17Aan: [EMAIL PROTECTED]Onderwerp: Re: AMQ9213 & Bind failures on Solaris From the FFST it looks like the program is "runmqlsr" and which would mean that even though you believe your listener is starting and binding the port you asked for, fine enough, it sure seems to have some issues. Try using some other port or find out who is using that particular port(1414, if it is so). Cheers Kumar ---Original Message--- From: MQSeries List Date: Wednesday, January 21, 2004 00:56:19 To: [EMAIL PROTECTED] Subject: AMQ9213 & Bind failures on Solaris Env: Solaris 5.8, WMQ 5.3 CSD05 I have a clustered queue manager that is reporting bind errors. Specifically: AMQ9213: A communications error for bind occurred. In the error log, I am getting bind error 13. Along with the error log reports, I am getting generated FDC files: +-+ | | | WebSphere MQ First Failure Symptom Report | | = | | | | Date/Time :- Tuesday January 20 20:42:09 PST 2004 | | Host Name :- vdpsusptas02 (SunOS 5.8) | | PIDS :- 5724B4103 | | LVLS :- 530.5 CSD05 | | Product Long Name :- WebSphere MQ for Sun Solaris | | Vendor :- IBM | | Probe Id :- RM07 | | Application Name :- MQM | | Component :- cccJobMonitor | | Build Date :- Sep 27 2003 | | CMVC level :- p530-05-L030926 | | Build Type :- IKAP - (Production) | | UserID :- 1002 (jlee) | | Program Name :- runmqlsr_nd | | Process :- 1437 | | Thread :- 0003 | | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR | | Minor Errorcode :- OK | | Probe Type :- MSGAMQ9213 | | Probe Severity :- 2 | | Probe Description :- AMQ9213: A communications error for bind occurred. | | FDCSequenceNumber :- 0 | | Arith1 :- 13 d | | Arith2 :- 13 d | | Comment1 :- | | | | Comment2 :- bind | | | | Comment3 :- (
Re: AMQ9213 & Bind failures on Solaris
From the FFST it looks like the program is "runmqlsr" and which would mean that even though you believe your listener is starting and binding the port you asked for, fine enough, it sure seems to have some issues. Try using some other port or find out who is using that particular port(1414, if it is so). Cheers Kumar ---Original Message--- From: MQSeries List Date: Wednesday, January 21, 2004 00:56:19 To: [EMAIL PROTECTED] Subject: AMQ9213 & Bind failures on Solaris Env: Solaris 5.8, WMQ 5.3 CSD05 I have a clustered queue manager that is reporting bind errors. Specifically: AMQ9213: A communications error for bind occurred. In the error log, I am getting bind error 13. Along with the error log reports, I am getting generated FDC files: +-+ | | | WebSphere MQ First Failure Symptom Report | | = | | | | Date/Time :- Tuesday January 20 20:42:09 PST 2004 | | Host Name :- vdpsusptas02 (SunOS 5.8) | | PIDS :- 5724B4103 | | LVLS :- 530.5 CSD05 | | Product Long Name :- WebSphere MQ for Sun Solaris | | Vendor :- IBM | | Probe Id :- RM07 | | Application Name :- MQM | | Component :- cccJobMonitor | | Build Date :- Sep 27 2003 | | CMVC level :- p530-05-L030926 | | Build Type :- IKAP - (Production) | | UserID :- 1002 (jlee) | | Program Name :- runmqlsr_nd | | Process :- 1437 | | Thread :- 0003 | | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR | | Minor Errorcode :- OK | | Probe Type :- MSGAMQ9213 | | Probe Severity :- 2 | | Probe Description :- AMQ9213: A communications error for bind occurred. | | FDCSequenceNumber :- 0 | | Arith1 :- 13 d | | Arith2 :- 13 d | | Comment1 :- | | | | Comment2 :- bind | | | | Comment3 :- (/tmp/MQSeries.1437) | | | | | +-+ . . . Consequently, all the other cluster queue managers that are trying to communicate to this manager are failing (the cluster sender channel on these remote queue managers go to a BINDING or RETRYING state). I don't see anything also binding to the port (1414). The listener (not using inetd) process starts fine (it terminates if it can't bind to the specified port, right?). I have tried stopping/restarting. Even tried rebuilding and refreshing cluster info. ... to no avail. ___IncrediMail - Email has finally evolved - Click Here
Re: AMQ9213 & Bind failures on Solaris
Given that the earth's magnetic field is starting to shift, it could very well mean north one day. Larry Hendersen <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Re: AMQ9213 & Bind failures on Solaris List <[EMAIL PROTECTED] n.AC.AT> 01/21/2004 10:52 AM Please respond to MQSeries List South? You mean North no doubt. :-) >From: Rick Tsujimoto <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: AMQ9213 & Bind failures on Solaris >Date: Wed, 21 Jan 2004 09:28:52 -0500 > >There's something broken along your comm path to the cluster, e.g. router, >firewall, etc. Get your comm person to check it out. I typically get this >sort of problem when my VPN tunnel between two queue managers goes south. > > > > > Antony Boggis > <[EMAIL PROTECTED]> To: >[EMAIL PROTECTED] > Sent by: cc: > MQSeries ListSubject: AMQ9213 & Bind >failures on Solaris > <[EMAIL PROTECTED] > en.AC.AT> > > > 01/21/2004 12:52 > AM > Please respond > to MQSeries List > > > > > >Env: Solaris 5.8, WMQ 5.3 CSD05 > > >I have a clustered queue manager that is reporting bind errors. >Specifically: > > >AMQ9213: A communications error for bind occurred. > > >In the error log, I am getting bind error 13. > > >Along with the error log reports, I am getting generated FDC files: > > > >+-+ > > | > | > | WebSphere MQ First Failure Symptom Report > | > | = > | > | > | > | Date/Time :- Tuesday January 20 20:42:09 PST 2004 > | > | Host Name :- vdpsusptas02 (SunOS 5.8) > | > | PIDS :- 5724B4103 > | > | LVLS :- 530.5 CSD05 > | > | Product Long Name :- WebSphere MQ for Sun Solaris > | > | Vendor:- IBM > | > | Probe Id :- RM07 > | > | Application Name :- MQM > | > | Component :- cccJobMonitor > | > | Build Date:- Sep 27 2003 > | > | CMVC level:- p530-05-L030926 > | > | Build Type:- IKAP - (Production) > | > | UserID:- 1002 (jlee) > | > | Program Name :- runmqlsr_nd > | > | Process :- 1437 > | > | Thread:- 0003 > | > | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR > | > | Minor Errorcode :- OK > | > | Probe Type:- MSGAMQ9213 > | > | Probe Severity:- 2 > | > | Probe Description :- AMQ9213: A communications error for bind > occurred. | > | FDCSequenceNumber :- 0 > | > | Arith1:- 13 d > | > | Arith2:- 13 d > | > | Comment1 :- > | > | > | > | Comment2 :- bind > | > | > | > | Comment3 :- (/tmp/MQSeries.1437) > | > | > | > | > | > >+-+ > > . > . > . > > >Consequently, all the other cluster queue managers that are trying to >communicate to this manager are failing (the cluster sender channel on >these remote queue managers go to a BINDING or RETRYING state). > > >I don't see anything also binding to the port (1414). The listener (not >using inetd) process starts fine (it terminates if it can't bind to the >specified port, right?). > > >I have tried stopping/restarting. >Even tried rebuilding and refreshing cluster info. > > >... to no avail. > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.a
Re: AMQ9213 & Bind failures on Solaris
South? You mean North no doubt. :-) From: Rick Tsujimoto <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: AMQ9213 & Bind failures on Solaris Date: Wed, 21 Jan 2004 09:28:52 -0500 There's something broken along your comm path to the cluster, e.g. router, firewall, etc. Get your comm person to check it out. I typically get this sort of problem when my VPN tunnel between two queue managers goes south. Antony Boggis <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: cc: MQSeries ListSubject: AMQ9213 & Bind failures on Solaris <[EMAIL PROTECTED] en.AC.AT> 01/21/2004 12:52 AM Please respond to MQSeries List Env: Solaris 5.8, WMQ 5.3 CSD05 I have a clustered queue manager that is reporting bind errors. Specifically: AMQ9213: A communications error for bind occurred. In the error log, I am getting bind error 13. Along with the error log reports, I am getting generated FDC files: +-+ | | | WebSphere MQ First Failure Symptom Report | | = | | | | Date/Time :- Tuesday January 20 20:42:09 PST 2004 | | Host Name :- vdpsusptas02 (SunOS 5.8) | | PIDS :- 5724B4103 | | LVLS :- 530.5 CSD05 | | Product Long Name :- WebSphere MQ for Sun Solaris | | Vendor:- IBM | | Probe Id :- RM07 | | Application Name :- MQM | | Component :- cccJobMonitor | | Build Date:- Sep 27 2003 | | CMVC level:- p530-05-L030926 | | Build Type:- IKAP - (Production) | | UserID:- 1002 (jlee) | | Program Name :- runmqlsr_nd | | Process :- 1437 | | Thread:- 0003 | | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR | | Minor Errorcode :- OK | | Probe Type:- MSGAMQ9213 | | Probe Severity:- 2 | | Probe Description :- AMQ9213: A communications error for bind occurred. | | FDCSequenceNumber :- 0 | | Arith1:- 13 d | | Arith2:- 13 d | | Comment1 :- | | | | Comment2 :- bind | | | | Comment3 :- (/tmp/MQSeries.1437) | | | | | +-+ . . . Consequently, all the other cluster queue managers that are trying to communicate to this manager are failing (the cluster sender channel on these remote queue managers go to a BINDING or RETRYING state). I don't see anything also binding to the port (1414). The listener (not using inetd) process starts fine (it terminates if it can't bind to the specified port, right?). I have tried stopping/restarting. Even tried rebuilding and refreshing cluster info. ... to no avail. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Find high-speed net deals comparison-shop your local providers here. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: AMQ9213 & Bind failures on Solaris
There's something broken along your comm path to the cluster, e.g. router, firewall, etc. Get your comm person to check it out. I typically get this sort of problem when my VPN tunnel between two queue managers goes south. Antony Boggis <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: cc: MQSeries ListSubject: AMQ9213 & Bind failures on Solaris <[EMAIL PROTECTED] en.AC.AT> 01/21/2004 12:52 AM Please respond to MQSeries List Env: Solaris 5.8, WMQ 5.3 CSD05 I have a clustered queue manager that is reporting bind errors. Specifically: AMQ9213: A communications error for bind occurred. In the error log, I am getting bind error 13. Along with the error log reports, I am getting generated FDC files: +-+ | | | WebSphere MQ First Failure Symptom Report | | = | | | | Date/Time :- Tuesday January 20 20:42:09 PST 2004 | | Host Name :- vdpsusptas02 (SunOS 5.8) | | PIDS :- 5724B4103 | | LVLS :- 530.5 CSD05 | | Product Long Name :- WebSphere MQ for Sun Solaris | | Vendor:- IBM | | Probe Id :- RM07 | | Application Name :- MQM | | Component :- cccJobMonitor | | Build Date:- Sep 27 2003 | | CMVC level:- p530-05-L030926 | | Build Type:- IKAP - (Production) | | UserID:- 1002 (jlee) | | Program Name :- runmqlsr_nd | | Process :- 1437 | | Thread:- 0003 | | Major Errorcode :- rrcE_COMMUNICATIONS_ERROR | | Minor Errorcode :- OK | | Probe Type:- MSGAMQ9213 | | Probe Severity:- 2 | | Probe Description :- AMQ9213: A communications error for bind occurred. | | FDCSequenceNumber :- 0 | | Arith1:- 13 d | | Arith2:- 13 d | | Comment1 :- | | | | Comment2 :- bind | | | | Comment3 :- (/tmp/MQSeries.1437) | | | | | +-+ . . . Consequently, all the other cluster queue managers that are trying to communicate to this manager are failing (the cluster sender channel on these remote queue managers go to a BINDING or RETRYING state). I don't see anything also binding to the port (1414). The listener (not using inetd) process starts fine (it terminates if it can't bind to the specified port, right?). I have tried stopping/restarting. Even tried rebuilding and refreshing cluster info. ... to no avail. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
