[systemd-devel] mdmon at md127 is stopped early

[Lennart Poettering]

On Mi, 09.02.22 17:16, Mariusz Tkaczyk (mariusz.tkaczyk at linux.intel.com) wrote:

> It is probably wrong, but it worked this way for many years:
> "Again: if your code is being run from the root file system, then this
> logic suggested above is NOT for you. Sorry. Talk to us, we can
> probably help you to find a different solution to your problem."[3]
>
> How can I block the service from being stopped? In initramfs there is a
> mdmon restart procedure, for example in dracut[4]. I need to save
> mdmon process from being stopped.
>
> I will try to adapt our implementation to your[3] suggestions but it is
> longer topic, I want to workaround the issue first.
>
> [1]https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
> [2]https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/tree/systemd/mdmon@.service

So with that unit systemd shouldn#t stop it the service at all, given
that you set DefaultDependencies=no.

It would be good to figure out why it is stopped anyway. i.e. check
with "systemctl show" on the unit what kind of requirement/conflicts
deps there are which might explain it.

Otherwise there might simply be another program that explicitly tells
systemd to shut this stuff down, i.e. some script or so. Turn on debug
logging (systemd-analyze log-level debug) before shutting down, the
logs should tell you a thing or two about why the service is stopped.

Lennart

--
Lennart Poettering, Berlin