Note: I compared the upstream and Debian/Ubuntu Service file. Differences are: 1. Service Name (don't care) 2. After=syslog.target which might be reasonable to pick 3. PIDFile=/var/run/keepalived.pid (which is not bad and we thought would be the fix here, but it seems is not required as my zesty test worked) 4. EnvironmentFile this uses different paths and option variables, transitioning this would be an unwanted conffile change
Ubuntu makes no Delta to Debian here, so we should address these there. I might file a bug for 2&3 there later on, but first I'll continue with my a analysis. Next: Repro on Xenial TODO: Understand why not leaving stale PIDs on Zesty anymore (despite not having PIDFile statement) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644530 Title: keepalived fails to restart cleanly due to the wrong systemd settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1644530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
