I woke up to an unexpected problem with my RAQ4 this morning.
None of the websites are accessible with my browser. I can communicate via Telnet. I can log in with FTP. I can download mail.
I have rebooted through Telnet, and the machine has also been front-panel-rebooted via support. I have looked at the log files and nothing mysterious there.
When I try to access a site, they call come back with a "The page cannot be displayed" error in IE, and "The connection was refused when attempting to contact ... (domain)" in Firefox. I have not made any changes to the httpd.conf file - in fact, I have not done anything for weeks! That's why it's so unexpected. The server was working fine until yesterday.
Folks, thanks for all your ideas & suggestions. (Surprisingly,) the problem has been resolved by my host's technical support people. I'm highly impressed!
One of my team had removed an old unused site from the server simply by deleting the site directory in /home/sites/ but he had not removed the site from the httpd.conf file. So everytime Apache was started it was hanging up looking for the directory. The problem was not immediately apparent to him at the time because it only caused a problem when Apache was next stopped/started (the server reboots by a cron job every 24 hours).
The solution was to remove the site from httpd.conf and now Apache starts properly and everything is back to normal!
Something sounds wrong. The admin area and the normal apache are 2 seperate copies running on 2 different ports. If something broke on your main apache, your admin area should NOT die. If your admin area apache died, your normal apache should not die either.
Have you tried telnetting to port 80 to see if you get a http accept?
I have set a cron job to delete the logs in /var periodically as I had the same /var filled problem a while ago.
The Cobalt control panel has been broken on my server for a very long time. We never got round to investigating it. Instead we starting editing httpd.conf and making any changes directly from the command line, and that has worked fine for us.
http://your.server:81/.cobalt/sysManage/ is now accessible again (but still broken - I get an "Internal Server Error" and the site list is not shown / other monitors do not report) but I cannot telnet to port 80 (nothing happens). But we've managed to live without the control panel now.