httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 45863] (98)Address already in use: make_sock: could not bind to address [::]:80
Date Thu, 08 Jan 2009 12:22:20 GMT

Istvan <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #19 from Istvan <>  2009-01-08 04:22:19 PST ---
(In reply to comment #18)
> On the Pidfile path is only specified on
> and that page is only
> linked from the bottom of through
> a small link titled "Listen", which is very hard to find online, so it's good
> to know it is specified in and extra directory configuration file also.
> Is there a reason why the pidfile error should only be logged and not displayed
> on console as the binding error is. It causes a fatal problem, for which users
> get no notification on the console, whereas even the smallest misconfigurations
> of httpd.conf result in console error messages.
> We are willing to write the necessary patch code for this, unless it is better
> for some reason, to have this error only logged and not on console.

Thanks John for the good intention to help, I was one of the unfortunate user
myself too, who just hit this bug on Fedora 10 with default httpd 2.2.10

The error message was exactly the same, but first I thought it's related to
IPv6 configuration which I disabled, but the issue remaind.
I'm afraid the PidFile solution I found on this page was no help either.
Eventually after some long hours spent on googling and tryring to fix the issue
myself, I found the solution to this issue.

I had to comment the

Include conf.d/*.conf

line in httpd.conf to be able to start the daemon. 

I don't know why it happened and why it fixed the issue, but now I have no PHP
configuration which is part of this conf.d directory and wanted to use the
server for PHP development.

If it's an ASF issue, or not, the users are suffering and those poor buggers on
the Fedora forums keep reinstalling their OS to try to fix this annoying issue.

Pity not this oraganization nor the OS distributor is willing to get this issue
fixed once and for all...

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message