Correction to the initial scenario: it turns out that the service restart (quick or not) is irrelevant. It was not obvious because the problem happens sporadically, so after adding a delay the test was passing by pure chance.
Further experiments have shown that to get the pseudo-dead service, it is enough to do # After reboot, mariadb service is already running sudo systemctl disable mariadb # optional delay sudo systemctl enable mariadb # optional delay sudo systemctl status mariadb # At this point we have the "dead" service, further shutdown causes systemd abort. On my machine it failed in ~30-40% of runs, but it is highly volatile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506206 Title: systemd abort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506206/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
