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

Bug#392058: marked as done (apache2.2-common: apache fails to start)



Your message dated Wed, 11 Oct 2006 09:24:03 -0500
with message-id <20061011142403.GB1841@mauritius.dodds.net>
and subject line Bug#392058: apache2.2-common: apache fails to start
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: apache2.2-common
Version: 2.2.3-2
Severity: grave
Justification: renders package unusable


When starting apache get the following:

Starting web server (apache2)...apache2: Syntax error on line 185 of
/etc/apache2/apache2.conf: Syntax error on line 1 of
/etc/apache2/mods-enabled/php5.load: API module structure `php5_module'
in file /usr/lib/apache2/modules/libphp5.so is garbled - perhaps this is
not an Apache module DSO?
 failed!
  invoke-rc.d: initscript apache2, action "start" failed.

Line 185 is:
Include /etc/apache2/mods-enabled/*.load

and line 1 is:
LoadModule php5_module /usr/lib/apache2/modules/libphp5.so

When I comment these out it still fails:

  Starting web server (apache2)...Syntax error on line 141 of
  /etc/apache2/apache2.conf:
  Invalid command 'Order', perhaps misspelled or defined by a module not
  included in the server configuration
   failed!

This section of the file is:

<Files ~ "^\.ht">
    Order allow,deny
        Deny from all
</Files>

and then I comment and it fails:

   Starting web server (apache2)...Syntax error on line 142 of
   /etc/apache2/apache2.conf:
   Invalid command 'Deny', perhaps misspelled or defined by a module not
   included in the server configuration
    failed!

and then I gave up.

The first bug does look similar to bugs 391472 and 391864 which both state
2.2.3-2 fixes the issues. However I am definitely running this version
and it doesn't fix it..

ian@jandi3:~$ dpkg -l | grep apache
ii  apache2                          2.2.3-2
Next generation, scalable, extendable web se
rc  apache2-common                   2.0.55-4.2
next generation, scalable, extendable web se
ii  apache2-mpm-prefork              2.2.3-2
Traditional model for Apache HTTPD 2.1
ii  apache2-utils                    2.2.3-2
utility programs for webservers
ii  apache2.2-common                 2.2.3-2
Next generation, scalable, extendable web se
ii  libapache2-mod-php5              5.1.6-3
server-side, HTML-embedded scripting languag


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apache2.2-common depends on:
ii  apache2-utils                 2.2.3-2    utility programs for webservers
ii  libmagic1                     4.17-4     File type determination library us
ii  lsb-base                      3.1-17     Linux Standard Base 3.1 init scrip
ii  mime-support                  3.37-1     MIME files 'mime.types' & 'mailcap
ii  net-tools                     1.60-17    The NET-3 networking toolkit

apache2.2-common recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On Wed, Oct 11, 2006 at 07:57:55PM +1300, Ian McDonald wrote:
> >This is because you have installed the one version of libapache2-mod-php5
> >which apache2.2-common does not conflict with, that was uploaded against 
> >the
> >wrong ABI.  The conflict needs to be updated, but this is not
> >release-critical.

> libapache2-mod-php5 (5.1.6-4) got installed today in latest updates
> and my apache is now working.

> >I'm not sure what the root cause of this is, but it looks like mod_access
> >(or the apache2 equivalent?) is no longer being compiled into the binary as
> >it was in previous versions.  That might warrant an RC severity on its 
> >own..

> These went away as well now.

> This bug can be closed.

Ok, closing.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

--- End Message ---

Reply to: