Devuan bug report logs - #138
chrony: is always offline at system start

Package: chrony; Reported by: Friedhelm Mehnert <[email protected]>; Keywords: jessie; Done: Mark Hindley <[email protected]>; Maintainer for chrony is (unknown).

---

Message received at [email protected]:

Received: (at 138-done) by bugs.devuan.org; 12 Jan 2023 11:39:04 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Thu, 12 Jan 2023 11:39:04 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 7fTkAUXxv2O3PgAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Thu, 12 Jan 2023 11:38:45 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id F2620B69; Thu, 12 Jan 2023 11:38:44 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 9D9AB226
	for <[email protected]>; Thu, 12 Jan 2023 11:38:43 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pFvur-0001Ch-Tq; Thu, 12 Jan 2023 11:38:41 +0000
Received: (nullmailer pid 10196 invoked by uid 1000);
	Thu, 12 Jan 2023 11:38:41 -0000
Date: Thu, 12 Jan 2023 11:38:41 +0000
From: Mark Hindley <[email protected]>
To: Friedhelm Mehnert <[email protected]>, [email protected]
Subject: Re: bug#138: chrony: is always offline at system start
Message-ID: <Y7/[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks

Version: 2.2.1-1

This was changed in Debian version 2.2.1-1.

Closing.

Mark

---

Notification sent to Friedhelm Mehnert <[email protected]>:
bug acknowledged by developer. Full text available.

---

Reply sent to Mark Hindley <[email protected]>:
You have taken responsibility. Full text available.

---

Tags added: jessie Request was from KatolaZ <[email protected]> to [email protected]. Full text available.

---

Message received at [email protected]:

Received: (at submit) by bugs.devuan.org; 21 Aug 2017 15:40:08 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [178.62.188.7]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Mon, 21 Aug 2017 17:40:08 +0200 (CEST)
Received: from mail.ud03.udmedia.de (ud03.udmedia.de [194.117.254.43])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits))
	(No client certificate requested)
	by tupac2.dyne.org (Postfix) with ESMTPS id 9892018DAC9
	for <[email protected]>; Mon, 21 Aug 2017 15:32:46 +0000 (UTC)
Authentication-Results: tupac2.dyne.org; dkim=pass
	reason="1024-bit key; unprotected key/testing"
	header.d=mail.ud03.udmedia.de [email protected]
	header.b=EhJ6eNS3; dkim-adsp=none (unprotected policy);
	dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h=
	content-type:mime-version:content-transfer-encoding:from:to
	:subject:message-id:date:sender; s=k1; bh=AAsbhgxiezVjpT5aoQqnFr
	CC6yDziJ9ae0zSiDL7Gw4=; b=EhJ6eNS3lk/kzNAlF9i63p1+IQQr75YiTtK+Bt
	we52LRYdsd0JDAiJ553Y/+m0Xac94ir+YkUD0hK9MalSRg9DZT1n/spb7aIrEjnB
	v8FbHjDPanMd4JECkuAs5JjKdxyCOaNJ9QwC/x1QuTppclIM3x7FpcAkfpCUt4zk
	PSbKE=
Received: (qmail 5738 invoked from network); 21 Aug 2017 17:32:45 +0200
Received: from p3e9d065b.dip0.t-ipconnect.de (HELO m6.friedhelms.net) ([email protected])
  by mail.ud03.udmedia.de with ESMTPSA (ECDHE-RSA-AES128-GCM-SHA256 encrypted, authenticated); 21 Aug 2017 17:32:45 +0200
Received: from [192.168.1.1] (helo=m1.friedhelms.net ident=Debian-exim)
	by m6.friedhelms.net with esmtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1djogx-0000SP-OW
	for [email protected]; Mon, 21 Aug 2017 17:32:44 +0200
Received: from fm by m1.friedhelms.net with local (Exim 4.84_2 #2 (Debian))
	id 1djogx-0007eW-A8; Mon, 21 Aug 2017 17:32:39 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Friedhelm Mehnert <[email protected]>
To: Devuan Bug Tracking System <[email protected]>
Subject: chrony: is always offline at system start
Message-ID: <[email protected]>
X-Mailer: reportbug 6.6.3+devuan1.3
Date: Mon, 21 Aug 2017 17:32:39 +0200
Sender: Friedhelm Mehnert <[email protected]>
X-Spam-Score: -1.0 (-)
X-Spam-Score-int: -9
Lines: 136
Bytes: 4321
X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

Package: chrony
Version: 1.30-2+deb8u2
Severity: normal

Dear Maintainer,

On *slower systems* like BananaPi chrony is always offline after system
start. To bring it online one has to do: "/etc/init.d/chrony restart".

The course of the problem is a timeout value within the startup-script.
On *slow machines" the startup of chrony takes more than 2 seconds.
The developers have been too optimistic (Developement systems are usualy
pretty fast). ;-)

/etc/init.d/chrony
>     1	#! /bin/sh
>     2	#
>     3	# Written by Miquel van Smoorenburg <[email protected]>.
>     4	# Modified for Debian GNU/Linux by Ian Murdock <[email protected]>.
>     5	# Modified for Debian by Christoph Lameter <[email protected]>
>     6	# Modified for chrony by John Hasler <[email protected]> 1998-2010
>     7	
>     8	### BEGIN INIT INFO
>     9	# Provides:          chrony
>    10	# Required-Start:    $remote_fs
>    11	# Required-Stop:     $remote_fs
>    12	# Should-Start:      $syslog $network $named $hwclock
>    13	# Should-Stop:       $syslog $network $named $hwclock
>    14	# Default-Start:     2 3 4 5
>    15	# Default-Stop:      0 1 6
>    16	# Short-Description: Controls chronyd NTP time daemon
>    17	# Description:       Chronyd is the NTP time daemon in the Chrony package
>    18	### END INIT INFO
>    19	
>    20	PATH=/bin:/usr/bin:/sbin:/usr/sbin
>    21	DAEMON=/usr/sbin/chronyd
>    22	FLAGS="defaults"
>    23	NAME="chronyd"
>    24	DESC="time daemon"
>    25	
>    26	test -f $DAEMON || exit 0
>    27	
>    28	putonline ()
>    29	{ # Do we have a default route?  If so put chronyd online.
>    30	    if timelimit -q -s9 -t5 -- netstat -rn 2>/dev/null | grep UG | cut -f 1 -d ' ' | grep -q '0\.0\.0\.0' 
>    31	    then
>    32		sleep 2  # Chronyd can take a while to start.
                ^^^^^
THIS needs to be changed to 5!
=================================

>    33		KEY=$(awk '$1 ~ /^commandkey$/ { print $2; exit}' /etc/chrony/chrony.conf)
>    34		PASSWORD=`awk '$1 ~ /^'$KEY'$/ {print $2; exit}' /etc/chrony/chrony.keys`
>    35		# Make sure chronyc can't hang us up.
>    36		if timelimit -q -s9 -t5 -- /usr/bin/chronyc > /dev/null << EOF
>    37	password $PASSWORD
>    38	online
>    39	burst 5/10
>    40	quit
>    41	EOF
>    42	        then
>    43	                touch /var/run/chrony-ppp-up
>    44	                echo "$NAME is running and online."
>    45	        else
>    46	                rm -f /var/run/chrony-ppp-up
>    47	                echo "$NAME is running and offline."    
>    48	        fi
>    49	    else
>    50	        rm -f /var/run/chrony-ppp-up
>    51	        echo "$NAME is running and offline."
>    52	    fi
>    53	}
>    54	
>    55	case "$1" in
>    56	    start)
>    57		start-stop-daemon --start --verbose --exec $DAEMON
>    58		case "$?" in
>    59			0) # daemon successfully started
>    60	#			putonline
>    61				;;
>    62		        1) # daemon already running
>    63			        ;;
>    64			*) # daemon could not be started
>    65				echo "$DAEMON failed to start."
>    66				exit 1
>    67				;;
>    68		esac
>    69		;;
>    70	    stop)
>    71		start-stop-daemon --stop --verbose --oknodo --exec $DAEMON
>    72		rm -f /var/run/chrony-ppp-up
>    73		;;
>    74	    restart|force-reload)
>    75		echo -n "Restarting $DESC: "
>    76		start-stop-daemon --stop --quiet --exec $DAEMON
>    77		sleep 1
>    78		start-stop-daemon --start --verbose --exec $DAEMON -- -r
>    79		case "$?" in
>    80			0) # daemon successfully started
>    81	#			putonline
>    82				;;
>    83		        1) # still running
>    84			        ;;
>    85			*) # daemon could not be started
>    86				echo "$DAEMON failed to restart."
>    87				rm -f /var/run/chrony-ppp-up
>    88				exit 1
>    89				;;
>    90		esac
>    91		;;
>    92	    *)
>    93		echo "Usage: /etc/init.d/chrony {start|stop|restart|force-reload}"
>    94		exit 1
>    95		;;
>    96	esac
>    97	
>    98	exit 0
>

I have had the problem with 3 different machines. All architectures are
affected.

-- System Information:

DEVUAN Jessie.

I deleted the system-information, since Im writing this bug report from
another machine, and it does not make any difference anyway.

Best Regards 
and a BIG THANKYOU for all the good work.

Friedhelm


-- no debconf information

---

Acknowledgement sent to Friedhelm Mehnert <[email protected]>:
New bug report received and forwarded. Copy sent to [email protected]. Full text available.

---

Report forwarded to [email protected], [email protected]:
bug#138; Package chrony. Full text available.

---