[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

fresh apt-get install of apache2 fails -- what next?



I'm familiar with Debian but brand new to Apache.  So I'm not sure what to
do after seeing this:

    [~]# apt-get install apache2-mpm-prefork apache2-doc
    Reading Package Lists... Done
    Building Dependency Tree... Done
    The following extra packages will be installed:
      apache2-common libapr0
    The following NEW packages will be installed:
      apache2-common apache2-doc apache2-mpm-prefork libapr0
[...]
    Unpacking libapr0 (from .../libapr0_2.0.39+cvs.1027964860-1_i386.deb) ...
    Selecting previously deselected package apache2-common.
    Unpacking apache2-common (from .../apache2-common_2.0.39+cvs.1027964860-1_i386.deb) ...
    Selecting previously deselected package apache2-doc.
    Unpacking apache2-doc (from .../apache2-doc_2.0.39+cvs.1027964860-1_all.deb) ...
    Selecting previously deselected package apache2-mpm-prefork.
    Unpacking apache2-mpm-prefork (from .../apache2-mpm-prefork_2.0.39+cvs.1027964860-1_i386.deb) ...
    Setting up libapr0 (2.0.39+cvs.1027964860-1) ...

    Setting up apache2-common (2.0.39+cvs.1027964860-1) ...
    Setting Apache2 to Listen on port 80. If this is not desired, please edit /etc/apache2/ports.conf as desired. Note that the Port directive no longer works.

    Setting up apache2-doc (2.0.39+cvs.1027964860-1) ...
    Setting up apache2-mpm-prefork (2.0.39+cvs.1027964860-1) ...
    Processing config directory: /etc/apache2/mods-enabled
    Processing config directory: /etc/apache2/sites-enabled
     Processing config file: /etc/apache2/sites-enabled/default
    apache2: could not open document config file /etc/apache2/httpd.conf
    dpkg: error processing apache2-mpm-prefork (--configure):
     subprocess post-installation script returned error exit status 1
    Errors were encountered while processing:
     apache2-mpm-prefork
    E: Sub-process /usr/bin/dpkg returned an error code (1)


And sure enough, there is no file called /etc/apache2/httpd.conf.  I have
no idea where this file is supposed to come from.

Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                  - Edsger Djkstra, 1930-2002



Reply to: