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 3E9AD1384B4 for ; Fri, 20 Nov 2015 10:22:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5DC7D21C00F; Fri, 20 Nov 2015 10:22:03 +0000 (UTC) Received: from smarthost03c.mail.zen.net.uk (smarthost03c.mail.zen.net.uk [212.23.1.22]) by pigeon.gentoo.org (Postfix) with ESMTP id 4059DE01B5 for ; Fri, 20 Nov 2015 10:22:01 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost03c.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1ZzipN-0000qp-56 for gentoo-user@lists.gentoo.org; Fri, 20 Nov 2015 10:22:01 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Chrony-2.2 failing Date: Fri, 20 Nov 2015 10:22 +0000 Message-ID: <1688590.CMN6j3byKX@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <564E0417.4080201@gmail.com> References: <2068412.puBuVpJXRl@wstn> <564E0417.4080201@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-smarthost03c-IP: [82.69.80.10] X-Archives-Salt: 066f44d9-ccd0-485a-89f5-24bdccdb6f11 X-Archives-Hash: d0c879b6fee28ee82718c85f4c6ebb63 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