Re: [gentoo-user] Dead apache (cannot listen)

[Kevin O'Gorman]

Thanks for top-posting  :o)

This is still a bit mysterious for me.  I've tried to do what you said, but
apache still fails to start because it cannot
open a listening port.  Here's what I've figured out about what I have:
/etc/conf.c/apache2 contains
    APACHE2_OPTS="-D DEFAULT_VHOST -D INFO -D LANGUAGE -D MANUAL -D SSL -D
SSL_DEFAULT_VHOST -D USERDIR"
to which I contributed only USERDIR -- the other stuff came with the
ebuild.  Maybe I should drop the SSL stuff since my server has
no https stuff (It does have htaccess and htpasswd stuff, but I think that's
different).  In any event, removing the SSL stuff does not change
the problem.

Everything else in that file is commented out, which I take to mean that
default values are used.  Among the defaults is
#CONFIGFILE=/etc/apache2/httpd.conf
and that file contains
   Include /etc/apache2/vhosts.d/*.conf
      And /etc/apache2/vhosts.d/  includes
         00_default_ssl_vhost.conf    and   00_default_vhost.conf

My 00_default_vhost.conf:
=============== start 00_default_vhost.conf ==========================
# If your host doesn't have a registered DNS name, enter its IP address
here.
#
#ServerName www.example.com:80
ServerName www.kosmanor.com:80

#KOSMANOR changes
#Listen 80
Listen 64.166.164.49:80
Listen localhost:80

# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
# If you change this to something that isn't under /var/www then suexec
# will no longer work.
DocumentRoot "/var/www/localhost/htdocs"

# This should be changed to whatever you set DocumentRoot to.
<Directory "/var/www/localhost/htdocs">
        # Possible values for the Options directive are "None", "All",
        # or any combination of:
        #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI
MultiViews
        #
        # Note that "MultiViews" must be named *explicitly* --- "Options
All"
        # doesn't give it to you.
        #
        # The Options directive is both complicated and important.  Please
see
        # http://httpd.apache.org/docs/2.2/mod/core.html#options
        # for more information.
        Options Indexes FollowSymLinks

        # AllowOverride controls what directives may be placed in .htaccess
files.
        # It can be "All", "None", or any combination of the keywords:
        #   Options FileInfo AuthConfig Limit
        AllowOverride All

        # Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
</Directory>

<IfModule alias_module>
        # Redirect: Allows you to tell clients about documents that used to
        # exist in your server's namespace, but do not anymore. The client
        # will make a new request for the document at its new location.
        # Example:
        #   Redirect permanent /foo http://www.example.com/bar

        # Alias: Maps web paths into filesystem paths and is used to
        # access content that does not live under the DocumentRoot.
        # Example:
        #   Alias /webpath /full/filesystem/path
        #
        # If you include a trailing / on /webpath then the server will
        # require it to be present in the URL.  You will also likely
        # need to provide a <Directory> section to allow access to
        # the filesystem path.

        # ScriptAlias: This controls which directories contain server
scripts.
        # ScriptAliases are essentially the same as Aliases, except that
        # documents in the target directory are treated as applications and
        # run by the server when requested rather than as documents sent to
the
        # client.  The same rules about trailing "/" apply to ScriptAlias
        # directives as to Alias.
        ScriptAlias /cgi-bin/ "/var/www/localhost/cgi-bin/"
</IfModule>

# "/var/www/localhost/cgi-bin" should be changed to whatever your
ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/var/www/localhost/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
</Directory>

# vim: ts=4 filetype=apache
=============== end 00_default_vhost.conf ==========================


On 9/6/07, Alexander Reitzel <loel@×××.de> wrote:
>
> you should look at your vhost configs. take an example of the current
> default_vhost config and make sure to keep the -D DEFAULT_VHOST
> in /etc/conf.d/apache2
> Ive had the same problem with one of my servers and after using the
> default
> thiggie it worked fine.
>
> Am Freitag, 7. September 2007 03:08:43 schrieb Kevin O'Gorman:
> > Somewhere in the update to 2.2.4-r12, listening got lost.  I tried to
> > follow instructions,
> > but apparently failed.
> >
> > Here's what happens (minus a MaxClients warning that doesn't look like a
> > show-stopper):
> >
> > treat init.d # ./apache2 start
> >  * 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
> > [ !! ]
> > treat init.d #
> >
> > So it got my instructions to listen, but failed.
> >
> > Looking at 'netstat --inet -l' does not show any listeners or open
> sockets
> > on port 80.
> >
> > What else should I look at?
>
>
> --
> gentoo-user@g.o mailing list
>
>


-- 
Kevin O'Gorman, PhD