On Fri, Nov 24, 2000 at 08:38:06AM -0800, Brian wrote:
> A recent update to one or more apache module installation
> scripts resulted in quite a few services being turned off.
>
>[...]
>
> Whichever
> apache update made the changes (I installed several at once)
> disabled mod_status, mod_dir, mod_
A recent update to one or more apache module installation
scripts resulted in quite a few services being turned off.
Edit the section of your /etc/apache/httpd.conf with the
LoadModule lines and check to see which modules might not be
enabled.
Compare against a working server or see if you've got
I'm having the same problem and I know that none of the solutions provided
so far will work. I do have apache-common installed. I went to the
lengths of commenting out the ExtendedStatus line in httpd.conf and then
got a similar syntax error on the first "Order" directive. I commented
that out a
You need to activate mod_status to use ExtendedStatus
Silver
- Original Message -
From: "Matt Miller" <[EMAIL PROTECTED]>
To:
Sent: Friday, November 24, 2000 8:23 AM
Subject: Apache won't start. Apacheconfig spews warnings/errors.
> Syntax error on line 248 of /etc/apache/httpd.conf:
>
Hi,
Have you installed apache-common?
> Running unstable, I do this:
>
> apachectl start
>
> And get this:
>
> Syntax error on line 248 of /etc/apache/httpd.conf:
> Invalid command 'ExtendedStatus', perhaps mis-spelled or
> defined by a module not included in the s
hi matt,
On Fri, 24 Nov 2000, Matt Miller wrote:
> Are the apacheconfig messages related to the invalid commands in
> /etc/apache/httpd.conf? Is Perl issuing errors or warnings?
i do not know as i run potato. i do not use apacheconfig as i can
hardly imagine a script that really configures apach
6 matches
Mail list logo
