Hi, On Fri, Dec 01, 2017 at 09:17:38PM -0800, Andres Salomon wrote:
On Fri, 1 Dec 2017 21:39:33 +0100 Paul Gevers <elb...@debian.org> wrote:Control: tags -1 moreinfo I forward the question to the submitter. (@Vincent, in the BTS, the submitter is not automatically subscribed, so never assume that).Thanks for Cc'ing me, Paul!
Thanks Paul! Indeed I totally forgot that submitters weren’t automatically subscribed.
Andres, is the issue always reproducible?Yep. I could do this all day (although rebooting is pretty annoying :) dilinger@e7450:~$ sudo apt-get remove --purge chrony [...] Purging configuration files for chrony (3.0-4+deb9u1) ... Processing triggers for systemd (232-25+deb9u1) ... dilinger@e7450:~$ ls /etc/chron* ls: cannot access '/etc/chron*': No such file or directory dilinger@e7450:~$ sudo apt-get install chrony [...] Preparing to unpack .../chrony_3.0-4+deb9u1_amd64.deb ... Unpacking chrony (3.0-4+deb9u1) ... Setting up chrony (3.0-4+deb9u1) ... Creating '_chrony' system user/group for the chronyd daemon… Creating config file /etc/chrony/chrony.conf with new version Creating config file /etc/chrony/chrony.keys with new version Created symlink /etc/systemd/system/chronyd.service → /lib/systemd/system/chrony.service. Created symlink /etc/systemd/system/multi-user.target.wants/chrony.service → /lib/systemd/system/chrony.service. Processing triggers for systemd (232-25+deb9u1) ... Processing triggers for man-db (2.7.6.1-2) ... dilinger@e7450:~$ systemctl status chrony ● chrony.service - chrony, an NTP client/server Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: e Active: active (running) since Fri 2017-12-01 21:06:12 PST; 48s ago Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5) Main PID: 12713 (chronyd) CGroup: /system.slice/chrony.service └─12713 /usr/sbin/chronyd [reboot] dilinger@e7450:~$ uptime 21:12:24 up 1 min, 1 user, load average: 0.59, 0.21, 0.08 dilinger@e7450:~$ systemctl status chrony ● chrony.service - chrony, an NTP client/server Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: e Active: inactive (dead) Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5)
What does “journalctl -u chrony” return when that happens?
Yes, it's reproducible, see above.
BTW, when I restarted my computer earlier this morning (also when I filed
the bug; see the original 00:26:01 logs), I manually started chrony.
It's been running since then (with a few suspend/resumes), but chrony
seems to have disappeared.
dilinger@e7450:~$ uptime
21:01:59 up 20:31, 1 user, load average: 0.39, 0.46, 0.60
dilinger@e7450:~$ systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: e
Active: inactive (dead)
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
dilinger@e7450:~$
I wonder if it's crashing or something?
What I would like you to try is to boot with the “systemd.log_level=debug” kernel parameter and attach the output of “journalctl -b” and a dump of “systemctl”. It may be worth to see if chrony from testing/unstable behaves the same way.
Also, I tried to reproduce this issue on a fresh Stretch install but failed. Could you give more details on your system (cpu arch, desktop environment, network manager, Debian stable version, …)?
Cheers, Vincent
signature.asc
Description: PGP signature
