Re: checkarray not running or emailing

[Leslie Rhorer <lesrhorer@att.net>]

     Yes, that works just fine, as does the daily email alert whenever 
an array is degraded, but `checkarray --cron --all --idle` doesn't 
produce an email.  It starts the array verification on all the arrays, 
but no status on the processes are sent.

     The normal execution for the script is to submit `echo check >  
/sys/block/mdx/md/sync_action` and then exit.  Obviously, the rest of 
the processes are handled by the scheduler and mdadm. I'm not seeing how 
anything other than mdadm should be generating the status emails.

     So why does `mdadm --monitor --test --oneshot /dev/mdx` produce an 
email message when `echo check > /sys/block/mdx/md/sync_action` produces 
none?  The "new" servers are running mdadm v4.1 under Debian Buster.  
The "old" servers are running mdadm v3.3.2 under Debian Jessie.

On 3/12/2020 4:17 AM, Brad Campbell wrote:
>
> On 12/3/20 09:41, Leslie Rhorer wrote:
>>     Aha! There it is, on both the old and new systems, so it probably 
>> is running.  The question remains, "Why isn't it posting to email?"
>>
> root@srv:~# mdadm --monitor --test --oneshot /dev/md2
> mdadm: Monitor using email address "root" from config file
>
> And in the mail :
>
> This is an automatically generated mail message from mdadm
> running on srv
>
> A TestMessage event had been detected on md device /dev/md2.
>
> Faithfully yours, etc.
>
> P.S. The /proc/mdstat file currently contains the following:
>
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> md2 : active raid1 nvme0n1[2] md5[3](W)
>       952696320 blocks super 1.2 [2/2] [UU]
>       bitmap: 6/8 pages [24KB], 65536KB chunk
>
>
>
> Brad
>