You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Dan Feidt <Ho...@yahoo.com> on 2000/06/24 00:26:00 UTC

config/6224: Could not bind to port 204 on startup

>Number:         6224
>Category:       config
>Synopsis:       Could not bind to port 204 on startup
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Jun 23 15:30:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     HongPong2000@yahoo.com
>Release:        Apache/1.3.12 (Unix)
>Organization:
apache
>Environment:
Linux 2.2.9 #5 Thu May 20 11:17:07 CDT 1999 i586 unknown
Server version: Apache/1.3.12 (Unix)
Server built:   Jun 23 2000 16:13:17
>Description:
When I try to start up, the errorlog says the following:
[Fri Jun 23 16:36:02 2000] [crit] (98)Address already in use: make_sock: could not bind to port 204
[Fri Jun 23 16:39:30 2000] [info] created shared memory segment #384
[Fri Jun 23 16:39:30 2000] [notice] Apache/1.3.12 (Unix) configured -- resuming normal operations
[Fri Jun 23 16:39:30 2000] [info] Server built: Jun 23 2000 16:13:17

ps ax gives this:
  PID TTY STAT  TIME COMMAND
    1  ?  S    0:04 init [3]
    2  ?  SW   0:01 (kflushd)
    3  ?  SW   0:00 (kpiod)
    4  ?  SW   0:01 (kswapd)
   10  ?  S    0:02 /sbin/update
   11  ?  S    0:00 /sbin/kerneld
   51  ?  S    0:02 /usr/sbin/syslogd
   52  ?  SW   0:00 (klogd)
   56  ?  S    0:00 /usr/sbin/inetd
   58  ?  S    0:00 /usr/sbin/rpc.mountd
   60  ?  S    0:00 /usr/sbin/rpc.nfsd
   62  ?  S    0:00 /usr/sbin/crond -l10
   68  ?  SW   0:00 (miniserv.pl)
   72  ?  SW   1:03 (gpm)
   74   1 SW   0:00 (agetty)
   75   2 SW   0:00 (agetty)
   76   3 SW   0:00 (agetty)
   77   4 SW   0:00 (agetty)
   78   5 SW   0:00 (agetty)
   79   6 SW   0:00 (agetty)
   80   8 SW   0:00 (agetty)
   81   9 SW   0:00 (agetty)
 9447  ?  S    0:00 in.telnetd
 9448  p0 S    0:00 -bash
11074  ?  S    0:01 in.telnetd
11075  p2 S    0:00 -bash
13845  p0 S    0:00 tail -f error_log
13949  p2 R    0:00 ps ax
   54  ?  SW   0:00 (rpc.portmap)

I'm at a loss as to why apache wants to use port 204, it is 80 in the config file. In any case, when it runs, the client (netscape mac) tells me the network connection was refused and so on. Unfortunately I'm terribly new at this, and self-teaching. There were 2 older versions of Apache, and they got mixed up, so I had to build a new one. I feel like a process I don't recognize is the problem, maybe.
>How-To-Repeat:
It seems unique to this server
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]