Summary: | sys-fs/mdadm-4.0 with systemd: service mdmonitor.service fails in default configuration | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Dummer <martin.dummer> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexanderyt, arthur, bertrand, leonchik1976, martin.dummer, systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Dummer
2017-08-26 11:07:31 UTC
1) nope mail address should be manually set in /etc/mdadm.conf (see on few last lines, before the ones of your arrays, that you've added on their initialisation). Also, as you can see, there is "-" sign before both `/run/sysconfig/mdadm` and `/usr/lib/systemd/scripts/mdadm_env.sh`. This means "it is ok to fail". And it fails exactly because you didn't set the email in mdadm.conf 2) although, I came here to report this exactly bug, but with another argumentation: a) `/run/sysconfig` looks like definitelly non-gentoo path. And looks like that systemd unit was copy-pasted from archlinux or so. b) well, it would be nice to either drop /usr/lib/systemd/scripts/mdadm_env.sh from the unit and make conf.d/mdadm the EnvironmentFile, or create that file during package installation and make it to do something useful. Sadly this seems to be stuck here for years. I've just tried to enable the service file and got 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. The other reported issues with /usr/lib/systemd/scripts/mdadm_env.sh are still in there as well. (In reply to r7l from comment #2) > Sadly this seems to be stuck here for years. I've just tried to enable the > service file and got 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. > > The other reported issues with /usr/lib/systemd/scripts/mdadm_env.sh are > still in there as well. I guess, "the right way" would be to use per-device `mdmon@` service :) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b0152d3ed507c45608377046bc2f65a48b47ec10 commit b0152d3ed507c45608377046bc2f65a48b47ec10 Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2024-02-19 20:32:53 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2024-02-19 21:00:55 +0000 sys-fs/mdadm: improve mdmonitor on systemd Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> Closes: https://bugs.gentoo.org/628968 sys-fs/mdadm/files/mdadm-4.2-mdadm_env.patch | 36 ++++++++++ sys-fs/mdadm/mdadm-4.2-r3.ebuild | 104 +++++++++++++++++++++++++++ 2 files changed, 140 insertions(+) |