All,
I'm not sure if this is a config issue or bug. I have 2 servers with
mdadm/mdraid arrays. In both a check of 'systemctl --type=service' shows
mdmonitor has failed. It fails to start each time:
● mdmonitor.service - MD array monitor
Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static; vendor
preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-08-22 22:33:52 CDT; 7h ago
Process: 377 ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS
(code=exited, status=1/FAILURE)
Process: 375 ExecStartPre=/usr/lib/systemd/scripts/mdadm_env.sh (code=exited,
status=203/EXEC)
Main PID: 377 (code=exited, status=1/FAILURE)
Looking at the service file I'm not sure if there is an issue here, or
somewhere else, but there is no file 'mdadm_env.sh' that is reference by
ExecStartPre=:
# This file is part of mdadm.
#
<snip>
[Unit]
Description=MD array monitor
DefaultDependencies=no
[Service]
Environment= MDADM_MONITOR_ARGS=--scan
EnvironmentFile=-/run/sysconfig/mdadm
ExecStartPre=-/usr/lib/systemd/scripts/mdadm_env.sh
ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS
Is this a bug?
--
David C. Rankin, J.D.,P.E.
