Apache 2.0 Problems

[davef8]

We installed Apache 2.0 onto a VPS machine per the customer's request. Now we are noticing that Apache 2.0 is becoming stuck/un-responsive every 24 hours. Unless apache is shutdown and then restarted it stays "hung". When the server is not responding the status command shows that the Apache server is still running.

Here is what is in the log file:
[Sun Jul 25 19:44:56 2004] [notice] caught SIGTERM, shutting down
[Sun Jul 25 19:45:02 2004] [notice] Apache/1.3.31 (Unix) mod_ssl/2.8.19 OpenSSL/0.9.7a PHP/4.3.8 mod_perl/1.27 FrontPage/5.0.2.2510 configured -- resuming normal operations

From these messages it would appear that something is shutting down Apache 2.0 and then starting Apache 1.3 instead. Does this make any sense? We have deleted the /etc/httpd folder and Apache 2.0 is located in /usr/local/apache2.

We have tried running the DA nightly housekeeping script

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

to see if that was the cause but this had no effect.

We also tried some techniques from other postings on these forums such as the Apache "restart tweaks" that others have used but these didn't help either. Besides the "error_log" is there a better place to investigate this issue? Besides the /etc/httpd folder where else would old Apache 1.3 files be located?

 

[thoroughfare]

DA isn't designed to use Apache 2 AFAIK, only Apache 1.3x

Matt

 

[davef8]

I understand it is not designed for Apache 2.0. However I noticed some threads from others who have successfully gotten Apache 2.0 to work and I was hoping they might be able to shed some light on this issue.

 

[jmstacey]

From these messages it would appear that something is shutting down Apache 2.0 and then starting Apache 1.3 instead. Does this make any sense? We have deleted the /etc/httpd folder and Apache 2.0 is located in /usr/local/apache2.

My guess is that would be DA. Try doing something like this:
http://help.directadmin.com/item.php?id=25

Substituting named with Apache

Or to get service monitoring working on Apache2 try figuring out why DA is not detecting the httpd service. Like does apache2 use a different process name? Stuff like that.