| Author |
Message
|
| sumit.jr |
 Posted: Mon Jun 04, 2007 6:05 am Post subject: Problem starting Listener |
 |
|
Newbie
Joined: 04 Jun 2007
Posts: 3
|
Hi
I am attempting to start Listener on my queue manager running on AIX and I get this message. Could anyone please guide me on what the problem could be ?
AMQ9218: The TCP/IP listener program could not bind to port number 1414.
The return code from the 'bind' call for port 1414 was 67. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 04, 2007 6:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Mr Google say TCP code 67 is "Link has been severed".
What does netstat say (if anything) about that port, specifically what else is using it? What does the box administrator say about any firewall or other network software that's running?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Mon Jun 04, 2007 6:10 am Post subject: Re: Problem starting Listener |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Maybe another process (another listener) is listening on this port ?
Try telnet on this port.
_________________
Marcin |
|
| Back to top |
|
|
| sumit.jr |
| Posted: Mon Jun 04, 2007 7:41 am Post subject: Re: Problem starting Listener |
|
|
Newbie
Joined: 04 Jun 2007
Posts: 3
|
This is how I tried netstat
netstat -Aan |grep 1415
But it only gives me PCB/ADDR
PCB/ADDR Proto Recv-Q Send-Q Local Address Foreign Address (state)
f10000f0002e2b58 tcp4 0 0 *.1415 *.* LISTEN
f10000f000471b58 tcp4 0 0 10.1.222.60.1415 10.1.111.67.1147 ESTABLISHED
f10000f00022fb58 tcp4 0 0 10.1.222.60.1415 10.1.111.60.43101 ESTABLISHED
Is there a way I can find out the processes these relate to ?
Although I tried lsof -i:<Port No>
which I was not aware was installed and it did give me the processes which were using the port.
Thanks a ton for your help.
Cheers,
Sumit |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 04, 2007 7:46 am Post subject: Re: Problem starting Listener |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sumit.jr wrote: |
netstat -Aan |grep 1415
|
| sumit.jr wrote: |
| AMQ9218: The TCP/IP listener program could not bind to port number 1414. |
What's wrong with this picture....? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sumit.jr |
| Posted: Mon Jun 04, 2007 8:38 am Post subject: |
|
|
Newbie
Joined: 04 Jun 2007
Posts: 3
|
| just a typo nothing else .... |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Jun 04, 2007 6:50 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| sumit.jr wrote: |
| just a typo nothing else .... |
OK...so what does the GREP output from 1414 say? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Jun 04, 2007 10:20 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Perhaps there is an entry for 1414 in /etc/services & /etc/inetd.conf. If so, the port is already bound by inetd and runmqlsr will not be able to bind to the same port. Remove the entries and restart inetd (or send it a SIGHUP) so that it re-reads the config files.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Jun 05, 2007 6:51 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Actually you should be able to do a:
# refresh -s inetd
once you have edited the inetd.conf file.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jun 05, 2007 10:18 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| csmith28 wrote: |
Actually you should be able to do a:
# refresh -s inetd
once you have edited the inetd.conf file. |
Works on AIX only |
|
| Back to top |
|
|
|
|
