mdadm monitor feature broken, email notification not set up, nor using beep/wall/notify-send

manual workaround: install esmtp and procmail (and configure procmail as local delivery agent, see /usr/share/doc/esmtp)

explicit workaround commands using esmtp:

#apt-get install esmtp procmail
#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\'

last line needs to address for esmtprc of course:

#echo mda=\'/usr/bin/formail -a \"Date: \`date -R\`\" \| /usr/bin/procmail -d %T\' >> /etc/esmtprc

On the other hand mdadm "recommends" postfix | mail-transport-agent.

So a synaptic install (not the initial install) seems to pull in postfix on Desktops!

Bug #379882

I've been trying to get something usable at least using notify-send as an external program to trigger, but I'm having trouble getting it to execute on failure, and I got sick of unplugging a hard drive and then waiting for the entire array to rebuild. If I can figure out how to get it working, maybe I could come up with a new default mdadm config file with external program notification.

However, that runs into another bug- Ubuntu's default notifier applet ignores the timeout parameter from notify-send, so there's no way to ensure the message stays on the screen for a while without popping up a dialog box with an OK button or something. I like a notification bubble better than a dialog box, but I think obviously the user should have to click that the message was read... which is no longer an option- Ubuntu notification bubbles aren't allowed to have buttons, nor can you specify the amount of time they're displayed for (this regression has been declared as by design).

Sooo something other than notify-send will probably be necessary. I just don't know what other options there are.

I don't like the local mail option since Ubuntu doesn't normally even have the concept of it. All of my mail is webmail, so I wouldn't want a mail client running just to see if I have a drive failure- doesn't make much sense to me.

> I got sick of unplugging a hard drive and then waiting for the entire array to rebuild.

Maybe try mdadm's --monitor --test option to generate test messages.

(Or have your arrays --grow a bitmaps to speed up resync.)

An email is essential, but something like the red crash report icon in the notification area would be very useful. If Openoffice crashing warrants a notification area icon, then my entire RAID array failing surely warrants something as well.

Hello,

this bug is confirmed, but I don't see anywhere that has been fixed.

My apologies if I don't know how to read launchpad. :(

Does it mean it is still existing 18 months after?

thank you!