I have a fairly fresh install, that has worked until today. I tried to make a subdomain phpmyadmin.bnjpro.dk pointing to https://bnjpro.dk/phpmyadmin. But something went wrong and the apache server will not restart. This means I am not able to use ispconfig to delete the subdomain in order to make apache start again. What can I do to make apache start again? Here is the output of journalctl -xn: Code: Jan 22 20:34:23 freja systemd[1]: Starting The Apache HTTP Server... ░░ Subject: A start job for unit apache2.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit apache2.service has begun execution. ░░ ░░ The job identifier is 1695. Jan 22 20:34:23 freja apachectl[2854]: AH00548: NameVirtualHost has no effect a> Jan 22 20:34:23 freja apachectl[2851]: Action 'start' failed. Jan 22 20:34:23 freja apachectl[2851]: The Apache error log may have more infor> Jan 22 20:34:23 freja systemd[1]: apache2.service: Control process exited, code> ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit apache2.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jan 22 20:34:23 freja systemd[1]: apache2.service: Killing process 2855 (vlogge> Jan 22 20:34:23 freja systemd[1]: apache2.service: Killing process 2855 (vlogge> Jan 22 20:34:23 freja systemd[1]: apache2.service: Failed with result 'exit-cod> ░░ Subject: Unit failed lines 1-23...skipping... Jan 22 20:34:23 freja systemd[1]: Starting The Apache HTTP Server... ░░ Subject: A start job for unit apache2.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit apache2.service has begun execution. ░░ ░░ The job identifier is 1695. Jan 22 20:34:23 freja apachectl[2854]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-ispconfig.vhost:7 Jan 22 20:34:23 freja apachectl[2851]: Action 'start' failed. Jan 22 20:34:23 freja apachectl[2851]: The Apache error log may have more information. Jan 22 20:34:23 freja systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit apache2.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jan 22 20:34:23 freja systemd[1]: apache2.service: Killing process 2855 (vlogger (access) with signal SIGKILL. Jan 22 20:34:23 freja systemd[1]: apache2.service: Killing process 2855 (vlogger (access) with signal SIGKILL. Jan 22 20:34:23 freja systemd[1]: apache2.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'. Jan 22 20:34:23 freja systemd[1]: apache2.service: Unit process 2855 (vlogger (access) remains running after unit stopped. Jan 22 20:34:23 freja systemd[1]: Failed to start The Apache HTTP Server. ░░ Subject: A start job for unit apache2.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit apache2.service has finished with a failure. ░░ ░░ The job identifier is 1695 and the job result is failed.
delete the website vhost symlink of the site you just edited in /etc/apache2/sites-enabled/ folder and then start apache.
You are absolutely right. deleting the vhost did the trick. Thank you. Is there a reason why it went sideways when trying to make that redirection?
Is config check enabled for apache under system > server config > web? This should prevent such failures.
No, not in this round. I have changed the ciphers in order to get a better score at qualysSSL But that was a week ago, and that didn't trip it. And I haven't changed it now in order to get the apache up again. It restarted right away when I deleted the symlink you suggested.
