Re: [gentoo-user] All of a sudden, no apache2. No clue why.

[Kevin O'Gorman]

> On Thu, 2010-07-29 at 14:24 -0700, Kevin O'Gorman wrote:
> > As of today, my apache2 web server seems to refuse to start.  I've
> > tried a system reboot, to no avail --
> > connections are refused on port 80.
> >
> > In /etc/init.d it looks like this: if I try to start it, it says it's
> > already started.  netstat says there's no listener
> > on port 80.  If I try to restart it, it cannot start a listener.  I'm
> > really bummed.
> >
> > Any ideas how to get this going again?
> >
> > Here's a short look at what I was doing in /etc/init.d
> >
> > treat init.d # ./apache2 start
> >  * WARNING:  apache2 has already been started.
> > treat init.d # ./apache2 restart
> >  * Stopping apache2 ...
> > httpd (no pid file) not running
> > [ ok ]
> >  * Starting apache2 ...
> > (98)Address already in use: make_sock: could not bind to address
> > 64.166.164.49:80
> > no listening sockets available, shutting down
> > Unable to open logs
> > [ ok ]
>
>
>
> On Thu, Jul 29, 2010 at 4:27 PM, William Kenworthy <billk@×××××××××.au>wrote:
There is an "Unable to open logs" in there ... are you doing some fancy
remote logging that cant start? - I cant see anything that says its
specifically port 80 thats causing the problem, just no listening
sockets available.

syslog is udp port 514, and then there is ssl on 443.

BillK

I'm doing nothing fancy, but I did have a nearly full root directory.  I
flushed out some
old portage stuff an I'm back to 19 GB free.  I still get the same result
messages during
a reboot.

It is true I modified the local apache config
/etc/apache2/kosmanor/hexDirs.conf slightly just before.  I added a /HexData
alias, like
a few others that I have.  I've attached the config file in case you can
find any unintended
change.

Looking at the logs, there does not seem to be logging going on since July
16, and things
were working then, I thought.  List of log directory follows.  I do seem to
have two different styles of log rotation going on simultaneously, but that
seems to have been the case for
quite a while now; I'll find that later.

treat apache2 # ls -l
total 4368
-rw-rw-rw- 1 root root      0 Jul 16 03:10 access_log
-rw-rw-rw- 1 root root 191438 Jun 15  2009 access_log.1.gz
-rw-rw-rw- 1 root root 678879 Jun 25 03:10 access_log-20100625.gz
-rw-rw-rw- 1 root root 693424 Jul  2 03:10 access_log-20100702.gz
-rw-rw-rw- 1 root root 701307 Jul  9 03:10 access_log-20100709.gz
-rw-rw-rw- 1 root root 840730 Jul 16 03:10 access_log-20100716.gz
-rw-rw-rw- 1 root root 234663 Jun  8  2009 access_log.2.gz
-rw-rw-rw- 1 root root 270349 Jun  1  2009 access_log.3.gz
-rw-rw-rw- 1 root root 277761 May 25  2009 access_log.4.gz
-rw-rw-rw- 1 root root      0 Jul 16 03:10 error_log
-rw-rw-rw- 1 root root 117611 Jun 15  2009 error_log.1.gz.out
-rw-rw-rw- 1 root root  61608 Jun 25 03:10 error_log-20100625.gz
-rw-rw-rw- 1 root root  69397 Jul  2 03:10 error_log-20100702.gz
-rw-rw-rw- 1 root root 118085 Jul  9 03:10 error_log-20100709.gz
-rw-rw-rw- 1 root root 114433 Jul 16 03:10 error_log-20100716.gz
-rw-rw-rw- 1 root root   5706 Jun  8  2009 error_log.2.gz
-rw-rw-rw- 1 root root   5628 Jun  1  2009 error_log.3.gz
-rw-rw-rw- 1 root root   6344 May 25  2009 error_log.4.gz
-rw-rw-rw- 1 root root      0 Feb  3  2008 ssl_access_log
-rw-rw-rw- 1 root root      0 Feb  3  2008 ssl_error_log
-rw-rw-rw- 1 root root      0 Feb  3  2008 ssl_request_log
treat apache2 # pwd
/var/log/apache2
treat apache2 #


The ownership may seem odd, but agrees with backups.  That July 16 log ends
with
something familiar:

[Fri Jul 16 03:10:07 2010] [notice] SIGUSR1 received.  Doing graceful
restart
(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
treat apache2 #

So I guess my page has been down for a while.  A nuisance at most because
it's just my
personal stuff, which a handful of people care about.  But I want it back
up, not to mention the logging.



-- 
Kevin O'Gorman, PhD