[gentoo-user] Chrony-2.2 failing

[gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

Hello list,

Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems 
to run just fine on this amd64 box, but on my x86 Atom box it fails to start 
thus:

# /etc/init.d/chronyd start
 * Starting chronyd ...
 * start-stop-daemon: caught an interrupt
 * start-stop-daemon: /usr/sbin/chronyd died
 * Failed to start chronyd                                     [ !! ]
 * ERROR: chronyd failed to start

This is after adjusting the config files. Has anyone else stumbled into 
this?

What's more, earlier versions had a decent man page and heavily commented 
chronyd.conf, but now the chrony.conf man page has been cut to a bare 
minimum and instead refers to a file chrony.txt "included in the 
distribution". I cannot find any such file after running ebuild $(equery w 
chrony) prepare.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Alexander Kapshuk]

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

On Thu, Nov 19, 2015 at 12:49 PM, Peter Humphrey <peter@prh.myzen.co.uk>
wrote:

> Hello list,
>
> Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems
> to run just fine on this amd64 box, but on my x86 Atom box it fails to
> start
> thus:
>
> # /etc/init.d/chronyd start
>  * Starting chronyd ...
>  * start-stop-daemon: caught an interrupt
>  * start-stop-daemon: /usr/sbin/chronyd died
>  * Failed to start chronyd                                     [ !! ]
>  * ERROR: chronyd failed to start
>
> This is after adjusting the config files. Has anyone else stumbled into
> this?
>
> What's more, earlier versions had a decent man page and heavily commented
> chronyd.conf, but now the chrony.conf man page has been cut to a bare
> minimum and instead refers to a file chrony.txt "included in the
> distribution". I cannot find any such file after running ebuild $(equery w
> chrony) prepare.
>
> --
> Rgds
> Peter
>
>
>
'/usr/share/info/chrony.info.bz2' seems to offer more complete
documentation.

chrony2.2 seems to be running OK on my system:

uname -p
Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz

Here's the contents of my 'chrony.conf', if that is of any help.

grep '^[a-z]' /etc/chrony/chrony.conf
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
maxupdateskew 5
driftfile /var/lib/chrony/drift
keyfile /etc/chrony/chrony.keys
commandkey 1
generatecommandkey
makestep 1.0 3
logdir /var/log/chrony
log measurements statistics tracking
rtcsync

[-- Attachment #2: Type: text/html, Size: 2205 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[Alan McKinnon]

On 19/11/2015 12:49, Peter Humphrey wrote:
> Hello list,
> 
> Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems 
> to run just fine on this amd64 box, but on my x86 Atom box it fails to start 
> thus:
> 
> # /etc/init.d/chronyd start
>  * Starting chronyd ...
>  * start-stop-daemon: caught an interrupt
>  * start-stop-daemon: /usr/sbin/chronyd died
>  * Failed to start chronyd                                     [ !! ]
>  * ERROR: chronyd failed to start
> 
> This is after adjusting the config files. Has anyone else stumbled into 
> this?
> 
> What's more, earlier versions had a decent man page and heavily commented 
> chronyd.conf, but now the chrony.conf man page has been cut to a bare 
> minimum and instead refers to a file chrony.txt "included in the 
> distribution". I cannot find any such file after running ebuild $(equery w 
> chrony) prepare.
> 


Doe sit fail consistently? IOW, now that everything else has settled
down, does "/etc/init.d/chrony start" still fail?

What about logs?
If none, you can inspect the start-stop-daemon line in the init file,
get the command line it launches chrony with, and see what that prints
to the console.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Chrony-2.2 failing

[Marc Joliet]

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

On Thursday 19 November 2015 10:49:08 Peter Humphrey wrote:
>Hello list,
>
[...]
>
>What's more, earlier versions had a decent man page and heavily commented
>chronyd.conf, but now the chrony.conf man page has been cut to a bare
>minimum and instead refers to a file chrony.txt "included in the
>distribution". I cannot find any such file after running ebuild $(equery w
>chrony) prepare.

You've already gotten an answer regarding the man page, but with regards to 
the configuration file in /etc, it looks like what you are looking for is in 
the standard documentation path:

% qlist chrony | grep doc/
/usr/share/doc/chrony-2.2/README
/usr/share/doc/chrony-2.2/NEWS
/usr/share/doc/chrony-2.2/FAQ
/usr/share/doc/chrony-2.2/chrony.conf.example1
/usr/share/doc/chrony-2.2/chrony.conf.example2
/usr/share/doc/chrony-2.2/chrony.conf.example3
/usr/share/doc/chrony-2.2/chrony.keys.example

The *.example3 file is apparently the one that used to be copied to /etc.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Thursday 19 Nov 2015 22:15:33 Marc Joliet wrote:
> On Thursday 19 November 2015 10:49:08 Peter Humphrey wrote:
> >Hello list,
> 
> [...]
> 
> >What's more, earlier versions had a decent man page and heavily commented
> >chronyd.conf, but now the chrony.conf man page has been cut to a bare
> >minimum and instead refers to a file chrony.txt "included in the
> >distribution". I cannot find any such file after running ebuild $(equery
> >w chrony) prepare.
> 
> You've already gotten an answer regarding the man page, but with regards
> to the configuration file in /etc, it looks like what you are looking for
> is in the standard documentation path:
> 
> % qlist chrony | grep doc/
> /usr/share/doc/chrony-2.2/README
> /usr/share/doc/chrony-2.2/NEWS
> /usr/share/doc/chrony-2.2/FAQ
> /usr/share/doc/chrony-2.2/chrony.conf.example1
> /usr/share/doc/chrony-2.2/chrony.conf.example2
> /usr/share/doc/chrony-2.2/chrony.conf.example3
> /usr/share/doc/chrony-2.2/chrony.keys.example
> 
> The *.example3 file is apparently the one that used to be copied to /etc.
> 
> HTH

Thanks for the ideas, gents.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Thursday 19 Nov 2015 19:17:11 Alan McKinnon wrote:

> Does it fail consistently? IOW, now that everything else has settled
> down, does "/etc/init.d/chrony start" still fail?

Yes, it's a hard fault:

# /etc/init.d/chronyd start
 * Caching service dependencies ...                                 [ ok ]
 * Starting chronyd ...
 * start-stop-daemon: caught an interrupt
 * start-stop-daemon: /usr/sbin/chronyd died
 * Failed to start chronyd                                          [ !! ]
 * ERROR: chronyd failed to start

> What about logs?

None evident.

> If none, you can inspect the start-stop-daemon line in the init file,
> get the command line it launches chrony with, and see what that prints
> to the console.

Here's where it gets strange. When I run that command, chronyd runs hunky-
dory, but calling it from /etc/init.d/chronyd gets me the error above. This 
is what works:

# start-stop-daemon --start --exec /usr/sbin/chronyd --pidfile 
/run/chronyd.pid -- -f /etc/chrony/chrony.conf -s -r

And this stops it:

# start-stop-daemon --stop --pidfile /run/chronyd.pid

All those file names are copied directly from the init.d file. I did wonder 
about a timing problem somewhere, but I wouldn't expect that always to turn 
out the same way.

As I said, chronyd works on this four-core i5 box, just not on the two-core 
Atom.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 263 bytes --]

On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
> As I said, chronyd works on this four-core i5 box, just not on the
> two-core  Atom.

Have a look in the kernel of the Atom box and compare the RTC settings between 
the two boxen.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Friday 20 November 2015 11:03:55 Mick wrote:
> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
> > As I said, chronyd works on this four-core i5 box, just not on the
> > two-core  Atom.
> 
> Have a look in the kernel of the Atom box and compare the RTC settings
> between the two boxen.

Well, that was instructive - thanks Mick. I found a couple of settings I'm 
sure I'd never have set knowingly, one of them a debug. After removing them 
I still get the caught-an-interrupt and failed-to-start errors, but now I 
find that chrony is apparently running well despite the errors. At any rate, 
it logs the selection of a source five seconds after it's started and the 
process is still running:

 2051 ?    S    0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r

I've had another check through the kernel config, comparing it with the i5 
config, and I've removed several more things that I think shouldn't be 
there, but it's made no further difference.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Dale]

Peter Humphrey wrote:
> Hello list,
>
>   <<< SNIP >>>
>
> What's more, earlier versions had a decent man page and heavily commented 
> chronyd.conf, but now the chrony.conf man page has been cut to a bare 
> minimum and instead refers to a file chrony.txt "included in the 
> distribution". I cannot find any such file after running ebuild $(equery w 
> chrony) prepare.
>


I noticed this too.  I made a backup of my old file before updating with
dispatch-conf.  If you need a copy of my old file, I'd be glad to send
it to you.  Also, before that I copied my list of servers and copied
that back after the config updates into the new file.  So far, it has
worked, so far.  Give it time, it'll break eventually.  :/

Let me know if you need a known working file.  I'll send you a copy of
both if you want them. 

Dale

:-)  :-) 

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Friday 20 November 2015 11:02:13 Dale wrote:

> Let me know if you need a known working file.  I'll send you a copy of
> both if you want them.

Thanks Dale, but I already have the files that used to work. They still do 
on one box but not the other - even when they're identical.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Alan McKinnon]

On 20/11/2015 19:02, Peter Humphrey wrote:
> On Friday 20 November 2015 11:03:55 Mick wrote:
>> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
>>> As I said, chronyd works on this four-core i5 box, just not on the
>>> two-core  Atom.
>>
>> Have a look in the kernel of the Atom box and compare the RTC settings
>> between the two boxen.
> 
> Well, that was instructive - thanks Mick. I found a couple of settings I'm 
> sure I'd never have set knowingly, one of them a debug. After removing them 
> I still get the caught-an-interrupt and failed-to-start errors, but now I 
> find that chrony is apparently running well despite the errors. At any rate, 
> it logs the selection of a source five seconds after it's started and the 
> process is still running:
> 
>  2051 ?    S    0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r
> 
> I've had another check through the kernel config, comparing it with the i5 
> config, and I've removed several more things that I think shouldn't be 
> there, but it's made no further difference.
> 


Well that's interesting. I suggest at this point you ask at chrony's
support list - they'd know better than others what RTC settings their
software needs.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Chrony-2.2 failing

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1818 bytes --]

On Friday 20 Nov 2015 17:07:47 Alan McKinnon wrote:
> On 20/11/2015 19:02, Peter Humphrey wrote:
> > On Friday 20 November 2015 11:03:55 Mick wrote:
> >> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
> >>> As I said, chronyd works on this four-core i5 box, just not on the
> >>> two-core  Atom.
> >> 
> >> Have a look in the kernel of the Atom box and compare the RTC settings
> >> between the two boxen.
> > 
> > Well, that was instructive - thanks Mick. I found a couple of settings
> > I'm sure I'd never have set knowingly, one of them a debug. After
> > removing them I still get the caught-an-interrupt and failed-to-start
> > errors, but now I find that chrony is apparently running well despite
> > the errors. At any rate, it logs the selection of a source five seconds
> > after it's started and the
> > 
> > process is still running:
> >  2051 ?    S    0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r
> > 
> > I've had another check through the kernel config, comparing it with the
> > i5 config, and I've removed several more things that I think shouldn't
> > be there, but it's made no further difference.
> 
> Well that's interesting. I suggest at this point you ask at chrony's
> support list - they'd know better than others what RTC settings their
> software needs.

I don't know what your settings are, but using the suggested by the ebuild new 
config file (which is *very* much a stipped down sample of the previous 
version) mine is not run with -s or -r.

I tried running chrony with all my old configuration settings and it barfed on 
number of my entries.  So I suggest that you first run it with only the 
settings provided in /usr/share/doc/chrony-2.2/chrony.conf.example1.bz2 and 
then modify one setting at a time.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[brettrsears]

B
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Alan McKinnon <alan.mckinnon@gmail.com>
Date: Fri, 20 Nov 2015 19:07:47 
To: <gentoo-user@lists.gentoo.org>
Reply-to: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing

On 20/11/2015 19:02, Peter Humphrey wrote:
> On Friday 20 November 2015 11:03:55 Mick wrote:
>> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
>>> As I said, chronyd works on this four-core i5 box, just not on the
>>> two-core  Atom.
>>
>> Have a look in the kernel of the Atom box and compare the RTC settings
>> between the two boxen.
> 
> Well, that was instructive - thanks Mick. I found a couple of settings I'm 
> sure I'd never have set knowingly, one of them a debug. After removing them 
> I still get the caught-an-interrupt and failed-to-start errors, but now I 
> find that chrony is apparently running well despite the errors. At any rate, 
> it logs the selection of a source five seconds after it's started and the 
> process is still running:
> 
>  2051 ?    S    0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r
> 
> I've had another check through the kernel config, comparing it with the i5 
> config, and I've removed several more things that I think shouldn't be 
> there, but it's made no further difference.
> 


Well that's interesting. I suggest at this point you ask at chrony's
support list - they'd know better than others what RTC settings their
software needs.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Friday 20 November 2015 17:30:56 Mick wrote:
> On Friday 20 Nov 2015 17:07:47 Alan McKinnon wrote:
> > On 20/11/2015 19:02, Peter Humphrey wrote:
> > > On Friday 20 November 2015 11:03:55 Mick wrote:
> > >> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote:
> > >>> As I said, chronyd works on this four-core i5 box, just not on the
> > >>> two-core  Atom.
> > >> 
> > >> Have a look in the kernel of the Atom box and compare the RTC
> > >> settings
> > >> between the two boxen.
> > > 
> > > Well, that was instructive - thanks Mick. I found a couple of settings
> > > I'm sure I'd never have set knowingly, one of them a debug. After
> > > removing them I still get the caught-an-interrupt and failed-to-start
> > > errors, but now I find that chrony is apparently running well despite
> > > the errors. At any rate, it logs the selection of a source five
> > > seconds
> > > after it's started and the
> > > 
> > > process is still running:
> > >  2051 ?    S    0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s
> > >  -r
> > > 
> > > I've had another check through the kernel config, comparing it with
> > > the
> > > i5 config, and I've removed several more things that I think shouldn't
> > > be there, but it's made no further difference.
> > 
> > Well that's interesting. I suggest at this point you ask at chrony's
> > support list - they'd know better than others what RTC settings their
> > software needs.
> 
> I don't know what your settings are, but using the suggested by the ebuild
> new config file (which is *very* much a stipped down sample of the
> previous version) mine is not run with -s or -r.
> 
> I tried running chrony with all my old configuration settings and it
> barfed on number of my entries.  So I suggest that you first run it with
> only the settings provided in
> /usr/share/doc/chrony-2.2/chrony.conf.example1.bz2 and then modify one
> setting at a time.

My first attempt to get chronyd running was with only the newly installed, 
stripped-down config, which I think is the same as that example. That's 
where all the trouble started. And all along, I've been comparing the 
configs on the two boxes and sometimes tweaking things.

I think I'll follow Alan's suggestion and head upstream.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Saturday 21 November 2015 09:59:18 I wrote:

> I think I'll follow Alan's suggestion and head upstream.

After some discussion with Miroslav Lichvar I've found a chrony.conf that 
works for me on my 32-bit 2-core Atom. This is it:

pool pool.ntp.org iburst
server ntp0.zen.co.uk iburst
server ntp1.zen.co.uk iburst
driftfile /var/lib/chrony/drift
makestep 1.0 3
allow 192.168.1/24
mailonchange prh@serv.prhnet 0.5
rtcfile /var/lib/chrony/rtc
rtconutc

The installation-default file causes the start-stop-daemon to catch an 
unexpected interrupt and report an error, even though the chronyd process 
continues to run.

Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd start' 
the init process runs normally and I'm left with scores of trace files, none 
of which help because the stray interrupt wasn't detected.

So I'm left with a setup that works for me but leaves what looks (to me) 
like a timing problem unsolved.

I'll report back if I hear any more.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Alan McKinnon]

On 24/11/2015 17:24, Peter Humphrey wrote:
> On Saturday 21 November 2015 09:59:18 I wrote:
> 
>> I think I'll follow Alan's suggestion and head upstream.
> 
> After some discussion with Miroslav Lichvar I've found a chrony.conf that 
> works for me on my 32-bit 2-core Atom. This is it:
> 
> pool pool.ntp.org iburst
> server ntp0.zen.co.uk iburst
> server ntp1.zen.co.uk iburst
> driftfile /var/lib/chrony/drift
> makestep 1.0 3
> allow 192.168.1/24
> mailonchange prh@serv.prhnet 0.5
> rtcfile /var/lib/chrony/rtc
> rtconutc
> 
> The installation-default file causes the start-stop-daemon to catch an 
> unexpected interrupt and report an error, even though the chronyd process 
> continues to run.
> 
> Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd start' 
> the init process runs normally and I'm left with scores of trace files, none 
> of which help because the stray interrupt wasn't detected.
> 
> So I'm left with a setup that works for me but leaves what looks (to me) 
> like a timing problem unsolved.
> 
> I'll report back if I hear any more.
> 



Ugh, don't you just hate issues like that? The problem with "solutions"
like start-stop-daemon is they have to deal with whatever the daemon
feels like returning (an infinite number of permutations), so support
for daemon is never complete.

Regardless of what one thinks of systemd, this is one of the things it
set out to deal with. There's only one way to start something, and it
behaves one way, making behaviour considerably more predictable.

[ A bit of a rant I know, but I'm still smarting from years of rancid
and Cisco logins - basically the same kind of problem you are having on
a much larger scale...]


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Wednesday 25 November 2015 19:05:44 Alan McKinnon wrote:
> On 24/11/2015 17:24, Peter Humphrey wrote:
--->8
> > The installation-default file causes the start-stop-daemon to catch an
> > unexpected interrupt and report an error, even though the chronyd
> > process
> > continues to run.
> > 
> > Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd
> > start' the init process runs normally and I'm left with scores of trace
> > files, none of which help because the stray interrupt wasn't detected.
--->8
> Ugh, don't you just hate issues like that? The problem with "solutions"
> like start-stop-daemon is they have to deal with whatever the daemon
> feels like returning (an infinite number of permutations), so support
> for daemon is never complete.

I've been offered one suggestion which will need me to make a local overlay 
with a small code change. I'll try that and see what happens.

> Regardless of what one thinks of systemd, this is one of the things it
> set out to deal with. There's only one way to start something, and it
> behaves one way, making behaviour considerably more predictable.

So it does occasionally have one benefit then.

> [ A bit of a rant I know, but I'm still smarting from years of rancid
> and Cisco logins - basically the same kind of problem you are having on
> a much larger scale...]

I'll be content with my tiny scale, thanks very much  :)

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

On Thu, 26 Nov 2015 10:39:56 +0000, Peter Humphrey wrote:

> > Regardless of what one thinks of systemd, this is one of the things it
> > set out to deal with. There's only one way to start something, and it
> > behaves one way, making behaviour considerably more predictable.  
> 
> So it does occasionally have one benefit then.

Yes. The rest of the time it has many more :)

SCNR


-- 
Neil Bothwick

Get your grubby hands off my tagline! I stole it first!

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Thursday 26 November 2015 13:00:29 Neil Bothwick wrote:
> On Thu, 26 Nov 2015 10:39:56 +0000, Peter Humphrey wrote:
> > > Regardless of what one thinks of systemd, this is one of the things it
> > > set out to deal with. There's only one way to start something, and it
> > > behaves one way, making behaviour considerably more predictable.
> > 
> > So it does occasionally have one benefit then.
> 
> Yes. The rest of the time it has many more :)

But the Unixy approach to command names is certainly not one of them  :)

> SCNR

Ditto repeato.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

On Thu, 26 Nov 2015 14:00:22 +0000, Peter Humphrey wrote:

> > > > Regardless of what one thinks of systemd, this is one of the
> > > > things it set out to deal with. There's only one way to start
> > > > something, and it behaves one way, making behaviour considerably
> > > > more predictable.  
> > > 
> > > So it does occasionally have one benefit then.  
> > 
> > Yes. The rest of the time it has many more :)  
> 
> But the Unixy approach to command names is certainly not one of them  :)

Indeed, thank ${DEITY} for tab-completion.

Why does "tab-completion" require so much typing?


-- 
Neil Bothwick

Windows Error #10: Insufficient money spent in hardware.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Chrony-2.2 failing

[Alan McKinnon]

On 26/11/2015 17:04, Neil Bothwick wrote:
> On Thu, 26 Nov 2015 14:00:22 +0000, Peter Humphrey wrote:
> 
>>>>> Regardless of what one thinks of systemd, this is one of the
>>>>> things it set out to deal with. There's only one way to start
>>>>> something, and it behaves one way, making behaviour considerably
>>>>> more predictable.  
>>>>
>>>> So it does occasionally have one benefit then.  
>>>
>>> Yes. The rest of the time it has many more :)  
>>
>> But the Unixy approach to command names is certainly not one of them  :)
> 
> Indeed, thank ${DEITY} for tab-completion.
> 
> Why does "tab-completion" require so much typing?
> 
> 


Because if it were "tc" you'd be forever wondering what it is!
And besides, tc is taken

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Chrony-2.2 failing

[Peter Humphrey]

On Thursday 26 November 2015 10:39:56 I wrote:
> On Wednesday 25 November 2015 19:05:44 Alan McKinnon wrote:
> > On 24/11/2015 17:24, Peter Humphrey wrote:
> --->8
> 
> > > The installation-default file causes the start-stop-daemon to catch an
> > > unexpected interrupt and report an error, even though the chronyd
> > > process
> > > continues to run.
> > > 
> > > Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd
> > > start' the init process runs normally and I'm left with scores of
> > > trace
> > > files, none of which help because the stray interrupt wasn't detected.
> 
> --->8
> 
> > Ugh, don't you just hate issues like that? The problem with "solutions"
> > like start-stop-daemon is they have to deal with whatever the daemon
> > feels like returning (an infinite number of permutations), so support
> > for daemon is never complete.
> 
> I've been offered one suggestion which will need me to make a local
> overlay with a small code change. I'll try that and see what happens.

The problem turns out to have been caused by the init script specifying 
--background to start-stop-daemon, which conflicts with chronyd's own 
forking to the background - at least, it does on my Atom box so it could 
elsewhere too.

Stand ready, bgo.

-- 
Rgds
Peter

Re: [gentoo-user] Chrony-2.2 failing

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2116 bytes --]

On Friday 20 Nov 2015 09:24:52 Peter Humphrey wrote:
> On Thursday 19 Nov 2015 22:15:33 Marc Joliet wrote:
> > On Thursday 19 November 2015 10:49:08 Peter Humphrey wrote:
> > >Hello list,
> > 
> > [...]
> > 
> > >What's more, earlier versions had a decent man page and heavily
> > >commented chronyd.conf, but now the chrony.conf man page has been cut
> > >to a bare minimum and instead refers to a file chrony.txt "included in
> > >the distribution". I cannot find any such file after running ebuild
> > >$(equery w chrony) prepare.
> > 
> > You've already gotten an answer regarding the man page, but with regards
> > to the configuration file in /etc, it looks like what you are looking for
> > is in the standard documentation path:
> > 
> > % qlist chrony | grep doc/
> > /usr/share/doc/chrony-2.2/README
> > /usr/share/doc/chrony-2.2/NEWS
> > /usr/share/doc/chrony-2.2/FAQ
> > /usr/share/doc/chrony-2.2/chrony.conf.example1
> > /usr/share/doc/chrony-2.2/chrony.conf.example2
> > /usr/share/doc/chrony-2.2/chrony.conf.example3
> > /usr/share/doc/chrony-2.2/chrony.keys.example
> > 
> > The *.example3 file is apparently the one that used to be copied to /etc.
> > 
> > HTH
> 
> Thanks for the ideas, gents.

I had another look at a laptop of mine and wondered if any of you gents had 
added '/usr/local/bin/chronyc online/offline' in your laptop network scripts?

There's two issues with this laptop.  First is that it is mostly used at home, 
but occasionally may be used on the move, so an ntp server is not always at 
hand.  Second is that it can take up to 70 seconds to get an IP address from 
the router, during which it will also have no access to the Internet.

This is my current config:
================================
server 0.uk.pool.ntp.org offline
server 1.uk.pool.ntp.org offline
server 2.uk.pool.ntp.org offline
server 3.uk.pool.ntp.org offline

maxupdateskew 100

driftfile /var/lib/chrony/drift

dumponexit
dumpdir /var/lib/chrony

makestep 1.0 3

rtcsync

rtcdevice /dev/rtc
================================

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]