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?
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. ;-)
# 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.
[snip valuable information] It seems the daemon is not running and no logs are created or updated.
With chronyd not running, this result is indeed expected.
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)?
Cheers, Vincent
signature.asc
Description: PGP signature
