[arch-general] mdmonitor.service /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory
New server, 2 1T drives in RAID1, with mdraid, I have an error during boot for mdmonitor: Jun 05 17:12:47 valhalla systemd[454]: mdmonitor.service: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory I've run into this before with mdadm, last time was due to not having MAILADDR configured in /etc/mdadm.conf (that is not the case now) # cat /etc/mdadm.conf DEVICE partitions ARRAY /dev/md0 metadata=1.2 name=archiso:0 UUID=1b67f2d4:4911f2c5:469f9dcf:315814ce ARRAY /dev/md1 metadata=1.2 name=archiso:1 UUID=0542c5c9:3802b256:32e97884:a2e49f53 ARRAY /dev/md2 metadata=1.2 name=archiso:2 UUID=812e8f85:0c4efbef:a0c02f49:215df35e ARRAY /dev/md3 metadata=1.2 name=archiso:3 UUID=80a3bf76:e6421b06:6edb2a88:741e8b6f MAILADDR david@mydomain.com PROGRAM /usr/sbin/handle-mdadm-events The problem very simply looks to be no /usr/lib/systemd/scripts/mdadm_env.sh wanted by mdmonitor.service, e.g. # cat /usr/lib/systemd/system/mdmonitor.service # This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. [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 There is no /usr/lib/systemd/scripts/mdadm_env.sh in the current mdadm package. Is this a bug (which I'm happy to file), or me being stupid? (go easy if the latter) -- David C. Rankin, J.D.,P.E.
On 06/05/2016 06:28 PM, David C. Rankin wrote:
New server, 2 1T drives in RAID1, with mdraid, I have an error during boot for mdmonitor:
Jun 05 17:12:47 valhalla systemd[454]: mdmonitor.service: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory
I've run into this before with mdadm, last time was due to not having MAILADDR configured in /etc/mdadm.conf (that is not the case now)
# cat /etc/mdadm.conf DEVICE partitions ARRAY /dev/md0 metadata=1.2 name=archiso:0 UUID=1b67f2d4:4911f2c5:469f9dcf:315814ce ARRAY /dev/md1 metadata=1.2 name=archiso:1 UUID=0542c5c9:3802b256:32e97884:a2e49f53 ARRAY /dev/md2 metadata=1.2 name=archiso:2 UUID=812e8f85:0c4efbef:a0c02f49:215df35e ARRAY /dev/md3 metadata=1.2 name=archiso:3 UUID=80a3bf76:e6421b06:6edb2a88:741e8b6f MAILADDR david@mydomain.com PROGRAM /usr/sbin/handle-mdadm-events
The problem very simply looks to be no /usr/lib/systemd/scripts/mdadm_env.sh wanted by mdmonitor.service, e.g.
# cat /usr/lib/systemd/system/mdmonitor.service
# This file is part of mdadm. # # mdadm is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version.
[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
There is no /usr/lib/systemd/scripts/mdadm_env.sh in the current mdadm package. Is this a bug (which I'm happy to file), or me being stupid? (go easy if the latter)
I don't think it's any problem at all. I've always had this message and mdadm starts and runs fine. I think this has been discussed on the list before. It's an optional file, but generates an ugly message. https://bbs.archlinux.org/viewtopic.php?id=183122 (#10) HTH, Dave
On 06/05/2016 06:12 PM, David N Murray via arch-general wrote:
I don't think it's any problem at all. I've always had this message and mdadm starts and runs fine. I think this has been discussed on the list before. It's an optional file, but generates an ugly message.
https://bbs.archlinux.org/viewtopic.php?id=183122 (#10)
HTH, Dave
Thank you Dave, It does indeed run fine: [17:21 valhalla:/home/david] # sc status mdmonitor ● mdmonitor.service - MD array monitor Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static; vendor preset: disabled) Active: active (running) since Sun 2016-06-05 17:12:47 CDT; 23min ago Process: 454 ExecStartPre=/usr/lib/systemd/scripts/mdadm_env.sh (code=exited, status=203/EXEC) Main PID: 460 (mdadm) Tasks: 1 (limit: 512) CGroup: /system.slice/mdmonitor.service └─460 /sbin/mdadm --monitor --scan Jun 05 17:12:47 valhalla systemd[1]: Starting MD array monitor... Jun 05 17:12:47 valhalla systemd[1]: Started MD array monitor. Just seems strange we wouldn't at least have a stub script for /usr/lib/systemd/scripts/mdadm_env.sh to get rid of the boot message. Oh well, I'll post to the mdraid list and see what the devs have to say. Thanks again -- David C. Rankin, J.D.,P.E.
On 06/05/2016 07:43 PM, David C. Rankin wrote:
On 06/05/2016 06:12 PM, David N Murray via arch-general wrote:
I don't think it's any problem at all. I've always had this message and mdadm starts and runs fine. I think this has been discussed on the list before. It's an optional file, but generates an ugly message.
https://bbs.archlinux.org/viewtopic.php?id=183122 (#10)
HTH, Dave
Thank you Dave,
It does indeed run fine:
[17:21 valhalla:/home/david] # sc status mdmonitor ● mdmonitor.service - MD array monitor Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static; vendor preset: disabled) Active: active (running) since Sun 2016-06-05 17:12:47 CDT; 23min ago Process: 454 ExecStartPre=/usr/lib/systemd/scripts/mdadm_env.sh (code=exited, status=203/EXEC) Main PID: 460 (mdadm) Tasks: 1 (limit: 512) CGroup: /system.slice/mdmonitor.service └─460 /sbin/mdadm --monitor --scan
Jun 05 17:12:47 valhalla systemd[1]: Starting MD array monitor... Jun 05 17:12:47 valhalla systemd[1]: Started MD array monitor.
Just seems strange we wouldn't at least have a stub script for /usr/lib/systemd/scripts/mdadm_env.sh to get rid of the boot message. Oh well, I'll post to the mdraid list and see what the devs have to say. Thanks again
Now we have a conundrum, the mdadm folks seem to think the missing file is an Arch problem: (from linux-raid@vger.kernel.org, contributing redhat dev): On 06/07/2016 02:31 PM, Jes Sorensen wrote:
"David C. Rankin" <drankinatty@suddenlinkmail.com> writes:
Neil, All,
I'm chasing down the reason there is no /usr/lib/systemd/scripts/mdadm_env.sh provided with mdadm. This is more a curiosity really as mdmonitor continues to run, but it always throws an error at boot:
Jun 05 17:12:47 valhalla systemd[454]: mdmonitor.service: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory
I have several Arch servers, all on mdadm 3.4-1. I ran into an issue a year or so ago with a boot error with mdmonitor due to my failure to provide MAILADDR in /etc/mdadm.com, but that has long since been corrected:
If you're running Arch Linux, you probably want to direct this question to the Arch Linux maintainers.
Jes
So is this something that needs to be filed as a bug here. The package is certainly missing something. The mdmonitor.service file is pointing to a file that does not exist in the package. What say the Arch devs? -- David C. Rankin, J.D.,P.E.
Hi David, On 06/09/2016 12:05 AM, David C. Rankin wrote:
Now we have a conundrum, the mdadm folks seem to think the missing file is an Arch problem:
(from linux-raid@vger.kernel.org, contributing redhat dev):
On 06/07/2016 02:31 PM, Jes Sorensen wrote:
"David C. Rankin" <drankinatty@suddenlinkmail.com> writes:
Neil, All,
I'm chasing down the reason there is no /usr/lib/systemd/scripts/mdadm_env.sh provided with mdadm. This is more a curiosity really as mdmonitor continues to run, but it always throws an error at boot:
Jun 05 17:12:47 valhalla systemd[454]: mdmonitor.service: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory
I have several Arch servers, all on mdadm 3.4-1. I ran into an issue a year or so ago with a boot error with mdmonitor due to my failure to provide MAILADDR in /etc/mdadm.com, but that has long since been corrected:
If you're running Arch Linux, you probably want to direct this question to the Arch Linux maintainers.
Jes
So is this something that needs to be filed as a bug here. The package is certainly missing something. The mdmonitor.service file is pointing to a file that does not exist in the package. What say the Arch devs?
That's a weird, since mdadm_env.sh only gets installed on SUSE systems. See the following line from the Makefile (line 316): if [ -f /etc/SuSE-release -o -n "$(SUSE)" ]; then $(INSTALL) -D -m 755 systemd/SUSE-mdadm_env.sh \ $(DESTDIR)$(SYSTEMD_DIR)/../scripts/mdadm_env.sh fi http://git.neil.brown.name/?p=mdadm.git;a=blob;f=Makefile;h=5fd7f166e7e14f24... Originating commit: http://git.neil.brown.name/?p=mdadm.git;a=commitdiff;h=61c094715836e76b66d7a... Also, personally I've never seen /usr/lib/systemd/scripts used on Arch. I don't think that's an official (as in used by systemd upstream) directory (though I'm not sure). Cheers, Wilhelm Schuster.
On 06/08/2016 05:22 PM, Wilhelm Schuster wrote:
That's a weird, since mdadm_env.sh only gets installed on SUSE systems. See the following line from the Makefile (line 316):
if [ -f /etc/SuSE-release -o -n "$(SUSE)" ]; then $(INSTALL) -D -m 755 systemd/SUSE-mdadm_env.sh \ $(DESTDIR)$(SYSTEMD_DIR)/../scripts/mdadm_env.sh fi
http://git.neil.brown.name/?p=mdadm.git;a=blob;f=Makefile;h=5fd7f166e7e14f24...
Originating commit: http://git.neil.brown.name/?p=mdadm.git;a=commitdiff;h=61c094715836e76b66d7a...
Also, personally I've never seen /usr/lib/systemd/scripts used on Arch. I don't think that's an official (as in used by systemd upstream) directory (though I'm not sure).
Yes, this is strange. It seems like the PKGBUILD should take into consideration that there will be no mdadm_env.sh installed on Arch and tweak the mdmonitor.service file accordingly with sed or the like to either eliminate the EXEC attempt to run the script, or at least install an empty "stub" mdadm_env.sh that does nothing but eliminates the boot error. I'll leave it up to the masterminds here. If this is an issue that needs a bug filed, let me know, I'm happy to file it. -- David C. Rankin, J.D.,P.E.
Smells like EPROBLEM. If there's no problem beyond logspam, you'll have a hard time to get the improvement accepted. Question though, now that you made me curious, do you patch out gtk debug messages for your GUI apps? cheers! mar77i
On 06/08/2016 05:41 PM, Martin Kühne via arch-general wrote:
Smells like EPROBLEM. If there's no problem beyond logspam, you'll have a hard time to get the improvement accepted. Question though, now that you made me curious, do you patch out gtk debug messages for your GUI apps?
Point well taken -- that's the last you'll hear of this issue from me... -- David C. Rankin, J.D.,P.E.
participants (4)
-
David C. Rankin
-
David N Murray
-
Martin Kühne
-
Wilhelm Schuster