Re: Bug#253203: apache will not start due to syntax error
On Tue, Jun 08, 2004 at 10:37:45AM -0400, William R. McDonough wrote:
> > Try "bash -x /usr/sbin/apachectl start"
> > --
> + PIDFILE=/var/run/apache.pid
> + HTTPD=/usr/sbin/apache
> + LYNX=lynx -dump
> + STATUSURL=http://localhost/server-status
> + ERROR=0
> + ARGV=start
> + '[' xstart = x ']'
> + '[' -f /var/run/apache.pid ']'
> ++ cat /var/run/apache.pid
> + PID=14803
> + '[' x14803 '!=' x ']'
> + kill -0 14803
> + STATUS=httpd (pid 14803?) not running
> + RUNNING=0
> + '[' 0 -eq 1 ']'
Ok, we're in 67 of apachectl ....
The next thing is: 'if /usr/sbin/apache'
> + /usr/sbin/apache
> Bareword found where operator expected at /dev/null line 1, near
Hmm, this looks more like a message from apache starting up.
> (Missing operator before bin?)
> Number found where operator expected at /dev/null line 1, near "line 68"
> (Do you need to predeclare line?)
> syntax error at /dev/null line 1, near "/usr/sbin"
> Execution of /dev/null aborted due to compilation errors.
> parse: Success
Haven't done perl in a while, but this looks _awfully_ close to a
perl error message :-/ Let's test.
$ perl -e '/usr/sbin'
Bareword found where operator expected at -e line 1, near "/usr/sbin"
(Missing operator before bin?)
Hmm, something seems to feed '/usr/sbin' to a perl interpreter. Do you
by any chance have mod_perl installed and maybe a 'PerlRequire' that loads
the wrong file?
> + echo '/usr/sbin/apachectl start: httpd could not be started'
> + ERROR=3
> + exit 3
HTH Ralf Mattes
> To UNSUBSCRIBE, email to debian-apache-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com