marked invalid for t/x since upstart is used in those releases, not
systemd, and this affects only systemd-controlled knockd.
** Changed in: knockd (Ubuntu Trusty)
Status: In Progress => Invalid
** Changed in: knockd (Ubuntu Xenial)
Status: In Progress => Invalid
** Changed in: knockd (Ubuntu Trusty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: knockd (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Description changed:
+ [impact]
+
+ on systems controlled by systemd, the knockd service will never start
+ because it is not possible to enable it.
+
+ [test case]
+
+ install a system that uses systemd, and install knockd package. try to
+ enable the service:
+
+ $ sudo systemctl enable knockd
+ Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
+ Executing: /lib/systemd/systemd-sysv-install enable knockd
+ The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
+ settings in the [Install] section, and DefaultInstance for template units).
+ This means they are not meant to be enabled using systemctl.
+ Possible reasons for having this kind of units are:
+ 1) A unit may be statically enabled by being symlinked from another unit's
+ .wants/ or .requires/ directory.
+ 2) A unit's purpose may be to act as a helper for some other unit which has
+ a requirement dependency on it.
+ 3) A unit may be started when needed via activation (socket, path, timer,
+ D-Bus, udev, scripted systemctl call, ...).
+ 4) In case of template units, the unit is meant to be enabled with some
+ instance name specified.
+
+
+ after fixing the knockd.service file, the service can be enabled:
+
+ $ sudo systemctl enable knockd.service
+ Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
+ Executing: /lib/systemd/systemd-sysv-install enable knockd
+
+
+ [regression potential]
+
+ very low, as knockd is useless currently since it can never be started
+ from systemd. any regressions would be in the area of starting knockd.
+
+ [other info]
+
+ the systemd service for knockd also needs the fix from bug 1819345
+
+ original description:
+
+ ---
+
+
About my Ubuntu:
Description: Ubuntu 18.04
Release: 18.04
About Knockd:
knockd:
Installed: 0.7-1ubuntu1
Candidate: 0.7-1ubuntu1
Version table:
*** 0.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
>>>>>>>>>>
When enabling knockd with systemctl y get the following error:
###
$ sudo systemctl enable knockd
Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable knockd
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
###
It doesnt start at boot also.
If I add the following to the end of /lib/systemd/system/knockd.service then
I can enable it successfully and starts at boot:
###
[Install]
WantedBy=multi-user.target
Alias=knockd.service
###
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: knockd 0.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 24 14:42:40 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-28 (483 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
SourcePackage: knockd
UpgradeStatus: Upgraded to bionic on 2018-08-10 (74 days ago)
** Description changed:
[impact]
on systems controlled by systemd, the knockd service will never start
because it is not possible to enable it.
[test case]
install a system that uses systemd, and install knockd package. try to
enable the service:
$ sudo systemctl enable knockd
Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable knockd
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
-
after fixing the knockd.service file, the service can be enabled:
$ sudo systemctl enable knockd.service
Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable knockd
-
[regression potential]
very low, as knockd is useless currently since it can never be started
from systemd. any regressions would be in the area of starting knockd.
[other info]
the systemd service for knockd also needs the fix from bug 1819345
+ this applies only to b/c/d since t/x use upstart to manage services, and
+ this problem is only in the knockd systemd service file.
+
original description:
---
-
About my Ubuntu:
Description: Ubuntu 18.04
Release: 18.04
About Knockd:
knockd:
Installed: 0.7-1ubuntu1
Candidate: 0.7-1ubuntu1
Version table:
*** 0.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
>>>>>>>>>>
When enabling knockd with systemctl y get the following error:
###
$ sudo systemctl enable knockd
Synchronizing state of knockd.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable knockd
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
###
It doesnt start at boot also.
If I add the following to the end of /lib/systemd/system/knockd.service then
I can enable it successfully and starts at boot:
###
[Install]
WantedBy=multi-user.target
Alias=knockd.service
###
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: knockd 0.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 24 14:42:40 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-28 (483 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
SourcePackage: knockd
UpgradeStatus: Upgraded to bionic on 2018-08-10 (74 days ago)
** Changed in: knockd (Ubuntu Trusty)
Importance: Medium => Undecided
** Changed in: knockd (Ubuntu Xenial)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799697
Title:
knockd do not start at boot after enabling it with systemctl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1799697/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
