1 |
On Sunday 13 Jul 2014 10:20:47 Peter Humphrey wrote: |
2 |
> On Tuesday 01 July 2014 15:01:33 I wrote: |
3 |
> > On Tuesday 01 July 2014 12:13:39 Mick wrote: |
4 |
> > > On Tuesday 01 Jul 2014 10:48:12 Peter Humphrey wrote: |
5 |
> > > > Hell list, |
6 |
> > > > |
7 |
> > > > I don't know when it started, but recently I've been getting error |
8 |
> > > > e-mails |
9 |
> > > > from cron, thus: |
10 |
> > > > |
11 |
> > > > Password: 501 Not authorised --- Reply not authenticated |
12 |
> > > > |
13 |
> > > > They're all timed at 03:10:0x, i.e. one minute after cron.daily tasks |
14 |
> > > > are |
15 |
> > > > run, and they occur at 7- or 8-day intervals. The only files in |
16 |
> > > > /etc/cron.daily are logrotate and man-db, neither of which I've |
17 |
> > > > touched. |
18 |
> > > > |
19 |
> > > > I've been expiring that e-mail folder at 30 days, so I have only four |
20 |
> > > > instances - I've now set the lifetime to 366 days to allow a history |
21 |
> > > > to build up. |
22 |
> > > > |
23 |
> > > > Anyone have a clue to this? It's hardly earth-shattering, but it |
24 |
> > > > might be |
25 |
> > > > good to find out what's going on. |
26 |
> > > |
27 |
> > > Only to confirm that I have been getting these on an old 32bit laptop. |
28 |
> > > I suspect that they are caused by chrony which I run on this PC and |
29 |
> > > some passwd setup that chronyc requires to connect to the timeservers |
30 |
> > > and update |
31 |
> > > RTC et al, via chronyd. I have not looked into configuring it beyond a |
32 |
> > > rather superficial "it'll do for now" level and have not yet added any |
33 |
> > > chrony.keys. When I get a moment I will revisit the configuration to |
34 |
> > > add the required key, but will need to spend some time going through |
35 |
> > > the man pages first. |
36 |
> > |
37 |
> > I was beginning to think I was the only one still running chrony :) |
38 |
> > |
39 |
> > My chrony does have a key set up, so I don't think that's the cause. Now |
40 |
> > that you remind me, I changed the setup on 31/5. The Atom LAN server has |
41 |
> > an appalling hardware clock, so I changed things around so that both the |
42 |
> > Atom and this box synchronise over the Internet, and they peer with each |
43 |
> > other. |
44 |
> > |
45 |
> > Maybe I should split them apart to make them independent. I'll watch them |
46 |
> > for a while first though, to see if a pattern emerges. |
47 |
> > |
48 |
> > Thanks for the idea Mick. |
49 |
> |
50 |
> Well, a week ago I did split the two chronys (the one on the server and the |
51 |
> one on the workstation), but I got another mail at 03:10:05 today. So I |
52 |
> guess that isn't it. |
53 |
|
54 |
Please try this: |
55 |
|
56 |
Go the PC that keeps getting these messages in its logs. Run: |
57 |
|
58 |
$ chrony |
59 |
|
60 |
chronyc> password |
61 |
password: <manually_enter_your_chrony_Passwd> |
62 |
|
63 |
If the passwd is wrong, or some characters are incompatible with the terminal, |
64 |
then you will get: |
65 |
|
66 |
"Password: 501 Not authorised --- Reply not authenticated" |
67 |
|
68 |
|
69 |
You can test this by entering the wrong passwd initially. Unfortunately, I no |
70 |
longer have the PC running chrony to test it here. |
71 |
|
72 |
-- |
73 |
Regards, |
74 |
Mick |