Hi all

When I run
# /etc/init.d/httpd start

then I get the error:

Starting httpd: [FAILED]

and "httpd status" still shows "stopped".

When I run
# bash -x /etc/init.d/httpd start then I get lots of output including
2 configuration warning messages and httpd starts.

I cannot explain why httpd only starts with "bash -x".

Can someone please tell me how to tweak these scripts so I can see the
errors without "bash -x"?

There are no errors in the log files.

Many thanks

BErnard

On Wed, 31 May 2006 22:58:08 +1200, Bernard wrote:
> Hi all
>
> When I run
> # /etc/init.d/httpd start
>
> then I get the error:
>
> Starting httpd: [FAILED]
>
> and "httpd status" still shows "stopped".

How about tailing the error_log file?

--
* John Oliver http://www.john-oliver.net/ *
* Reform California gun laws - http://www.reformcagunlaws.com/ *
* http://www.gunownersca.com - http://www.crpa.org/ *
* San Diego shooters come to http://shooting.forsandiego.com/ *

John

You mean tail -f error_log?
I am confused. There are no errors in the log file.

Bernard


John Oliver <joliver@john-oliver.net> wrote:

>On Wed, 31 May 2006 22:58:08 +1200, Bernard wrote:
>> Hi all
>>
>> When I run
>> # /etc/init.d/httpd start
>>
>> then I get the error:
>>
>> Starting httpd: [FAILED]
>>
>> and "httpd status" still shows "stopped".
>
>How about tailing the error_log file?

On Thu, 01 Jun 2006 19:54:12 +1200, Bernard wrote:
> John
>
> You mean tail -f error_log?
> I am confused. There are no errors in the log file.

So, if you open one terminal and tail -f error_log, and then in another
terminal start httpd and get a failure, nothing is logged?

If you're working in one window, try to start httpd, then just tail
error_log Also, check your httpd.conf to be certain you're looking at
the same error_log that your httpd is using.

--
* John Oliver http://www.john-oliver.net/ *
* Reform California gun laws - http://www.reformcagunlaws.com/ *
* http://www.gunownersca.com - http://www.crpa.org/ *
* San Diego shooters come to http://shooting.forsandiego.com/ *

On Thu, 01 Jun 2006 19:54:12 +1200, Bernard wrote:
> John
>
> You mean tail -f error_log?
> I am confused. There are no errors in the log file.

So, if you open one terminal and tail -f error_log, and then in another
terminal start httpd and get a failure, nothing is logged?

If you're working in one window, try to start httpd, then just tail
error_log Also, check your httpd.conf to be certain you're looking at
the same error_log that your httpd is using.

--
* John Oliver http://www.john-oliver.net/ *
* Reform California gun laws - http://www.reformcagunlaws.com/ *
* http://www.gunownersca.com - http://www.crpa.org/ *
* San Diego shooters come to http://shooting.forsandiego.com/ *

Oliver

Thanks for your kind suggestions.

There is little progress.
Definitely all your conditions are met.

I am at a point where the change of a single configuration directive
makes the difference but no sense.

#DocumentRoot "/var/www/html"
DocumentRoot "/home/test/html"

where /home/test/html is fully accessible by the apache user.

So with DocumentRoot "/home/test/html"
httpd fails, and the error log file is not even created if I delete it
before starting httpd.


The creazy point is that when I start httpd with the same failing
configuration and

bash -x /etc/init.d/httpd start

then everything is ok and I get good entries in error_log.

Also

/etc/init.d/httpd configtest

is ok.

This is not the normal type of error. I have never seen anything as
crazy as this.

What annoys me is that the script is actually detecting an error but
it does not tell me what it is.

Someone please tell me how to myself.

Thanks

Bernard


John Oliver <joliver@john-oliver.net> wrote:

>On Thu, 01 Jun 2006 19:54:12 +1200, Bernard wrote:
>> John
>>
>> You mean tail -f error_log?
>> I am confused. There are no errors in the log file.
>
>So, if you open one terminal and tail -f error_log, and then in another
>terminal start httpd and get a failure, nothing is logged?
>
>If you're working in one window, try to start httpd, then just tail
>error_log Also, check your httpd.conf to be certain you're looking at
>the same error_log that your httpd is using.

Oliver

Thanks for your kind suggestions.

There is little progress.
Definitely all your conditions are met.

I am at a point where the change of a single configuration directive
makes the difference but no sense.

#DocumentRoot "/var/www/html"
DocumentRoot "/home/test/html"

where /home/test/html is fully accessible by the apache user.

So with DocumentRoot "/home/test/html"
httpd fails, and the error log file is not even created if I delete it
before starting httpd.


The creazy point is that when I start httpd with the same failing
configuration and

bash -x /etc/init.d/httpd start

then everything is ok and I get good entries in error_log.

Also

/etc/init.d/httpd configtest

is ok.

This is not the normal type of error. I have never seen anything as
crazy as this.

What annoys me is that the script is actually detecting an error but
it does not tell me what it is.

Someone please tell me how to myself.

Thanks

Bernard


John Oliver <joliver@john-oliver.net> wrote:

>On Thu, 01 Jun 2006 19:54:12 +1200, Bernard wrote:
>> John
>>
>> You mean tail -f error_log?
>> I am confused. There are no errors in the log file.
>
>So, if you open one terminal and tail -f error_log, and then in another
>terminal start httpd and get a failure, nothing is logged?
>
>If you're working in one window, try to start httpd, then just tail
>error_log Also, check your httpd.conf to be certain you're looking at
>the same error_log that your httpd is using.