Your message dated Mon, 14 Dec 2015 17:06:58 +0100
with message-id <[email protected]>
and subject line Re: I propose this old bug be closed or more details released
has caused the Debian Bug report #583115,
regarding No sources right after boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
583115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583115
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.23-7
Severity: important
See, what happens, if I use chronyc right after I have booted my computer:
juhtolv@juhtolv:/home/juhtolv % chronyc
chrony version 1.23, copyright (C) 1997-2002 Richard P. Curnow
chrony comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions.
See the GNU General Public License version 2 for details.
chronyc> activity
200 OK
0 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
chronyc>
In most cases this helps:
-=*[ROOT ZSH]*=- root@juhtolv:/root # /etc/init.d/chrony restart
Restarting time daemon: chronyd is running and online.
And after that chronyc says:
juhtolv@juhtolv:/home/juhtolv % chronyc
chrony version 1.23, copyright (C) 1997-2002 Richard P. Curnow
chrony comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions.
See the GNU General Public License version 2 for details.
chronyc> activity
200 OK
2 sources online
0 sources offline
17 sources doing burst (return to online)
0 sources doing burst (return to offline)
chronyc>
I think there is something wrong with dependenccies of boot-scripts.
Maybe init-scrip of chrony should not run at all before networking
scripts have been run.
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing-proposed-updates'), (500,
'proposed-updates'), (101, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chrony depends on:
ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib
ii libreadline5 5.2-7 GNU readline and history libraries
ii timelimit 1.5-1 Simple utility to limit a process'
ii ucf 3.0025 Update Configuration File: preserv
Versions of packages chrony recommends:
ii udev 154-1 /dev/ and hotplug management daemo
chrony suggests no packages.
-- no debconf information
--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"Quidquid Latine dictum sit altum videtur."
--- End Message ---
--- Begin Message ---
tags 583115 unreproducible
thanks
On Sat, 15 Aug 2015 15:29:10 +1000 Andrew Worsley <[email protected]>
wrote:
> I installed the current version chrony:amd64/jessie 1.30-2 uptodate
in
> a virtual machine and was
> not able to fault it's start up.
>
> The script in /etc/init.d/chrony appears to be working fine.
>
> I am using systemd and I am not even sure the script
> /etc/init.d/chrony is even used now?
>
> I suggest that no update has happened on this for several years and
> there is no sign of the bug
> in the current release it be closed.
>
> Otherwise please submit some details . e.g. /etc/chrony/chrony.conf
> plus network set up.
>
> Andrew
Hi,
Since nobody objected to Andrew’s assertion, I’m tagging this bug
report as unreproducible
and closing it; feel free to reopen it if you think that’s false.
Cheers,
Vincent
--- End Message ---
