Apache pid file

In order to do this it has to keep the scoreboard used to keep track of all children across generations. The status module will also use a G to indicate those children which are still serving requests started before the graceful restart was given. At present there is no way for a log rotation script using USR1 to know for certain that all children writing the pre-restart log have finished.

We suggest that you use a suitable delay after sending the USR1 signal before you do anything with the old log. For example if most of your hits take less than 10 minutes to complete for users on low bandwidth links then you could wait 15 minutes before doing anything with the old log. When you issue a restart, a syntax check is first run, to ensure that there are no errors in the configuration files. If your configuration file has errors in it, you will get an error message about that syntax error, and the server will refuse to restart.

This avoids the situation where the server halts and then cannot restart, leaving you with a non-functioning server. This still will not guarantee that the server will restart correctly. To check the semantics of the configuration files as well as the syntax, you can try starting httpd as a non-root user. If there are no errors it will attempt to open its sockets and logs and fail because it's not root or because the currently running httpd already has those ports bound.

If it fails for any other reason then it's probably a config file error and the error should be fixed before issuing the graceful restart. It re-reads its configuration files, and re-opens any log files. Then it spawns a new set of children and continues serving hits. The WINCH or graceful-stop signal causes the parent process to advise the children to exit after their current request or to exit immediately if they're not serving anything.

The parent will then remove its PidFile and cease listening on all ports. The parent will continue to run, and monitor children which are handling requests. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How to restart apache2 when I get a pid conflict? Ask Question. Asked 7 years, 10 months ago.

Active 3 years, 10 months ago. Viewed 38k times. The command pidof apache2 returns : I don't know if it will help but here is the line in apache2. Thank you very much! Improve this question. Community Bot 1. Ivan Gabriele Ivan Gabriele 1 1 gold badge 8 8 silver badges 17 17 bronze badges.

How was Apache installed? Arenstar Arenstar 3, 2 2 gold badges 24 24 silver badges 34 34 bronze badges. I have tried it but apache2 start shows same errors — user You need to kill what ever is running on port The PID complaint is only because you are trying to stop something that hasnt written a pid..

Or a precompiled version of apache? After running sudo killall -9 httpd , the built-in apache stop serving. Realizing that apachectl will auto-restart each time I killall httpd. Scott Chu Scott Chu 2 2 bronze badges. Michael Hampton k 39 39 gold badges silver badges bronze badges. Sirajuddin Khan Sirajuddin Khan 1. And after that, then what? Allan Karseth Allan Karseth 1. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.