Droplet (almost) dead

February 19, 2019 292 views
Apache LAMP Stack

When I rebooted my droplet it completely locked down. I cannot access with SSH or FTP. I cannot even ping the domain on it. I can only access with the "Console access" from my DO account.

Analysis of the apache error log learns that it rebooted three times with a few minutes. Each time that produced the following entries:
mpmprefork:notice AH00171: graceful restart requested. Doing restart
mpm
prefork:notice AH00163: Apache/2.4.29 (Ubuntu)mod_fcgid/2.3.9 OpenSSL/1.1.0g configured -- resuling normal operations
core:notice AH00094 Command line: '/usr/sbin/apache2'

After that I got:
mpmprefork AH00169: caught SIGterm, shutting down
suexec:notice suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
mpm
prefork:notice AH00163: Apache/2.4.29 (Ubuntu)mod_fcgid/2.3.9 OpenSSL/1.1.0g configured -- resuling normal operations
core:notice AH00094 Command line: '/usr/sbin/apache2'

That was the end of it.

This is a fresh Ubuntu 18.04 droplet with Virtualmin installed.
I am not aware of having done anything extraordinary since the previous reboot: just installing PHP modules, changing php.ini a bit and uploading files.

1 comment
2 Answers

Hey friend!

I'm sorry about the trouble this is causing for you. It sounds like your droplet's network is out entirely. Here's something our support team put together to help with that situation:

https://www.digitalocean.com/community/questions/having-trouble-with-the-network-on-your-droplet

Jarland

I tried switching the Apache loglevel to debug but that didn't produce any meaningful result. Further "service apache2 restart"s didn't produce anything meaningful in the log at all.

In the end I tried "reboot" and then mysteriously things started working again. But I have no idea what was wrong and except for the loglevel I didn't change anything.

Have another answer? Share your knowledge.