Question

Server won't reboot --

Posted August 15, 2019 493 views
Apache DigitalOcean

A few of the sites went down again today, cheaptextbooks.com and dailydeal.com.

I tried to run update code and reboot the server, I ran this:

sudo apt-get update && sudo apt-get dist-upgrade
sudo service apache2 restart

I got this error message:

Job for apache2.service failed because the control process exited with error code. See “systemctl status apache2.service” and “journalctl -xe” for details.

I run systemctl status apache2.service and I get this output:

================================================
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Thu 2019-08-15 12:48:00 UTC; 8min ago
Docs: man:systemd-sysv-generator(8)
Process: 16759 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 5852 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

Aug 15 12:48:00 Droplet5 apache2[5852]: * The apache2 configtest failed.
Aug 15 12:48:00 Droplet5 apache2[5852]: Output of config test was:
Aug 15 12:48:00 Droplet5 apache2[5852]: AH00526: Syntax error on line 24 of /etc/apache2/sites-enabled/coder-forge.com-le-ssl.conf:
Aug 15 12:48:00 Droplet5 apache2[5852]: SSLCertificateFile: file ’/etc/letsencrypt/live/coder-forge.com-0001/fullchain.pem’ does not exist or is empty
Aug 15 12:48:00 Droplet5 apache2[5852]: Action ‘configtest’ failed.
Aug 15 12:48:00 Droplet5 apache2[5852]: The Apache error log may have more information.
Aug 15 12:48:00 Droplet5 systemd[1]: apache2.service: Control process exited, code=exited status=1
Aug 15 12:48:00 Droplet5 systemd[1]: Failed to start LSB: Apache2 web server.
Aug 15 12:48:00 Droplet5 systemd[1]: apache2.service: Unit entered failed state.

Aug 15 12:48:00 Droplet5 systemd[1]: apache2.service: Failed with result 'exit-code’.

If anyone can help I’d appreciate it.

Will pay cash if anyone can help.

Thank you!

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.

1 answer

FIXED!

This issue arises if the following has occurred:

  • apache purged and re-installed
  • SSLs revoked and re-instated

Try first to reboot:
sudo service apache2 restart

Get file that is causing the issue from error log.

Navigate to this directory:
cd /etc/apache2/sites-enabled
unlink YOURDOMAIN.YOURDOMAINEXTENSION-le-ssl.conf

Reboot
sudo service apache2 restart

Submit an Answer