On Tue, Mar 06, 2007 at 11:03:34PM +0000, eoghan wrote: > On 3/6/07, Mike Galvez <[EMAIL PROTECTED]> wrote: > > >> >> > > -----Original Message----- > >> >> > > From: [EMAIL PROTECTED] > >> >> > > [mailto:[EMAIL PROTECTED] On Behalf Of eoghan > >> >> > > Sent: Tuesday, March 06, 2007 5:50 AM > >> >> > > To: freebsd > >> >> > > Subject: apache problem > >> >> > > > >> >> > > Hi > >> >> > > I am running apache 2.2.4 on FreeBSD 6.1. This is a recent > >> >> > > upgrade from ports (in the past few days or so). Since then I > >> >> > > cant browse to localhost. Just get an unable to connect > >> >> > > message. The server seems to start with: > >> >> > > $sudo apachectl start > >> >> > > If I try it again I see its already running. > >> >> > > My error log shows: > >> >> > > [Mon Mar 05 11:20:00 2007] [notice] Apache/2.2.4 (FreeBSD) > >> >> > > mod_ssl/2.2.4 OpenSSL/0.9.7e-p1 DAV/2 PHP/5.2.1 with Suhosin-Patch > >> >> > > configured -- resuming normal operations > >> >> > > [Mon Mar 05 11:20:22 2007] [notice] caught SIGTERM, shutting down > >> >> > > > >> >> > > I have tried the apache list but no real answers, and apache > >> >> > > was working fine for me before I upgraded. Has anyone else > >> >> > > noticed this since an upgrade to the 2.2.4 version from ports? > >> >> > > > >> >> > > Thanks > >> >> > > Eoghan > >> >> > > >> >> > I had the same problem. Here is how I fixed it: > >> >> > #apachectl stop > >> >> > # cd /usr/ports/www/apache22 > >> >> > #make clean > >> >> > # make deinstall > >> >> > # rm ./* > >> >> > Then do a cvsup ports all > >> >> > now once more > >> >> > #cd /usr/ports/www/apache22 > >> >> > # make (it will use your stored config) > >> >> > #make install > >> >> > #make clean > >> >> > #apachectl start > >> >> > >> >> Hi > >> >> Gret, thanks for that, I will give this a go. > >> >> Regards > >> >> Eoghan > >> >> > >> >all the best > >> >please let me know if it works 4U > >> >-- I have made a posting on [EMAIL PROTECTED] -- so the maintainer knows > >> >aboutthe problem. If this also works for you it should not be too > >> >difficult for someone to fix the port. > >> >David > >> > >> Hi > >> I have tried this and i still cant get it working. Also tried syntax > >> check and its checks out OK, as someone else suggested to do... any > >> further suggestions? > >> Thanks > >> Eoghan > >> _______________________________________________ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to > >"[EMAIL PROTECTED]" > >Hi, > > > >I was rebuilding one of my servers yesterday. I was having trouble getting > >ldap > >support to build, but I was also seeing the same issue you describe. The > >configtest reported no errors and Apache appeared to start and I could see > >it in > >the process list, but could not contact the server. Out of frustration i > >bounced > >the box and when it came back up Apache started as expected (minus ldap of > >course). > > > > > >-- > >Michael Galvez http://www.people.virginia.edu/~mrg8n > >Information Technology Specialist University of Virginia > > Hi > By bounced the box, do you mean restarted it? > Thanks > Eoghan
Yes. Restart the OS. Even though I had killed all http processes, Apache 2.2.4 server would not restart correctly without restarting the OS. -Mike > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Michael Galvez http://www.people.virginia.edu/~mrg8n Information Technology Specialist University of Virginia _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"