Description of problem:
I get messages like these in the mdadm section of my nightly logwatch mail.
mdadm: cannot open /dev/md/1: No such file or directory
Now I've got around to investigate what actually is wrong. It seems to be the use of the "mdadm" command in the services/mdadm script. In the absence of any /etc/mdadm.conf file, it uses the command "mdadm --examine --scan" to find all devices. But it ought to use "mdadm --detail --scan" instead.
I sent a (slightly longer) report about this upstreams, see http://sourceforge.net/p/logwatch/mailman/message/32679812/ As you can see in the reply, this is something upstreams agrees on, and already have implemented.
Since releases of logwatch aren't very frequent, would it be possible to backport this fix in the Fedora package for the time being? It's a rather trivial fix, after all.
This was fixed by the upstream revision 180. I'll sync logwatch in F20 with the one in F21/rawhide, which is currently from revision 198.
logwatch-7.4.0-33.20140704svn198.fc20 has been submitted as an update for Fedora 20.
Sounds good, thanks!
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing logwatch-7.4.0-33.20140704svn198.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
logwatch-7.4.0-33.20140704svn198.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Fix mdadm logwatch script ...
Change all the occurences of /etc/mdadm.conf with /etc/mdadm/mdadm.conf
Run and test logwatch after.
Or make a symlink from /etc/mdadm/mdadm.conf to /etc/mdadm.conf