Date: Fri, 12 Mar 2004 13:21:16 -0800 From: Kent Stewart <kstewart@owt.com> To: Mark <admin@asarian-host.net> Cc: freebsd-questions@freebsd.org Subject: Re: "bind: Address already in use" on Apache 1.3.29 Message-ID: <200403121321.16131.kstewart@owt.com> In-Reply-To: <200403122055.I2CKTSCD094107@asarian-host.net> References: <200403122026.I2CKQ1P5092986@asarian-host.net> <200403121242.17022.kstewart@owt.com> <200403122055.I2CKTSCD094107@asarian-host.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 12 March 2004 12:55 pm, Mark wrote: > ----- Original Message ----- > From: "Kent Stewart" <kstewart@owt.com> > To: <freebsd-questions@freebsd.org> > Cc: "Mark" <admin@asarian-host.net> > 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 restart it. 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. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403121321.16131.kstewart>