I tried to reproduce this by installing 2.4.18-2ubuntu3.9 in a container and then upgrading up to 2.4.18-2ubuntu3.10, but it restarted after upgrade correctly.
Your report of: 2019-04-05 06:33:36 status unpacked apache2:amd64 2.4.18-2ubuntu3.10 2019-04-05 06:33:36 status unpacked apache2:amd64 2.4.18-2ubuntu3.10 [... more than 100 times the same lines ...] 2019-04-05 06:33:37 status unpacked apache2:amd64 2.4.18-2ubuntu3.10 ...seems suspicious to me. However unfortunately since I cannot reproduce I don't think this bug can make any progress. I also don't see any other reports of this problem, which suggests to me that it's caused by something specific to your configuration. We do appreciate the report though - in aggregate these are helpful to find major problems. For now, this bug will have to remain Incomplete since there's nothing that Ubuntu developers can do to identify a bug at this stage. If you can find steps to reproduce the problem, then please provide them and change the bug status back to New. Or if others affected also find this report then please also let us know. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
