Browse by category
Search | Advanced search
Sometimes Apache refuses to start. When this happens sweat instantly appears on your forehead because without apache running none of your website's are available. Here are some things you can try based on problems we've come across. Hitting the reset switch isn't the solution and not something you should do when you come across a problem like this.
The correct way to start, stop or restart apache is by using the apachectl program. Such as:
Checking Apache configuration
Apachectl can also be used to check the apache configuration, such as:
Check the Apache error logs
Take a look at the error logs (usually "/var/log/httpd/") and see if you can find what's causing the problem.
This is caused by one or more processes running on the 443 (secure socket ) port. To fix this problem first find the process ID's that are running on port 443:
This will return results which look something like:
Where xxxx yyyy & zzzz are numbers for the process ID's. Now kill the processes with:
Apache will not start. Error log contains:
Now, checking your disk shows that you have plenty of space. The problem is that apache didn't shut down properly, and it's left myriads of semaphore-arrays left, owned by my apache-user. Run:
Run the following commands (in that order):
Removing these semaphores immediately should solve the problem and allow apache to start: