All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ram Ramesh <rramesh2400@gmail.com>
To: Leslie Rhorer <lesrhorer@att.net>,
	Brad Campbell <lists2009@fnarfbargle.com>,
	linux-raid@vger.kernel.org
Subject: Re: checkarray not running or emailing
Date: Wed, 11 Mar 2020 23:53:49 -0500	[thread overview]
Message-ID: <f4d8ab8d-90cb-e9d0-3b15-ceab881dfcc1@gmail.com> (raw)
In-Reply-To: <7ba840ec-74fd-96bf-5088-7f8479ddcba5@att.net>

This may be a silly question, but is email working in your system?

I run debian, but a different version. Cron only sends me a message when 
something is wrong. I mean if checkarray failed, I get a message. If my 
array is degraded, I get a message. If everything is fine, no message. 
May be that is the standard. I am not the authority, but that is what is 
happening in my system.

I believe cron emails stdout+stderr of the command run. May be 
checkarray does not output anything in a successful run and therefore no 
email.

It is best to also query debian.user email: debian-user@lists.debian.org

Ramesh

On 3/11/20 8:41 PM, 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?"
>
> On 3/11/2020 7:50 AM, Brad Campbell wrote:
>> On 11/3/20 09:11, Leslie Rhorer wrote:
>>>      Is there seriously no one here who knows how checkarray was 
>>> launched in previous versions?
>>>
>>> On 3/1/2020 3:03 PM, Leslie Rhorer wrote:
>>>>     I have upgraded 2 of my servers to Debian Buster, and now 
>>>> neither one seems to be running checkarray automatically.  In 
>>>> addition, when I run checkarray manually, it isn't sending update 
>>>> emails on the status of the job.  Actually, I have never been able 
>>>> to figure out how checkarray runs.  One my older servers, there 
>>>> doesn't seem to be anything in /etc/crontab, /etc/cron.monthly, 
>>>> /etc/init.d/, /etc/mdadm/mdadm.conf, or /lib/systemd/system/ that 
>>>> would run checkarray.
>>>
>>
>> On mine it's in /etc/cron.d/mdadm
>>
>> brad@srv:/etc/cron.d$ cat mdadm
>> #
>> # cron.d/mdadm -- schedules periodic redundancy checks of MD devices
>> #
>> # Copyright © martin f. krafft <madduck@madduck.net>
>> # distributed under the terms of the Artistic Licence 2.0
>> #
>>
>> # By default, run at 00:57 on every Sunday, but do nothing unless the 
>> day of
>> # the month is less than or equal to 7. Thus, only run on the first 
>> Sunday of
>> # each month. crontab(5) sucks, unfortunately, in this regard; 
>> therefore this
>> # hack (see #380425).
>> 57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date 
>> +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle 
>> --quiet; fi
>>
>> dpkg -L mdadm gave me a list of files and I just checked the cron 
>> entries.
>>
>> I don't run anything that recent, but Debian is Debian.
>>
>> Brad

  reply	other threads:[~2020-03-12  4:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <814aad65-fba3-334c-c4df-6b8f4bfc4193.ref@att.net>
2020-03-01 21:03 ` checkarray not running or emailing Leslie Rhorer
2020-03-11  1:11   ` Leslie Rhorer
2020-03-11 12:17     ` Wols Lists
2020-03-12  1:17       ` Leslie Rhorer
2020-03-11 12:50     ` Brad Campbell
2020-03-12  1:41       ` Leslie Rhorer
2020-03-12  4:53         ` Ram Ramesh [this message]
2020-03-13  0:24           ` Leslie Rhorer
2020-03-12  9:17         ` Brad Campbell
2020-03-13  0:13           ` Leslie Rhorer
2020-03-13 16:53             ` Brad Campbell
2020-03-15 11:11               ` Leslie Rhorer
2020-03-11 13:18     ` Robin Hill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f4d8ab8d-90cb-e9d0-3b15-ceab881dfcc1@gmail.com \
    --to=rramesh2400@gmail.com \
    --cc=lesrhorer@att.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.