Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222600 > unrolled thread

Re: cron problem

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: cron problem ghe <ghe@slsware.net> - 2020-05-17 19:30 +0200
    Re: cron problem David Wright <deblis@lionunicorn.co.uk> - 2020-05-17 20:10 +0200
    Re: cron problem Greg Wooledge <wooledg@eeg.ccf.org> - 2020-05-18 13:40 +0200

#222600 — Re: cron problem

On 5/17/20 10:42 AM, ghe wrote:
> Buster, Supermicro desktop
> 
> Cron jobs (some of them) don't show up in root's email.
> 
> I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze cron 
> results show up fine; Buster's don't. I've reinstalled the Buster jobs. 
> I've copyNpasted them from the Squeeze crontab. Both logwatch results 
> show up (part of /etc/crop.daily). It seems that that the jobs I enter 
> manually don't show up. They didn't use to do that.
> 
> 
> Here's my crontab on Buster:
> 
> root@sbox:~# cat /var/spool/cron/crontabs/root
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.93Jh1O/crontab installed on Sun May 17 10:11:58 2020)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 5 1 * * * /bin/cat /proc/mdstat
> 10 1 * * * test -x /usr/sbin/apticron && /usr/sbin/apticron --cron 
> #apticron
> 
> (The date is a few minutes ago because I removed a dup of logwatch.)
> 
> 
> And on Squeeze:
> 
> root@rrserv:~# cat /var/spool/cron/crontabs/root
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.bgZABv/crontab installed on Wed May 13 12:48:16 2020)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 2 1 * * * /bin/cat /proc/mdstat
> 
> 
> Here's what happens if I manually run one of them (Buster):
> 
> root@sbox:# /bin/cat /proc/mdstat
> Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] 
> [raid4] [raid10]
> md0 : active raid1 sdc1[1] sda1[0]
>        488253440 blocks super 1.2 [2/2] [UU]
>        bitmap: 0/4 pages [0KB], 65536KB chunk
> 
> unused devices: <none>
> 
> 
> I have a feeling that I've done something trivially wrong. But I can't 
> find it. Thoughts?
> 


-- 
Glenn English

[toc] | [next] | [standalone]

#222602

On Sun 17 May 2020 at 11:21:11 (-0600), ghe wrote:
> On 5/17/20 10:42 AM, ghe wrote:
> > Buster, Supermicro desktop
> > 
> > Cron jobs (some of them) don't show up in root's email.
> > 
> > I admin 2 domains -- one on Squeeze, one on Buster. My Squeeze
> > cron results show up fine; Buster's don't. I've reinstalled the
> > Buster jobs. I've copyNpasted them from the Squeeze crontab. Both
> > logwatch results show up (part of /etc/crop.daily). It seems that
> > that the jobs I enter manually don't show up. They didn't use to
> > do that.
> > 
> > 
> > Here's my crontab on Buster:
> > 
> > root@sbox:~# cat /var/spool/cron/crontabs/root
> > # DO NOT EDIT THIS FILE - edit the master and reinstall.
> > # (/tmp/crontab.93Jh1O/crontab installed on Sun May 17 10:11:58 2020)
> > # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> > 5 1 * * * /bin/cat /proc/mdstat
> > 10 1 * * * test -x /usr/sbin/apticron && /usr/sbin/apticron --cron
> > #apticron
> > 
> > (The date is a few minutes ago because I removed a dup of logwatch.)
> > 
> > 
> > And on Squeeze:
> > 
> > root@rrserv:~# cat /var/spool/cron/crontabs/root
> > # DO NOT EDIT THIS FILE - edit the master and reinstall.
> > # (/tmp/crontab.bgZABv/crontab installed on Wed May 13 12:48:16 2020)
> > # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> > 2 1 * * * /bin/cat /proc/mdstat
> > 
> > 
> > Here's what happens if I manually run one of them (Buster):
> > 
> > root@sbox:# /bin/cat /proc/mdstat
> > Personalities : [raid1] [linear] [multipath] [raid0] [raid6]
> > [raid5] [raid4] [raid10]
> > md0 : active raid1 sdc1[1] sda1[0]
> >        488253440 blocks super 1.2 [2/2] [UU]
> >        bitmap: 0/4 pages [0KB], 65536KB chunk
> > 
> > unused devices: <none>
> > 
> > 
> > I have a feeling that I've done something trivially wrong. But I
> > can't find it. Thoughts?

I always examine my cron with

    crontab -l

rather than just catting some random file.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222614

On Sun, May 17, 2020 at 11:21:11AM -0600, ghe wrote:
> > Cron jobs (some of them) don't show up in root's email.

Which MTA are you using, and how did you configure its behavior for
mail addressed to "root"?

Some MTAs will deliver literally to root's inbox (/var/mail/root or
some other place).  Others will refuse to deliver to root, and will
insist that you alias root to an unprivileged user.

It's extremely possible that you've already aliased root to some other
user, and have forgotten that you did this.  Thus, you're looking in
the wrong place.

What happens if you run "echo test | mailx root"?  Where does the mail
go in that case?  Mail from cron follows an almost identical delivery
path, so you can use this to test the basic MTA functionality before
bringing cron into the picture.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web