-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello,
Am Mo den 3. Jun 2013 um 20:41 schrieb Willi Mann: > Could anyone please look at this bug report? It seems to me that the > mdadm script could handle this situation more gracefully and the > location of the mdadm.conf file is not the same as on the system the > script was developed on. Please take a look at the full bug log at > > http://bugs.debian.org/710867 Brrr, a web site... Am Mo den 3. Jun 2013 um 13:18 schrieb Chris: > the older debian logwatch packages doesn't include a mdadm service script so > you've probably used the one from upstream or a 3rd party? No, I used the one from logwatch. But I checked again and saw that I was wrong (a bit). The script was never failing as it was not there in old versions. :-D However, in the new package this script is there and is broken. > an mdadm service script was added which is checking the: > > /etc/mdadm.conf > > on line 34 in /usr/share/logwatch/scripts/services/mdadm > > On my debian wheezy system this file is placed in: > > /etc/mdadm/mdadm.conf > > so try to change the mentioned line above and see if this helps. The correct location for mdadm.conf is the second one, /etc/mdadm/mdadm.conf. At least on debian systems. Am Mo den 3. Jun 2013 um 13:35 schrieb Chris: > So probably one of the above outputs a wrong list of devices. ~> cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE /dev/hd[a-d][1-9] /dev/sd[a-b][1-9] # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes metadata=1.0 # automatically tag new arrays as belonging to the local system #HOMEHOST <system> # instruct the monitoring daemon where to send mail alerts MAILADDR [email protected] # definitions of existing MD arrays ARRAY /dev/md0 UUID=6e61a0dd:d722ad7f:00a0395f:7c490649 ARRAY /dev/md1 metadata=1.0 level=raid1 num-devices=2 UUID=727a8cdb:08ecb6ab:c53a0793:fa9c837f ARRAY /dev/md2 metadata=1.0 level=raid1 num-devices=2 UUID=c14fa070:a86978f3:1b194f3f:e1fced7e #ARRAY /dev/md3 metadata=1.0 level=raid1 num-devices=2 UUID=c39b2023:014d416d:a4e6fa0c:b1ad4ee8 #ARRAY /dev/md4 metadata=1.0 level=raid1 num-devices=2 UUID=956a3a8a:ec9db273:ab9785e6:19e0bb1a ARRAY /dev/md5 metadata=1.0 level=raid1 num-devices=2 UUID=697d7105:10a4abcc:0bf6e153:662f8b4e ~> mdadm --examine --scan ARRAY /dev/md0 UUID=6e61a0dd:d722ad7f:00a0395f:7c490649 ARRAY /dev/md/1 metadata=1.0 UUID=727a8cdb:08ecb6ab:c53a0793:fa9c837f name=ikki.ket:1 ARRAY /dev/md/2 metadata=1.0 UUID=c14fa070:a86978f3:1b194f3f:e1fced7e name=ikki.ket:2 ARRAY /dev/md/5 metadata=1.0 UUID=697d7105:10a4abcc:0bf6e153:662f8b4e name=ikki:5 So, fixing the config file location in the script should solve the bug. Gruß Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <[email protected]> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQGcBAEBCgAGBQJRrRnUAAoJEKZ8CrGAGfasjAQL/jbdEqvn5ns2ubMlJmCPiwsJ PvBxxzRYjOIXgNFLKBUv+mLh+hGDqA4DVR8qg2JlQW1wU/J/RiNntAIpmgbH8O7o px6xDPdjcmGxWU3WDzoDPBMC27Kv9S/rA1dtwZt95gTPopFCnNOS45UlWBcBgyYr Xc2n+6TGL93mQ1kwpzoIMXdHElsNzjYaXI5L7r3NBQ+6yKFw8nRMYWEukU1or4jA kRnEuj5Gz3KeCxpy4E6akPuuDeAfuvsmWKQBhG8uCj6TA+RbE+0T1AFqIdSe9ipm IQURp6fM2mDhCtS7PEPQZ04tsG+tQIgebbOeUnQU1n0E4F6IMSs8i4AZG2V8d79K X7jqq1cEMEtp4Fq1PJYom251JdP6rziekrfUAZ867LFTGfG+ydwu2BS7+/9G9XOl VX/mxEvfnd4Z0OCTRoKysOvbqOGkzAMLcQgqcBPX7KcmcBV06bxMy0dwylAkhRUL 2Oja2pw8jxgQdgZYA/zxDASmk7NlffEXOd1Aqn15ww== =Zy1m -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
