[notice] caught SIGTERM, shutting down

Need some help please …

Was performing basic testing to verify system readiness, etc… After issuing a shutdown -r now I found that Apache did not load.

In the /var/log/httpd/error_log I find the error:

[notice] caught SIGTERM, shutting down

After manually starting: sudo service httpd start apache loads and the following is displayed in the httpd log:

[Sun Dec 18 02:44:58 2011] [notice] Digest: generating secret for digest authentication …

[Sun Dec 18 02:44:58 2011] [notice] Digest: done

[Sun Dec 18 02:44:58 2011] [notice] Apache/2.2.15 (Unix) PHP/5.3.2 configured – resuming normal operations

postdrop: warning: unable to look up public/pickup: No such file or directory

What would cause apache not to start automatically on server load?

I did verify httpd exists in the /etc/rc.d/init.d directory

Your thoughts are appreciated!


2 Replies

Apache may have hung due to insufficient entropy in /dev/random. Sometimes this is a problem on virtual machines, because they don't have keyboards or mice to generate random events and have to rely on just disk and network operations. By the time you manually starrted Apache, enough entropy had been added to /dev/random for it to be able to start.

It could also be something as simple as Apache not being configured to start automatically on boot. Assuming you are on a Red Hat-like system such as CentOS or Fedora, the chkconfig –list command will show you which services are set to start for each runlevel. You should see a line like

httpd           0:off   1:off   2:on    3:on    4:on    5:on    6:off

If instead it says "off" all the way across, you can activate it with chkconfig httpd on.


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct