FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80

This may be an Apache issue and if so I'll take my questions elsewhere
but I upgraded from FC7 to FC8 and now for some odd reason when I
restart apache I get this error:

"(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs"


But I can kill the running httpd and apache will start without a
problem...no warnings whatsoever. I never got this error prior to
upgrading.

I've changed absolutely nothing about my httpd.conf but during testing I
did note that the default httpd.conf installed doesn't cause the restart
error. I'm guessing that's because the default httpd.conf doesn't setup
virtualhosts, etc. but it might be significant. Apache's test shows no
errors in the .conf file. I don't have any files in the conf.d directory
so there are no conflicts there.


Any ideas?
.

Relevant Pages

  • Re: Ports after upgrade
    ... You should try to use portsnap instead of cvsup which is in the base since 6.2. ... Your problem looks like a portupgrade mistake. ... After upgrading portupgrade you should rebuild apache with something like that: ...
    (freebsd-questions)
  • Re: How to manually patch/configure/compile Apache 2.2.4s mod_autoindex module?
    ... Apache 2.2.4, which apart from some hassles when upgrading the PHP4 ... this user, I had allowed directory listings, with fancyindexing ... Overriding the Default Ports Directories ...
    (freebsd-questions)
  • How to manually patch/configure/compile Apache 2.2.4s mod_autoindex module?
    ... I used to use Apache 1.3.33 on my live server, and recently I upgraded to Apache 2.2.4, which apart from some hassles when upgrading the PHP4 extensions, went well. ... However, there is one small thingy that is different: there are exactly two directories on which I allow directory listings, and these listings are called from an external W*nd*ws program that one of the users of my machine has made and has distributed. ... In fact, it looks like the only place where this could be changed, is the mod_autoindex.c file, under the "work" directory in the proper "ports" directory. ...
    (freebsd-questions)
  • Apache2 crashing
    ... After upgrading to Apache 2.0.49 and PHP4.3.5_7, ... every time I do a graceful restart or if I send it a kill 1. ...
    (freebsd-questions)
  • Re: apache13 to 22
    ... So how I do procedure of upgrading it? ... >> There is no clear-cut upgrade procedure, but it's doable, I think, but on ... you really have to schedule a downtime and let your ... > I'm messing with apache on my home computer, ...
    (freebsd-questions)