Question
OpenSSL is causing my server to crash (I think)
- Posted on April 3, 2018
- ApacheLet's EncryptUbuntu 16.04
Asked by Jack Harding
Hi there. I have an Apache server running on Ubuntu 16.04 and I have multiple websites running on it. I’ve noticed that occasionally, all of my sites are down with ‘This site cannot be reached’ errors. Restarting apache fixes this, but I’m just tring to find the cause. I’ve looked in the error logs and I noticed this:
[Mon Apr 02 12:31:31.411760 2018] [mpm_prefork:notice] [pid 20212] AH00163: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations
[Mon Apr 02 12:31:31.411836 2018] [core:notice] [pid 20212] AH00094: Command line: '/usr/sbin/apache2'
[Mon Apr 02 12:31:31.543994 2018] [mpm_prefork:notice] [pid 20212] AH00169: caught SIGTERM, shutting down
Am I right in thinking that this is the cause of my problem? I followed the tutorial here for enabling SSL, but ran in to some issues where I had to do things differently. I basically just ran commands I found on Google until it worked (stupid I know, but I’m very inexperienced with this stuff).
If anyone could tell me how I could resolve this, I would be very grateful!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
The log snippet you shared does not in itself indicate an issue. The
caught SIGTERM, shutting downis what Apache logs normally when it receives a stop or restart command.Can you share your Apache configuration found in /etc/apache2/sites-enabled (feel free to change identifying names to something like example.org if you’d like. Seeing this will help in identifying the problem.
As this happens randomly it’s also possible that it’s related to resource usage, especially if this is a smaller droplet. Are you using the monitoring agent on your droplet?