On Mon, 25 Feb 2019 01:22:40 +0100 Vincent Blut wrote: > On Sun, Feb 24, 2019 at 08:19:02PM +0100, Francesco Poli wrote: > >On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote: > > > >> Please use `ps ax | grep chrony' (or ps -ef). `ps a' only lists > >> processes with a tty. > > > >You are right, sorry: I wanted to simplify the command output, but I > >overplayed... ;-) > >Anyway, chronyd really fails to start: > > > > # ps ax | grep chrony > > 12035 pts/0 S+ 0:00 grep chrony > > Interesting. Does `grep -i chrony /var/log/messages' report something > suspect?
Nothing is added to /var/log/messages when chrony fails to start. > > >> Also, the output of `chronyc tracking' would be useful to check > >> chronyd’s status and system time information. > > > >Do you mean, when the daemon is not running? > > Well, no. ;-) Obviously! ;-) > > > > # chronyc tracking > > 506 Cannot talk to daemon > > > >Or when the daemon is running with log disabled? > > Yes, when chronyd is running with the log directive disabled but the > syscall filter enabled. # ps ax | grep chrony 15534 ? S 0:00 /usr/sbin/chronyd -F -1 15535 ? S 0:00 /usr/sbin/chronyd -F -1 15557 pts/1 S+ 0:00 grep chrony # chronyc tracking Reference ID : XXXXXXXX (yyyyyyyy.zzzzz.tld) Stratum : 4 Ref time (UTC) : Mon Feb 25 20:50:10 2019 System time : 0.000000003 seconds slow of NTP time Last offset : +0.000052817 seconds RMS offset : 0.000052817 seconds Frequency : 62.991 ppm slow Residual freq : +12.282 ppm Skew : 0.023 ppm Root delay : 0.047111727 seconds Root dispersion : 0.002364162 seconds Update interval : 2.0 seconds Leap status : Normal [...] > >The interesting thing is that chronyd seems to be started by > >"service chrony start" and then seems to die immediately after > >beginning to write some logs: > > > > [again, snip some information] > > Hmm, that’s fairly strange. I failed to reproduce this issue on some of > my systems. Would you please share your chrony.conf file (privately if > you prefer)? I think there's nothing really special in it. I've attached it. There's another important thing that I should mention. Today I have upgraded chrony on another box and the system call filter works fine there (with mailonchange disabled, but with log *enabled*). So I tried to think about the differences between the box where it fails, and the box where it works. The first difference is the architecture: • the box where it fails is i386 • the box where it works is amd64 However, I suspect that chrony level of abstraction is high enough to make this difference immaterial... Or am I wrong? The second difference is the init system and might be more relevant: • the box where it fails runs with sysvinit as PID 1 • the box where it works runs with systemd as PID 1 I cannot think about other potentially relevant differences, but, of course, feel free to ask, in case you have any idea... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
chrony.conf.gz
Description: application/gzip
pgpVYLFirsBBY.pgp
Description: PGP signature
