Hello, everyone. Here's a debdiff patch with a backport of upstream patch to xenial branch of systemd.
I've successfully built a modified source and deployed it to some xenial machines — it works as intended, failed service restart correctly, just as intended by Restart=always policy. Before: systemd[1]: vpp.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: Stopped vector packet processing engine. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'core-dump'. systemd[1]: vpp.service: Service hold-off time over, scheduling restart. systemd[1]: vpp.service: Failed to schedule restart job: Transaction is destructive. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'resources'. After: systemd[1]: vpp.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: Stopped vector packet processing engine. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'core-dump'. systemd[1]: vpp.service: Service hold-off time over, scheduling restart. systemd[1]: Stopped vector packet processing engine. systemd[1]: Starting vector packet processing engine... ** Patch added: "debdiff for xenial systemd branch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+attachment/5281628/+files/lp-1839290-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839290 Title: systemd doesn't restart a service after crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
