When I am trying to restart the apache from WHM. I keep getting the following message:


+++++++++++++++++++++++++++++++++++++
Attempting to restart httpd


Not Found

The requested URL /server-status was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to
use an ErrorDocument to handle the request.
_________________________________________________________________


Apache/1.3.20 Server at host.xxx.com Port 80

httpd has failed, please contact the sysadmin.
++++++++++++++++++++++++++++++++++++

Can someone give me some directions?

hmmm... check your apache error logs.. you can find it at
/usr/local/apache/logs/

See what it says... and then move from there..

It looks like it's trying to spawn the lynx browser to go to your local address and display or use the server-status page's URL -- but it can't, because Apache isn't currently up. You would get that same error if you stopped Apache and tried it via the command line, since Apache wouldn't be up for it to go to that URL on the local server. I don't know why it'd have a simple restart do that though!

WHen I type in this command: /etc/rc.d/init.d/httpd configtest.

I am getting a bunch of messages like:

[Sun Sep 9 02:11:43 2001] [warn] VirtualHost 216.139.221.xx1:80 overlaps with VirtualHost 216.139.221.xx1:80, the first has precedence, perhaps you need a NameVirtualHost directive
[Sun Sep 9 02:11:43 2001] [warn] NameVirtualHost 216.139.221.xx2:80 has no VirtualHosts

How do I fix up such problem??
Anyhelp would be appreciated.

Anyone who is capable of fixing this problem. Please contact me at besta520@optushome.com.au

Those two warnings, are simply that, just warnings.

For a fix for these problems that you pasted in, simply do this:

Before the FIRST VirtualHost with the IP 216.139.221.xx1, put in:

NameVirtualHost 216.139.221.xx1:80

Note: Do that above the _first_ instance of a VirtualHost using that IP (you needn't specify the port in the actual virtualhost in this regard, but it's okay).

Make sure there are no other NameVirtualHost directives anywhere else with that EXACT same IP and port. (being 216.139.221.xx1:80 -- whatever those xx's stand for). That will ensure that you can use the same IP for other domains or sub domains.

As for the "NameVirtualHost 216.139.221.xx2:80 has no VirtualHosts" error, that just means that you have the NameVirtualHost directive specifying an IP that's not even being used by any VirtualHost. Since there's no VirtualHost using 216.139.221.xx2, you can comment out or remove that NameVirtualHost directive that points to "216.139.221.xx2:80" -- at least until you have a domain/virtual host using it.

Make those changes and run configtest again and they will go away. These are trivial warnings to some degree, yet they are also meaning (at least one anyway) that your virtualhost directives for certain addresses might not work or might (or will) take precedence over another (and that other will never work, since the first instance is overriding the second.) -- and you probably don't want that to happen for obvious reasons.

Thanks Tim. That problem has been resolved.

However, for some reason apache is constantly crashing.
The server cpu load, ram usage all very low.

Originally posted by spiderman
Thanks Tim. That problem has been resolved.

However, for some reason apache is constantly crashing.
The server cpu load, ram usage all very low.

That can be caused due to a few reasons. How often does it crash? Is it sudden or over time? What, if any, errors are in the logs for Apache? What are you running? What have you done when changing the configuration for Apache? I think with all the problems you've been reporting lately on this forum and all the basic questions, that if you are running a web host with customers that are paying, I'd highly suggest and advise you to hire someone with the knowledge needed to properly set up and configure the server and the tools you run and for general needs and administration. Good luck.