my apache server is to run OK without any problems. It also doesn"t issue any warning during restart. However, if I examine error.log I have the right to see the adhering to lines repeating native time to time:

AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4 configured -- resuming typical operations AH00094: Command line: "/usr/sbin/apache2" AH00169: caught SIGTERM, shutting downWhat perform they say? How can I fix it?

enhance this question
request Jun 25 "14 in ~ 15:18

Max KoretskyiMax Koretskyi
66711 yellow badge77 silver- badges1515 bronze badges
add a comment |

1 prize 1

active earliest Votes
The log paper just mirrors some startups/shutdowns of Apache workers. In her Apache configuration, you can set how many workers (aka threads) Apache might use. Top top a consistent setup, Apache have the right to be started number of times. Particularly when your server is liven (e.g. There are many visitors on among your vhosts), it"s no strange to see 20 (or more) Apache processes running. There is nothing to worry about, they"re just informational.

You are watching: Ah00169: caught sigterm, shutting down

AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4 configured -- resuming typical operations

This way a brand-new thread spawned under procedure id 8817.

AH00094: Command line: "/usr/sbin/apache2"

This is just a an alert saying that the /usr/sbin/apache2 command was used to begin the thread, so no one-of-a-kind flags/options were passed come it.

AH00169: recorded SIGTERM, shutting down

This line tells you the the process with process id 8817 has shut down again.

See more: Witcher 3 Spoils Of War White Orchard Spoils Of War Location Guide

This log was invoked by /etc/apache2/apache2.conf which it has actually the directive pointing to the log document that you space seeing at. Come see much less of the logging, you can edit this line in apache2.conf LogLevel warn to LogLevel error which will log only if over there is error that leading to the server come malfunction. Options for that logging are: trace1, debug, info, notice, warn, error, crit, alert, emerg. You have the right to play with every one of these choices to discover which logging level you favor the most.

To watch the log for her domain, you can discover that in her conf record that organize the configurations for the domain organize in /etc/apache2/sites-available. I.e. Yoursite.conf