From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AF3F41392EF for ; Tue, 1 Jul 2014 14:01:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E996AE0B0E; Tue, 1 Jul 2014 14:01:35 +0000 (UTC) Received: from smarthost01c.mail.zen.net.uk (smarthost01c.mail.zen.net.uk [212.23.1.5]) by pigeon.gentoo.org (Postfix) with ESMTP id ECC24E0AB9 for ; Tue, 1 Jul 2014 14:01:34 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01c.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X1yco-000FKn-4M for gentoo-user@lists.gentoo.org; Tue, 01 Jul 2014 14:01:34 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Odd cron errors Date: Tue, 01 Jul 2014 15:01:33 +0100 Message-ID: <1723749.tmeyHiYkSl@wstn> Organization: at home User-Agent: KMail/4.12.5 (Linux/3.12.21-gentoo-r1; KDE/4.12.5; x86_64; ; ) In-Reply-To: <201407011213.58389.michaelkintzios@gmail.com> References: <280844506.WEGFKYD1Ij@wstn> <201407011213.58389.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01c-IP: [82.69.80.10] X-Archives-Salt: e852bba7-e219-4ddd-a6c4-d70392f91331 X-Archives-Hash: e5e061f19ffc9d496f3c1c2ca2d03bfb 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