public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Odd cron errors
Date: Tue, 01 Jul 2014 15:01:33 +0100	[thread overview]
Message-ID: <1723749.tmeyHiYkSl@wstn> (raw)
In-Reply-To: <201407011213.58389.michaelkintzios@gmail.com>

On Tuesday 01 July 2014 12:13:39 Mick wrote:
> On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote:
> > Hell list,
> > 
> > I don't know when it started, but recently I've been getting error e-mails
> > from cron, thus:
> > 
> > Password: 501 Not authorised --- Reply not authenticated
> > 
> > They're all timed at 03:10:0x, i.e. one minute after cron.daily tasks are
> > run, and they occur at 7- or 8-day intervals. The only files in
> > /etc/cron.daily are logrotate and man-db, neither of which I've touched.
> > 
> > I've been expiring that e-mail folder at 30 days, so I have only four
> > instances - I've now set the lifetime to 366 days to allow a history to
> > build up.
> > 
> > Anyone have a clue to this? It's hardly earth-shattering, but it might be
> > good to find out what's going on.
> 
> Only to confirm that I have been getting these on an old 32bit laptop.  I
> suspect that they are caused by chrony which I run on this PC and some
> passwd setup that chronyc requires to connect to the timeservers and update
> RTC et al, via chronyd.  I have not looked into configuring it beyond a
> rather superficial "it'll do for now" level and have not yet added any
> chrony.keys. When I get a moment I will revisit the configuration to add
> the required key, but will need to spend some time going through the man
> pages first.

I was beginning to think I was the only one still running chrony :)

My chrony does have a key set up, so I don't think that's the cause. Now that 
you remind me, I changed the setup on 31/5. The Atom LAN server has an 
appalling hardware clock, so I changed things around so that both the Atom and 
this box synchronise over the Internet, and they peer with each other.

Maybe I should split them apart to make them independent. I'll watch them for 
a while first though, to see if a pattern emerges.

Thanks for the idea Mick.

-- 
Regards
Peter



  reply	other threads:[~2014-07-01 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  9:48 [gentoo-user] Odd cron errors Peter Humphrey
2014-07-01 10:57 ` Alan McKinnon
2014-07-01 13:12   ` Dale
2014-07-01 13:52   ` Peter Humphrey
2014-07-01 11:13 ` Mick
2014-07-01 14:01   ` Peter Humphrey [this message]
2014-07-13  9:20     ` Peter Humphrey
2014-07-13 10:15       ` Mick
2014-07-13 15:42         ` Dale
2014-07-13 15:54           ` Dale
2014-07-13 16:30             ` Mick
2014-07-13 20:08               ` Peter Humphrey

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=1723749.tmeyHiYkSl@wstn \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox