Received: (qmail 27852 invoked by uid 2012); 1 Sep 1998 15:28:07 -0000
Message-Id: <19980901152807.27851.qmail@hyperreal.org>
Date: 1 Sep 1998 15:28:07 -0000
From: Phil E Dietz <pedietz@west.com>
Reply-To: pedietz@west.com
To: apbugs@hyperreal.org
Subject: Address already in use errors
X-Send-Pr-Version: 3.2

>Number:         2937
>Category:       os-aix
>Synopsis:       Address already in use errors
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Sep  1 08:30:00 PDT 1998
>Closed-Date:    Mon Dec 03 05:43:41 PST 2001
>Last-Modified:  Mon Dec 03 05:43:41 PST 2001
>Originator:     pedietz@west.com
>Release:        1.3.1
>Organization:
>Environment:
AIX 4.2.1 
(guessOS  003000014C00-ibm-aix4.2)
>Description:
Receiving "67)Address already in use: make_sock: could not bind to port 80"
errors on AIX4.2.1 box.

I have hard restarted it like the docs say but they still show up every 60 secs.

(side note, in order to compile on AIX4.2 I had to modify os.c and add #if (AIX < 42) like a previous PR mentions.  The previous PR used (AIX < 43) but indeed it's 42.
>How-To-Repeat:
NA
>Fix:
Add a troubleshooting page to your docs.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-feedback
State-Changed-By: coar
State-Changed-When: Sun Sep 27 11:42:29 PDT 1998
State-Changed-Why:

If you're getting an error message about port 80 already
being in use, then either that's the case or your operating
system is very ill.  Do you have multiple Listen or
VirtualHost directives referencing the same address and
port?  When you think the server is shut down, what does
"netstat -an | grep ':80'" show?

Severity-Changed-From-To: critical-serious
Severity-Changed-By: coar
Severity-Changed-When: Sun Sep 27 11:42:29 PDT 1998
Comment-Added-By: coar
Comment-Added-When: Tue Sep 29 03:37:26 PDT 1998
Comment-Added:
[Input from submitter, who did *not* Cc apbugs]
Ok I finally figured it out..I have apache set as 'respawn' in the inittab.

Every so often the inittab will try to kick off a new httpd and fail because
of the port failures.

So my question is:
        Can the apache server be set to 'respawn' in the inittab?
        If the parent process of apache never dies, I would assume it could.

Going through the Apache PR database, this may be related to PR 2662.
State-Changed-From-To: feedback-open
State-Changed-By: lars
State-Changed-When: Sat Nov 14 09:28:17 PST 1998
State-Changed-Why:
issue is still open...

Severity-Changed-From-To: serious-non-critical
Severity-Changed-By: lars
Severity-Changed-When: Sat Nov 14 09:28:17 PST 1998
State-Changed-From-To: open-closed
State-Changed-By: trawick
State-Changed-When: Mon Dec  3 05:43:41 PST 2001
State-Changed-Why:
much time has elapsed, many fixes have been put into Apache...  please upgrade to the latest level...  if the
problem persists, please open a new PR

Thanks!
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]