This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.1
---------------
knockd (0.7-1ubuntu1.18.10.1) cosmic; urgency=medium
* Fix systemd knockd.service file:
- use After=network-online.target (LP: #1819345)
- add [Install] so knockd service can be enabled (LP: #1799697)
-- Dan Streetman <ddstr...@canonical.com> Sun, 10 Mar 2019 11:13:50
-0400
** Changed in: knockd (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1819345
Title:
knockd systemd service uses After=network.target instead of network-
online.target
Status in knockd package in Ubuntu:
Fix Released
Status in knockd source package in Trusty:
Invalid
Status in knockd source package in Xenial:
Invalid
Status in knockd source package in Bionic:
Fix Released
Status in knockd source package in Cosmic:
Fix Released
Status in knockd source package in Disco:
Fix Released
Status in knockd package in Debian:
New
Bug description:
[impact]
the knockd systemd service file is configured to start knockd
After=network.target, however the systemd 'network.target' only means
network configuration has started, not completed; the interface(s)
that knockd is configured to listen on may not even be up yet. In
that case, starting knockd fails.
[test case]
install, configure, and enable knockd on a system. reboot the system,
and check the logs for knockd errors about the interface not being up.
verify knockd is not running.
Note that since the 'network.target' dependency is essentially a race
condition between knockd.service executing and the interface it
listens on being configured, it may be necessary to have a more
complex network configuration (which takes longer to fully set up) to
more easily trigger this, such as setting up a bridge or bond with
multiple interfaces and using dhcp and configuring knockd to listen on
the bridge or bond interface.
[regression potential]
changing the systemd service dependency to use network-online instead
of network delays when knockd starts, and regressions would be related
to knockd not running before the network was fully configured, or not
running at all if systemd failed to ever reach network-online target.
[other info]
this requires the knock systemd service file fix from bug 1799697
also, since the knockd systemd service cannot be enabled at all
without that fix.
this applies only to b/c/d since t/x use upstart for service
management, and this bug is only in the knockd systemd service file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1819345/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
