Chronyd and Chrony services failed to start

    • Offizieller Beitrag

    do you have a file in /usr/lib/systemd/system/systemd-timesyncd.service.d


    start chronyd on the command line and then /usr/lib/chrony/chrony-helper update-daemon

    If this works, we need to dig deeper

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    I checked my /etc/default/chrony

    Code
    $ cat /etc/default/chrony
# This is a configuration file for /etc/init.d/chrony and
# /lib/systemd/system/chrony.service; it allows you to pass various options to
# the chrony daemon without editing the init script or service file.


# Options to pass to chrony.
DAEMON_OPTS="-F -1"

    The manual says:


    -F level

    This option configures a system call filter when chronyd is compiled with support for the Linux secure computing (seccomp) facility. In level 1 the process is killed when a forbidden system call is made, in level -1 the SIGSYS signal is thrown instead and in level 0 the filter is disabled (default 0).

    It’s recommended to enable the filter only when it’s known to work on the version of the system where chrony is installed as the filter needs to allow also system calls made from libraries that chronyd is using (e.g. libc) and different versions or implementations of the libraries may make different system calls. If the filter is missing some system call, chronyd could be killed even in normal operation.



    Start chrony with chronyd -d -F 1 and see what happenes.


    If it gets killed, it is time for strace

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    This is the output of sudo /usr/sbin/chronyd -d -F 1

    Code
    2022-01-07T19:15:16Z chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2022-01-07T19:15:16Z Frequency -9.749 +/- 0.225 ppm read from /var/lib/chrony/chrony.drift
2022-01-07T19:15:16Z Loaded seccomp filter
2022-01-07T19:15:31Z Selected source 51.38.27.129
Bad system call


    Here I have attached the output of sudo strace /usr/sbin/chronyd -d -F 1

    OK, on your system -F 1 will not allow to adjust the clock:


    Code
    clock_adjtime(CLOCK_REALTIME,  <unfinished ...>) = ?
+++ killed by SIGSYS +++


    Edit /etc/default/chrony and change DAEMON_OPTS="-F -1" to DAEMON_OPTS=""

    then start chronyd systemctl start chronyd check status systemclt status chronyd


    Anything special about your system Kernel?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Danke 1

  • votdev

    Hat das Label gelöst hinzugefügt.

  • votdev

    Hat das Label OMV 5.x hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden