public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Thu, 19 Nov 2015 19:17:11 +0200	[thread overview]
Message-ID: <564E0417.4080201@gmail.com> (raw)
In-Reply-To: <2068412.puBuVpJXRl@wstn>

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



  parent reply	other threads:[~2015-11-19 17:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 10:49 [gentoo-user] Chrony-2.2 failing Peter Humphrey
2015-11-19 17:06 ` Alexander Kapshuk
2015-11-19 17:17 ` Alan McKinnon [this message]
2015-11-20 10:22   ` Peter Humphrey
2015-11-20 11:03     ` Mick
2015-11-20 17:02       ` Peter Humphrey
2015-11-20 17:07         ` Alan McKinnon
2015-11-20 17:30           ` Mick
2015-11-21  9:59             ` Peter Humphrey
2015-11-24 15:24               ` Peter Humphrey
2015-11-25 17:05                 ` Alan McKinnon
2015-11-26 10:39                   ` Peter Humphrey
2015-11-26 13:00                     ` Neil Bothwick
2015-11-26 14:00                       ` Peter Humphrey
2015-11-26 15:04                         ` Neil Bothwick
2015-11-26 15:12                           ` Alan McKinnon
2015-11-27  9:33                     ` Peter Humphrey
2015-11-20 19:39           ` brettrsears
2015-11-19 21:15 ` Marc Joliet
2015-11-20  9:24   ` Peter Humphrey
2015-12-07 18:41     ` Mick
2015-11-20 17:02 ` Dale
2015-11-20 17:06   ` 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=564E0417.4080201@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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