Your message dated Tue, 28 Feb 2023 20:49:38 +0000
with message-id <[email protected]>
and subject line Bug#815834: fixed in mdadm 4.2+20230227-1
has caused the Debian Bug report #815834,
regarding mdadm: with systemd as PID 1, no clean way to restart the mdadm
monitor
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
815834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815834
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 3.3.4-1.1+b1
Severity: normal
Hello!
The issue I am reporting may be related to bug #796624, but it's not
the same.
After upgrading packages (especially libraries), I routinely use
"checkrestart" (from package debian-goodies) to see which processes
need to be restarted.
I noticed that, whenever the mdadm monitor process needs to be restarted
(for instance, after a libc6 upgrade), there seems to be no clean way to
actually restart it, if using systemd as PID 1.
Suppose we have to restart the mdadm monitor process:
# checkrestart
[...]
service mdadm-raid restart
service mdadm-waitidle restart
service mdadm restart
[...]
# ps aux | grep mdadm | head -n 1
root 359 0.0 0.0 13620 2508 ? Ss 23:18 0:00 /sbin/mdadm
--monitor --scan
Which service command should I use?
# service mdadm restart
Failed to restart mdadm.service: Unit mdadm.service is masked.
# service mdadm-waitidle restart
Failed to restart mdadm-waitidle.service: Unit mdadm-waitidle.service is
masked.
# service mdadm-raid restart
The first two do nothing, since they are masked.
The last one seems to be successful, but:
# checkrestart
[...]
service mdadm-raid restart
service mdadm-waitidle restart
service mdadm restart
[...]
# ps aux | grep mdadm | head -n 1
root 359 0.0 0.0 13620 2556 ? Ss 23:18 0:00 /sbin/mdadm
--monitor --scan
Nothing has changed! Please note that the mdadm monitor process PID is
the same as before: it has not been restarted.
It seems that, with systemd as PID 1, the available services are
unable to restart the running mdadm monitor...
Please note that, with sysvinit as PID 1, it's possible to restart
the mdadm monitor via the appropriate service.
Please provide a clean way to restart the mdadm monitor process:
I could kill it and then start it again by hand, but it doesn't feel
especially safe to do that...
It seems to me that the init script which is able to restart the
mdadm monitor process is /etc/init.d/mdadm .
I wonder why there's no corresponding service file for systemd and
why the service is masked instead.
Wait, there's /lib/systemd/system/mdmonitor.service : is
# systemctl restart mdmonitor.service
or
# service mdmonitor restart
the clean way I am looking for?
Unfortunately, checkrestart does not suggest it.
Please clarify, thanks for your time!
Bye.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.5.58
ii initscripts 2.88dsf-59.3
ii libc6 2.21-9
ii lsb-base 9.20160110
ii udev 228-6
Versions of packages mdadm recommends:
ii exim4-daemon-light [mail-transport-agent] 4.86-7+b2
ii kmod 22-1
mdadm suggests no packages.
-- debconf information:
mdadm/initrdstart_msg_errblock:
mdadm/initrdstart_msg_errmd:
mdadm/mail_to: root
* mdadm/initrdstart: all
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_msg_intro:
mdadm/autocheck: true
mdadm/start_daemon: true
mdadm/initrdstart_msg_errexist:
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 4.2+20230227-1
Done: Daniel Baumann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann <[email protected]> (supplier of updated mdadm
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 28 Feb 2023 20:48:50 +0100
Source: mdadm
Architecture: source
Version: 4.2+20230227-1
Distribution: experimental
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 815834 822354 829621 850180 889978
Changes:
mdadm (4.2+20230227-1) experimental; urgency=medium
.
* Uploading to experimental.
* Merging upstream version 4.2+20230227.
* Removing sysvinit scripts in favour of systemd units:
- properly checkrestart mdmonitor (Closes: #815834).
- no update-rc.d warnings anymore (Closes: #822354).
- properly shutdown (Closes: #829621).
- making /etc/default/mdadm obsolete for most things (Closes: #850180).
* Removing cron jobs in favour of systemd timers:
- daily checks also work if system is not always on (Closes: #889978).
* Adding rediffed patch from ubuntu to randomize md array check timers.
* Adding rediffed patch from ubuntu to honor debconf daily scan in
systemd unit.
* Adding rediffed patch from ubuntu to fix empty spaces in timer unit
files.
* Wrap and sorting debian directory.
Checksums-Sha1:
3b93e67b353754c1307f31b7de8e2a72bc4fe5bd 2070 mdadm_4.2+20230227-1.dsc
80daf9eb782bc89f8a78a4ae5abedb64642236a5 463064 mdadm_4.2+20230227.orig.tar.xz
39c620f90756cb3d460733bc6e96c77ef6c63c98 86020
mdadm_4.2+20230227-1.debian.tar.xz
ed6235af01928708e2f52f57d39ccfb694953e32 6341
mdadm_4.2+20230227-1_amd64.buildinfo
Checksums-Sha256:
baad2c851ccefa473ed1419cb8b16287aa796b8346e085a6af528993cd66d586 2070
mdadm_4.2+20230227-1.dsc
962d479291fa264076e16405d26dd4399dc53f183237d8d4c7f3b98096d671bd 463064
mdadm_4.2+20230227.orig.tar.xz
1fa793c38d4cd543614502112f863c955a49c89704f728957e7228baf113b763 86020
mdadm_4.2+20230227-1.debian.tar.xz
29fcb34b09912473528f815033545152185950c2afc35167d122a3ddfc8bd65c 6341
mdadm_4.2+20230227-1_amd64.buildinfo
Files:
b342a5f4636fd3905b77a79d2f3d6262 2070 admin optional mdadm_4.2+20230227-1.dsc
461015b69fdefd62ce7bbdca4cff03c3 463064 admin optional
mdadm_4.2+20230227.orig.tar.xz
57309a7deb6fcd4c520344e7d09380c6 86020 admin optional
mdadm_4.2+20230227-1.debian.tar.xz
08ff30683f270c0cf54050f926903098 6341 admin optional
mdadm_4.2+20230227-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmP+XCcACgkQVc8b+Yar
ucdDMg//Vwyo54XsT6sljpj0KYNbLQrZ8ns+Z74kki6fj8YAHiNTPfJZw6NMvmAm
Prhw3viy7HgEN/zmQNikyMSECp29XYSbBt0qzszOwlSK8qmuZcKLMI5MpaRR/zC2
TnYGuiJNfYreEi2QcTeVSX0Ar5ZnyE/bAH2b9ZXDDn64hPe75yKYgfCrigGmMj5Q
OwVQfWVECcq7uCvIhQJUI7NKnDS6p66Bm9xa3372H8IGNSEIBK0QdE7xEUwObwoc
MG2dCmWWdtK7oX/9QYqwvUDuSzQvdzP/6I3NEWXlibMDKkaLtUYox3g6GKkwvdqX
c8SMO6QQ0qoL0SkvYHSlx040/Puovs+g5K1QCpj/4W1CyuyrNpa+rj30URpFo+53
F8eSRezsRO/CMMW0h5+bdcF36qBEvxkVU1U0jAMoFjH0OXfMDrbHjW3AE7csW0BW
FX9d0EA8/YWLErl+vXtsZpchQg0OH8GySxVjTw+/w0+Nu3DRcGoY/Ttgk8Zz6oi6
VmRWGUy1eihR/gipR7Rsqpdo626Kwhcx4/QRWrgvf6/QB48eiYfzPFIjSVKcBywe
vk/G3JKrVegoRcYjA+DX8M8NExeXq6k1x/XUFssXkgAlPk/DmNdZqn9UF85F6lzc
6SJFPjMxn/PIiMYNY6fpu5h3OnzH/jnD+UcnIVJ/txvNHaqueqY=
=r77U
-----END PGP SIGNATURE-----
--- End Message ---
