[dm-devel] multipath-tools: enabling multipathd.service fails
Michael Laß
bevan at bi-co.net
Sun Nov 12 13:03:45 UTC 2017
Hi,
when running "systemctl enable multipathd.service", systemd also wants
to enable multipathd.socket due to the following line in
multipathd.service:
> [Install]
> ...
> Also=multipathd.socket
At least on systems running systemd 235, this leads to the following
error:
> 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.
This error occurs because multipathd.socket is missing an [Install]
section and in particular a "WantedBy" line, so systemd does not know
how to enable it. The section was removed in commit
62ef3766d9472f2122bc1dbd1e685f3e914b626b a few years ago.
I guess there are two options to fix this: either removing the "Also"
line in multipathd.service so that multipathd.socket is not enabled as
well, or adding back an [Install] section to multipathd.socket.
Cheers,
Michael
More information about the dm-devel
mailing list