The Update Apache tool in WHM seems faulty. Items I had checked off before were unchecked. Why? So I rechecked the items and ran it only to get the dreaded "httpd has failed, please contact the sysadmin" message. It will not restart. Here's part of the log in /usr/local/apache/logs/error_log:
Reply With Quote
[Sun May 1 12:03:05 2005] [error] [client 68.142.250.49] File does not exist: /home/talkandm/public_html/forums/printthread.php
[Sun May 1 12:03:05 2005] [error] [client 68.142.250.49] File does not exist: /home/talkandm/public_html/404.shtml
[Sun May 1 12:06:07 2005] [notice] caught SIGTERM, shutting down
[Sun May 1 12:06:11 2005] [notice] Apache/1.3.33 (Unix) mod_perl/1.26 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4$
[Sun May 1 12:06:11 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Sun May 1 12:06:11 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
2005-05-01 12:06:11 1DSGxP-0000d5-Tz Rewrite of nobody@host.domain.com yielded unparseable address: malformed address$
2005-05-01 12:06:11 1DSGxP-0000d5-Tz Rewrite of nobody@host.domain.com yielded unparseable address: malformed address$
[Sun May 1 12:09:39 2005] [warn] pid file /usr/local/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Sun May 1 12:09:39 2005] [notice] Apache/1.3.33 (Unix) mod_perl/1.26 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4$
[Sun May 1 12:09:39 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Sun May 1 12:09:39 2005] [notice] Accept mutex: sysvsem (Default: sysvsem)
What's the sense of checking off what mods you want installed if WHM ignores them on the next update? How do you get around this?



LinkBack URL
About LinkBacks
Reply With Quote




