On Friday 12 March 2004 12:55 pm, Mark wrote:
> ----- Original Message -----
> From: "Kent Stewart" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: "Mark" <[EMAIL PROTECTED]>
> Sent: Friday, March 12, 2004 9:42 PM
> Subject: Re: "bind: Address already in use" on Apache 1.3.29
> > On Friday 12 March 2004 12:26 pm, Mark wrote:
> > > Hello,
> > >
> > > I upgraded my Apache server to 1.3.29, on FreeBSD 4.9R-p3. Now,
> > > all of sudden, it will not bind anymore, for no apparent reason:
> > >
> > > [Fri Mar 12 21:12:12 2004] [notice] Apache/1.3.29 (Unix)
> > > mod_perl/1.28 PHP/4.3.4 mod_ssl/2.8.16 OpenSSL/0.9.7c configured
> > > -- resuming normal operations [Fri Mar 12 21:12:12 2004] [notice]
> > > Accept mutex: flock (Default: flock) bind: Address already in use
> > >
> > > No address is in use, I can assure you. This is quite absurd; I
> > > use the same config as the.28 version. The daemon will not
> > > prefork, either.
> > >
> > > Anyone has similar experience? Or an idea to solve it?
> > Did you stop the oldversion of Apache before you tried to start the
> > new one?
> Of course. A billion times, even. Plus, I unloaded all but every
> module and restarted again, and again, and again. I even went so far
> as to remove all Listen commands. Still the same! Something is fishy.
I would stop Apache and see if you have any httpd's left running. That
is about the only thing I can think of that would prevent the new one
from binding. If you do, I would try a "killall httpd".
I had that happen once and it was because something from the old version
was still running. Apache is the only port that I don't use portupgrade
to do the update. I build, stop apache, make deinstall, install it, and
I have been known to do a shutdown now to drop into single user mode but
I never had to do it because of apache.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"