Hi, thanks for the log This seems interesting at first AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
this seemed to me like: 1. had a valid server config 2. start the server/service 3. modify the configuration (broken ServerName) 4. upgrade triggers restart of the server which picks up the new config Due to that it fails to start on the upgrade. But I think that is a red herring as this is not an error that makes it fail to start. Especially as it then says "started" afterwards. Can you check if the error of not being restarted is reproducible be re-installing the package like: $ sudo apt install --reinstall apache2 If it is reproducible - just to be sure - please check and fix your config in regard to the hostname. Retry it again. If with a a fixed hostname you still have the issue that the command to re-install apache does not restart it then you could please in another shell open up journal like $ journalctl -f And then re-install it again checking status before and after. $ sudo systemctl status apache2 $ sudo apt install --reinstall apache2 $ sudo systemctl status apache2 Please report the output of both consoles then here, as with the logs as is I can't find the issue that you are facing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823313 Title: Apache update to 2.4.18-2ubuntu3.10 stopped service but did not start it back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1823313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
