Apache2 Fails to install/start

[Eric Peters]

Binary package hint: apache2

Setting up apache2-mpm-prefork (2.2.3-3.2build1) ...
 * 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
   ...fail!
invoke-rc.d: initscript apache2, action "start" failed.

Setting up apache2 (2.2.3-3.2build1) ...
Setting up php5-common (5.2.1-0ubuntu1) ...
Setting up libapache2-mod-php5 (5.2.1-0ubuntu1) ...

Creating config file /etc/php5/apache2/php.ini with new version
Your apache2 configuration is broken, so we're not restarting it for you.

Setting up php5 (5.2.1-0ubuntu1) ...

More info here http://<email address hidden>/msg08152.html

[Tim Webster (tdwebste)]

I have the same problem:

Error:
apache2ctl -t
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

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

Bug Reference:
http://www.mail-archive.com/debian-apache%40lists.debian.org/msg08152.html
Did this bug get closed properly in Ubuntu?

Other Info:
==========================================
apache2ctl -l
Compiled in modules:
  core.c
  mod_log_config.c
  mod_logio.c
  worker.c
  http_core.c
  mod_so.c

apache2ctl -V
Server version: Apache/2.2.3
Server built: Jan 15 2007 18:11:52
Server's Module Magic Number: 20051115:3
Server loaded: APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture: 32-bit
Server MPM: Worker
  threaded: yes (fixed thread count)
    forked: yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/worker"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT=""
 -D SUEXEC_BIN="/usr/lib/apache2/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache2.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types"
 -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf"

-- System Information:
Debian Release: 4.0
  APT prefers feisty-updates
  APT policy: (500, 'feisty-updates'), (500, 'feisty-security'), (500, 'feisty-proposed'), (500, 'feisty-backports'), (500, 'feisty'), (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-proposed'), (500, 'edgy-backports'), (500, 'edgy')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.20-15-generic
Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=UTF-8)

Versions of packages apache2 depends on:
ii apache2-mpm-worker 2.2.3-3.2build1 High speed threaded model for Apac

[Tim Webster (tdwebste)]

Bug Fixers,

Still waiting for this fix in feisty!
I am looking the following.
1) An estimate how long it will be until someone has the time to look at this and move the fix from debian into ubuntu.

If I don't get a response by the end of May, This will be the last time I install ubuntu on a server. The fact that ubuntu requires editing the source.list every time there is a release is currently a big problem for deploying ubuntu on servers. Not keeping with debian bug fixes, will kill my interest in ubuntu for server applications.
Please use repository aliases, so we can track the legacy or previous_stable release of ubuntu for servers and let the desktop users track stable or testing, while developers play in unstable or experimental.
By the time code hits our servers, we expect it to be tested and verified. Like wise we have very little interest in tracking latest kernel. Would much rather track the previous kernel with bug fixes.

tic, toc, my patients is running out.

[Caspar Clemens Mierau (leitmedium)]

Thanks for your bug report. I cannot prove this bug report with the same package. Can you please check if this bug still persists and provide us with your steps to you your apache installation and the important apache configuration files like apache2.conf?

Thank you in advance

[Tim Webster (tdwebste)]

Thanks for getting back to me.

Currently I am using 2.0.55-4ubuntu4 which is fine. The apache version
that comes with festy 2.2.3-3.2build1 is broken for me. Are you
interested in a bug report for this version.

This is on a production server, so I am reluctant to upgrade this
computer to gutsy at this early stage of its development. However if
you wish a bug report with 2.2.3-5, I will setup another computer to
test. Are you interested in ubuntu or debian? I am not familar with
apache2, svn, python packages deferences between the two.

Please let me know what apache2 package versions you are interested me
sending a bug report for. I would rather not take time putting
together a bug report for an old package version if support for it has
been obsoleted.

regards
Tim

On 6/27/07, Caspar Clemens Mierau <email address hidden> wrote:
> Thanks for your bug report. I cannot prove this bug report with the same
> package. Can you please check if this bug still persists and provide us
> with your steps to you your apache installation and the important apache
> configuration files like apache2.conf?
>
> Thank you in advance
>
> ** Bug watch added: Debian Bug tracker #396678
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396678
>
> ** Also affects: apache2 (upstream) via
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396678
> Importance: Unknown
> Status: Unknown
>
> ** Changed in: apache2 (Ubuntu)
> Status: New => Incomplete
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Mathias Gug (mathiaz)]

If you could test it with the latest version from gutsy (2.2.3-5) from ubuntu, it would be great. But don't do it on your production server. If you can test it on a test server, that would help us to check if the latest version in gutsy fixes your problem.

Tanks for your help.

[Tim Webster (tdwebste)]

BUG has NOT been fixed by apache Version: 2.2.3-5

The problem is perhaps the apache upgrade from 2.0 to 2.2

Starting from apache2 2.0.55-4ubuntu4
upgrade apache2, libapache2-svn, libapache2-mod-python to gutsy by

aptitude install apache2 libapache2-mod-python libapache2-svn
There are no install errors, except that apache2 will not restart

* Restarting 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

 apache2ctl -t
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

Thanks for you help,
Tim

On 6/27/07, Caspar Clemens Mierau <email address hidden> wrote:
> Thanks for your bug report. I cannot prove this bug report with the same
> package. Can you please check if this bug still persists and provide us
> with your steps to you your apache installation and the important apache
> configuration files like apache2.conf?
>
> Thank you in advance
>
> ** Bug watch added: Debian Bug tracker #396678
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396678
>
> ** Also affects: apache2 (upstream) via
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396678
> Importance: Unknown
> Status: Unknown
>
> ** Changed in: apache2 (Ubuntu)
> Status: New => Incomplete
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Caspar Clemens Mierau (leitmedium)]

Thanks for your comment. Can you please attach your apache2.conf and a "ls -al" of "mods-enabled" and mods-available? Thank you.

[Tim Webster (tdwebste)]

I appreciated your help with this. I know I could solve this myself,
but that is not the point. Long term support means moving from release
to release, or continuously upgrading without reinstalling.

On 7/1/07, Caspar Clemens Mierau <email address hidden> wrote:
> Thanks for your comment. Can you please attach your apache2.conf and a
> "ls -al" of "mods-enabled" and mods-available? Thank you.
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Soren Hansen (soren)]

The trouble is that the Order directive moved during the Apache 2.2 development cycle. It used to live in mod_access, but now lives in mod_authz_host. This is handled in Debian and hence Ubuntu by automatically adding these modules when doing a fresh install or when upgrading from anything below 2.2.3-3.1.
I've tested upgrades from 2.0 (Apache2 in Edgy) to 2.2 (Apache2 in Feisty) and all works well. Did the upgrade perhaps fail for you the first time in some way?

[Tim Webster (tdwebste)]

I am currently away on a business trip. I will verify this when I
return. And I will also take a look at the package install scripts.
The first apache upgrade from (2.0) to (2.2) failed just like the
rest. Chuckle if the first updated didn't fail I wouldn't have a
problem now, smile. I look into this more when I get back.

On 7/13/07, Soren Hansen <email address hidden> wrote:
> The trouble is that the Order directive moved during the Apache 2.2 development cycle. It used to live in mod_access, but now lives in mod_authz_host. This is handled in Debian and hence Ubuntu by automatically adding these modules when doing a fresh install or when upgrading from anything below 2.2.3-3.1.
> I've tested upgrades from 2.0 (Apache2 in Edgy) to 2.2 (Apache2 in Feisty) and all works well. Did the upgrade perhaps fail for you the first time in some way?
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tim Webster (tdwebste)]

hmm, I have apache-common (1.3) installed as well. I should have
removed that a long time ago. dpkg, apt wasn't complaining so I never
though to check. Since apache-common (1.3) contains mod_access,
perhaps that was the problem. I will check when I get back.

On 7/13/07, Soren Hansen <email address hidden> wrote:
> The trouble is that the Order directive moved during the Apache 2.2 development cycle. It used to live in mod_access, but now lives in mod_authz_host. This is handled in Debian and hence Ubuntu by automatically adding these modules when doing a fresh install or when upgrading from anything below 2.2.3-3.1.
> I've tested upgrades from 2.0 (Apache2 in Edgy) to 2.2 (Apache2 in Feisty) and all works well. Did the upgrade perhaps fail for you the first time in some way?
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tim Webster (tdwebste)]

The problem still exist. Cannot upgrade apache2 in Edgy to apache2 in
Feisty or Gutsy.

The hardware this server is running on is due to be upgraded in Sept.
I have decided to run debian on our servers and ubuntu on our
desktops. The apache2 upgrade problem is not to sole reason for this
decision. The primary reason is debian's use of release aliases, ie
"stable, testing, unstable, experimental".

If you want to see how the upgrade failed please refer to my previous
attached log file.

Tim

On 7/13/07, Soren Hansen <email address hidden> wrote:
> The trouble is that the Order directive moved during the Apache 2.2 development cycle. It used to live in mod_access, but now lives in mod_authz_host. This is handled in Debian and hence Ubuntu by automatically adding these modules when doing a fresh install or when upgrading from anything below 2.2.3-3.1.
> I've tested upgrades from 2.0 (Apache2 in Edgy) to 2.2 (Apache2 in Feisty) and all works well. Did the upgrade perhaps fail for you the first time in some way?
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Dan Butler (dbutler1986)]

This is a rather easy fix - I don't know if it could be done as a post-install script or something? Anyway, I fixed it with the following:

$ cd /etc/apache2/mods-enabled
$ for f in `ls ../mods-available` do
> sudo ln -s ../mods-available/$f $f
>done
$ sudo apache2 -k start

This is because even with authz_host loaded, there are more 'bugs' in the conf file caused by other modules that are not loaded by default in this version of the apache2 package for feisty. I didn't want to go through them all so I just enabled every module. You might prefer to go through them one by one until it stops panicking.

[Soren Hansen (soren)]

On Mon, Jul 30, 2007 at 01:41:14PM -0000, Tim Webster wrote:
> The problem still exist. Cannot upgrade apache2 in Edgy to apache2 in
> Feisty or Gutsy.

I need a bit more info about the current state of apache2 on your system
to figure this one out. There is code in place that should handle this.
If this code is not triggered, this needs to be fixed. Could you give me
the output of:

dpkg -l 'apache2*'

> The hardware this server is running on is due to be upgraded in Sept.
> I have decided to run debian on our servers and ubuntu on our
> desktops. The apache2 upgrade problem is not to sole reason for this
> decision. The primary reason is debian's use of release aliases, ie
> "stable, testing, unstable, experimental".

I'm curious why that matters so much? Do you primarily use stable and
then pull in new packages from testing or unstable as needed or do you
have a class of systems running only stable, a class of systems running
only testing..

--
Soren Hansen
Ubuntu Server Team
http://www.ubuntu.com/

[Tim Webster (tdwebste)]

I have ignored your request for dpkg -l ...... the problem is the upgrade scripts. If this is too difficult to script, then it needs to be in the change list and package readme files/kept in doc.

The problem was that as part of the upgrade from apache2 to apache2.2 the required modules where not made available in mods-enabled. This caused the syntax error.

I added the following to fixed this. Actually my complete set up required a few more. To determine all the modules required. The files in sites-enabled need to be parsed.

lrwxrwxrwx 1 root root 28 2006-12-22 08:05 alias.load -> ../mods-available/alias.load
lrwxrwxrwx 1 root root 33 2006-12-22 08:05 auth_basic.load -> ../mods-available/auth_basic.load
lrwxrwxrwx 1 root root 33 2006-12-22 08:05 authn_file.load -> ../mods-available/authn_file.load
lrwxrwxrwx 1 root root 36 2006-12-22 08:05 authz_default.load -> ../mods-available/authz_default.load
lrwxrwxrwx 1 root root 38 2006-12-22 08:05 authz_groupfile.load -> ../mods-available/authz_groupfile.load
lrwxrwxrwx 1 root root 33 2006-12-22 08:05 authz_host.load -> ../mods-available/authz_host.load
lrwxrwxrwx 1 root root 33 2006-12-22 08:05 authz_user.load -> ../mods-available/authz_user.load
lrwxrwxrwx 1 root root 32 2006-12-22 08:05 autoindex.load -> ../mods-available/autoindex.load
lrwxrwxrwx 1 root root 26 2006-12-22 08:05 env.load -> ../mods-available/env.load
lrwxrwxrwx 1 root root 27 2006-12-22 08:05 mime.load -> ../mods-available/mime.load

Next I had to let apache2 know were to find the mime.types
add to apache2.conf
TypesConfig /etc/mime.types

-----------------------------

unrelated but a bugs encounted upgrading from trac 10.3 to 10.4
trac 10.4 uses sqlite3

solution:
aptitude install sqlite sqlite3
mv trac.db trac.db.bak
sqlite trac.db.bak .dump | sqlite3 trac.db

trac-admin /project upgrade

I found the TagsWikiModule incompatible so I disabled it. I will look into re-enabling it another day.
comment this module out of trac.ini
#default_handler = TagsWikiModule
#trac.wiki.web_ui.wikimodule = disabled
#tractags.* = enabled

-------------
You are curious why I prefer debian's use of release aliases, ie "stable, testing, unstable, experimental" and why they are important. Many Linux users are often testers and developers when required. The use of release aliases breaks down the upgrade process so that packages are upgraded. This is essentially what happens as packages move from unstable to testing. There is a large number of testing users. And we used testing for our desktops and laptops. Failed package upgrades due to missed config migration is not crucial as these computer are not customized. However our servers are different story. Our servers use stable as much as possible, with testing servers using testing. The upgrade issues discovered by the testing machines is recorded and reported. The debian release aliases allows us test and manage the required config changes easier.

[Launchpad Janitor (janitor)]

[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]

[Tim Webster (tdwebste)]

Expired

Please read bug report and suggested fix supplied in previous message.

On 9/22/07, Launchpad Janitor <email address hidden> wrote:
> [Expired for apache2 (Ubuntu) because there has been no activity for 60
> days.]
>
> --
> Apache2 Fails to install/start
> https://bugs.launchpad.net/bugs/95162
> You received this bug notification because you are a direct subscriber
> of the bug.
>