Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

INN FAQ Part 3/9: Reasons why INN isn't starting
Section - (3.3) syslog message: inndstart: inndstart cant bind Address already in use

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Cities ]


Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting
Previous Document: (3.2) Why does innd just exit right away with no message?
Next Document: (3.4) syslog message: ME internal no to group
See reader questions & answers on this topic! - Help others by sharing your knowledge
>I try to start INN but got this error in my syslog file:
>       inndstart: inndstart cant bind Address already in use
>Can anyone give me a hint on how to fix it ?

Something else is already using port 119.  Comment out the line in
/etc/inetd.conf for port 119 and "kill -HUP" the inetd program (which
makes it re-read the configuration file).

Remember, there are two ways for programs to take control over an
incoming port.  (1) the program runs and grabs the port (which has to
be done as root) and then handles all incoming connections, or (2) the
program is listed in /etc/inetd.conf and inetd grabs the port and hands
off any incoming connections to the program specified in
/etc/inetd.conf (i.e. one process gets started for every incoming
connection.)

If you do (1) and (2) at the same time, the inetd will grab the port
and then anyone else that grabs the port will get an "Address already
in use" error.

INN's "innd" program is type (1).  C News+NNTP uses something that is
type (2).

Most people that get this error ran C News+NNTP a long time ago and
forgot to remove the line from their /etc/inetd.conf file.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: INN FAQ Part 3/9: Reasons why INN isn't starting
Previous Document: (3.2) Why does innd just exit right away with no message?
Next Document: (3.4) syslog message: ME internal no to group

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)





Last Update November 21 2011 @ 01:00 PM