Service chronyd stops automatically after startup
by lpwevers from LinuxQuestions.org on (#5EW56)
Hi,
I'm trying to have the time in sync on a Debian 10 server using chronyd. When I start the service all seems OK, but after a few seconds it automatically stops itself:
Code:root@digsvl003:~# systemctl status chronyd
chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2021-03-03 10:19:49 CET; 6s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 22640 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Process: 22644 ExecStartPost=/usr/lib/chrony/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
Main PID: 22642 (code=exited, status=0/SUCCESS)
Mar 03 10:19:43 digsvl003 chronyd[22642]: Frequency -37.850 +/- 0.528 ppm read from /var/lib/chrony/chrony.drift
Mar 03 10:19:43 digsvl003 chronyd[22642]: Loaded seccomp filter
Mar 03 10:19:43 digsvl003 systemd[1]: Started chrony, an NTP client/server.
Mar 03 10:19:49 digsvl003 chronyd[22642]: Selected source 194.109.6.2
Mar 03 10:19:49 digsvl003 chronyd[22642]: System clock wrong by -7.094333 seconds, adjustment started
Mar 03 10:19:42 digsvl003 chronyd[22642]: System clock was stepped by -7.094333 seconds
Mar 03 10:19:49 digsvl003 chronyd[22642]: chronyd exiting
Mar 03 10:19:49 digsvl003 systemd[1]: Stopping chrony, an NTP client/server...
Mar 03 10:19:49 digsvl003 systemd[1]: chrony.service: Succeeded.
Mar 03 10:19:49 digsvl003 systemd[1]: Stopped chrony, an NTP client/server.In /etc/chrony/chrony.conf I have:
Code:# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
server ntp.xs4all.nl iburst
server ntp.tue.nl iburst
pool 2.debian.pool.ntp.org iburst
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
# Uncomment the following line to turn logging on.
#log tracking measurements statistics
# Log files location.
logdir /var/log/chrony
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
# Allow NTP client access from local network.
allow 127.0.0.1
cmdallow 127.0.0.1How do I prevent chronyd from stopping immediately after starting it?
Kind regards,
Louis
I'm trying to have the time in sync on a Debian 10 server using chronyd. When I start the service all seems OK, but after a few seconds it automatically stops itself:
Code:root@digsvl003:~# systemctl status chronyd
chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2021-03-03 10:19:49 CET; 6s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 22640 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Process: 22644 ExecStartPost=/usr/lib/chrony/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
Main PID: 22642 (code=exited, status=0/SUCCESS)
Mar 03 10:19:43 digsvl003 chronyd[22642]: Frequency -37.850 +/- 0.528 ppm read from /var/lib/chrony/chrony.drift
Mar 03 10:19:43 digsvl003 chronyd[22642]: Loaded seccomp filter
Mar 03 10:19:43 digsvl003 systemd[1]: Started chrony, an NTP client/server.
Mar 03 10:19:49 digsvl003 chronyd[22642]: Selected source 194.109.6.2
Mar 03 10:19:49 digsvl003 chronyd[22642]: System clock wrong by -7.094333 seconds, adjustment started
Mar 03 10:19:42 digsvl003 chronyd[22642]: System clock was stepped by -7.094333 seconds
Mar 03 10:19:49 digsvl003 chronyd[22642]: chronyd exiting
Mar 03 10:19:49 digsvl003 systemd[1]: Stopping chrony, an NTP client/server...
Mar 03 10:19:49 digsvl003 systemd[1]: chrony.service: Succeeded.
Mar 03 10:19:49 digsvl003 systemd[1]: Stopped chrony, an NTP client/server.In /etc/chrony/chrony.conf I have:
Code:# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
server ntp.xs4all.nl iburst
server ntp.tue.nl iburst
pool 2.debian.pool.ntp.org iburst
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
# Uncomment the following line to turn logging on.
#log tracking measurements statistics
# Log files location.
logdir /var/log/chrony
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
# Allow NTP client access from local network.
allow 127.0.0.1
cmdallow 127.0.0.1How do I prevent chronyd from stopping immediately after starting it?
Kind regards,
Louis