For now, try commenting out the "Order" line. If necessary, that whole 4 line block. See if it will come up that way. If it does, then we need to understand what it does not like about those particular lines. Is the "Order" statement syntactically correct? Is it within the right scope?

Did you upgrade apache from a previous version on that box? Perhaps the config file is left over from the previous upgrade? Apache has a long history of changing the syntax of the config files, but I would have thought that to be stable by now.

Regards,
-S-

On Mon, 9 Apr 2007, [EMAIL PROTECTED] wrote:

Sorry forgot to include the chunk that line 141 comes from:

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

Cheers,

Jason

Hi there,

I've just installed etch onto a Qube2, and have installed the apache2
package via apt-get.

Problem is the package appears broken. Here's the details:

cobalt:/etc# apt-show-versions  | grep apache
apache2-mpm-worker/testing uptodate 2.2.3-4
apache2/testing uptodate 2.2.3-4
apache2.2-common/testing uptodate 2.2.3-4
apache2-utils/testing uptodate 2.2.3-4
cobalt:/etc# /etc/init.d/apache2 start
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!
cobalt:/etc# apache2 -v
Server version: Apache/2.2.3
Server built:   Mar 27 2007 14:28:50
cobalt:/etc# apache2 -l
Compiled in modules:
  core.c
  mod_log_config.c
  mod_logio.c
  worker.c
  http_core.c
  mod_so.c
cobalt:/etc# cat /etc/apt/sources.list
# deb http://ftp.au.debian.org/debian/ testing main

deb http://ftp.au.debian.org/debian/ testing main
deb-src http://ftp.au.debian.org/debian/ testing main

deb http://security.debian.org/ testing/updates main
deb-src http://security.debian.org/ testing/updates main
cobalt:/etc#

I've removed it and reinstalled and same problem.

Any advice?

Sorry if this is the wrong list but I'm a newb to debian :)

Cheers,

Jason

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to