Re: Apache won't start. Apacheconfig spews warnings/errors.

[Pluto <plutoplanet@freenet.co.nz>]

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 server configuration
>       /usr/sbin/apachectl start: httpd could not be started
> 
> I haven't altered /etc/apache/httpd.conf.  Where did the invalid command
> 'ExtendedStatus' come from?  If I comment this command and try to start
> apache, I'm taken to another invalid command, and then another, and so
> on.  Finally, after I comment 8 or 12 invalid commands apache will start.
> apachectl has worked fine until a few days ago.
> 
> I do this:
> 
>       apacheconfig
> 
> And get this:
> 
>       Finding DSO mods....
>       Use of uninitialized value in pattern match (m//) at
>       /usr/sbin/apacheconfig line 484.
>       ..Use of uninitialized value in pattern match (m//) at
>       /usr/sbin/apacheconfig line 484.
>       Use of uninitialized value in pattern match (m//) at
>        /usr/sbin/apacheconfig line 484.
> 
> and so on for a few screens.  Finally the config files are generated,
> and, upon attempted restart, the above-described 'Invalid Command' errors
> appear.
> 
> Here is line 484 of /usr/sbin/apacheconfig:
> 
>       if ($main::allconf =~ m/^\s*$l\W/m)
> 
> Are the apacheconfig messages related to the invalid commands in
> /etc/apache/httpd.conf?  Is Perl issuing errors or warnings?  Should I
> just manually fix /etc/apache/httpd.conf and go on my merry way?
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 



-- 
P