Re: changes to cron
On Tue, Sep 7, 2010 at 10:13 PM, Rick Pasotto <rick@niof.net> wrote:
> I updated many packages yesterday, including cron. Now I'm getting
> messages like this from logcheck:
>
> Sep 7 15:20:03 niof /USR/SBIN/CRON[20375]: (CRON) error (grandchild #20376 failed with exit status 1)
> Sep 7 15:23:01 niof /USR/SBIN/CRON[20492]: (CRON) error (grandchild #20493 failed with exit status 1)
> Sep 7 15:24:01 niof /USR/SBIN/CRON[20533]: (CRON) error (grandchild #20538 failed with exit status 1)
> Sep 7 15:24:02 niof /USR/SBIN/CRON[20532]: (CRON) error (grandchild #20540 failed with exit status 1)
> Sep 7 15:24:02 niof /USR/SBIN/CRON[20534]: (CRON) error (grandchild #20539 failed with exit status 1)
> Sep 7 15:24:02 niof /USR/SBIN/CRON[20535]: (CRON) error (grandchild #20537 failed with exit status 1)
> Sep 7 15:24:02 niof /USR/SBIN/CRON[20536]: (CRON) error (grandchild #20541 failed with exit status 1)
> Sep 7 15:30:03 niof /USR/SBIN/CRON[20922]: (CRON) error (grandchild #20923 failed with exit status 1)
>
> I have no idea what these error messages are trying to tell me. Is there
> something wrong with my crontab?
Cron settings changed [1], as a result, those commands launched by
cron that fail (and are logged in syslog) or print information to
standard output are sending mails
So go to see which scripts fails from cron entries and fix them to
return 0 (when they do their work) if you don't want this message
Regards,
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581612
Reply to: