Chronyd (Network Time Protocol) - Stopped

Tried to install Nethserver 7.9 under a Proxmxo LXC Container…

On the End it looks not so bad but there is a problem with chronyd:

These are my modules/packages installed on nethserver…

rpm -qa nethserver*
nethserver-hosts-1.2.2-1.ns7.noarch
nethserver-subscription-inventory-3.6.8-1.ns7.x86_64
nethserver-mail-common-2.31.6-1.ns7.noarch
nethserver-mail-imapsync-2.31.6-1.ns7.noarch
nethserver-directory-3.4.3-1.ns7.noarch
nethserver-duc-1.7.0-1.ns7.noarch
nethserver-restore-data-2.0.7-1.ns7.noarch
nethserver-httpd-proxypass-3.12.2-1.ns7.noarch
nethserver-backup-config-2.5.2-1.ns7.noarch
nethserver-firewall-base-ui-3.18.2-1.ns7.noarch
nethserver-cgp-2.4.1-1.ns7.noarch
nethserver-nut-1.5.5-1.ns7.noarch
nethserver-phonehome-1.4.0-1.ns7.noarch
nethserver-lib-2.2.11-1.ns7.noarch
nethserver-cockpit-lib-1.10.9-1.ns7.noarch
nethserver-lang-cockpit-1.4.6-20.ns7.noarch
nethserver-mail-getmail-2.31.6-1.ns7.noarch
nethserver-cockpit-1.10.9-1.ns7.noarch
nethserver-lang-it-1.4.6-20.ns7.noarch
nethserver-ntp-1.1.3-1.ns7.noarch
nethserver-ddclient-2.0.5-1.ns7.sdl.noarch
nethserver-cups-1.2.3-1.ns7.noarch
nethserver-nethforge-release-7-3.ns7.noarch
nethserver-postgresql12-1.0.0-1.ns7.noarch
nethserver-release-7-19.ns7.noarch
nethserver-backup-data-1.7.6-1.ns7.noarch
nethserver-subscription-ui-3.6.8-1.ns7.noarch
nethserver-ndpi-1.3.4-1.ns7.noarch
nethserver-avahi-1.1.0-1.ns7.noarch
nethserver-net-snmp-1.1.0-1.ns7.noarch
nethserver-yum-1.4.1-1.ns7.noarch
nethserver-php-1.3.0-1.ns7.noarch
nethserver-vpn-ui-1.7.2-1.ns7.noarch
nethserver-dnsmasq-1.7.2-1.ns7.noarch
nethserver-firewall-base-3.18.2-1.ns7.noarch
nethserver-mail-server-2.31.6-1.ns7.noarch
nethserver-mail-filter-2.31.6-1.ns7.noarch
nethserver-mail-disclaimer-2.31.6-1.ns7.noarch
nethserver-mattermost-1.7.9-1.ns7.x86_64
nethserver-lang-en-1.4.6-20.ns7.noarch
nethserver-base-3.9.0-1.ns7.noarch
nethserver-antivirus-1.6.0-1.ns7.noarch
nethserver-smartd-1.1.0-1.ns7.noarch
nethserver-openssh-1.8.0-1.ns7.noarch
nethserver-unbound-1.1.1-1.ns7.noarch
nethserver-fail2ban-1.7.3-1.ns7.noarch
nethserver-sssd-1.7.1-1.ns7.noarch
nethserver-ejabberd-1.8.4-1.ns7.noarch
nethserver-ipsec-tunnels-1.2.4-1.ns7.noarch
nethserver-pulledpork-2.1.7-1.ns7.noarch
nethserver-dante-1.0.6-1.ns7.noarch
nethserver-ntopng-3.1.3-1.ns7.noarch
nethserver-mrmarkuz-0.0.1-6.ns7.noarch
nethserver-httpd-3.12.2-1.ns7.noarch
nethserver-lsm-1.2.4-1.ns7.noarch
nethserver-collectd-3.1.1-1.ns7.noarch
nethserver-openvpn-1.15.0-1.ns7.noarch
nethserver-wireguard-1.0.0-2.ns7.noarch
nethserver-stephdl-1.1.9-1.ns7.sdl.noarch
nethserver-diagtools-1.0.4-1.ns7.noarch
nethserver-mail-smarthost-2.31.6-1.ns7.noarch
nethserver-subscription-3.6.8-1.ns7.noarch
nethserver-netdata-2.0.2-1.ns7.noarch
nethserver-httpd-admin-service-2.7.0-1.ns7.noarch

and asking for crony this is the answer…

 systemctl status cronyd
Unit cronyd.service could not be found.

This is strange because…


Service seems there, but if requesting any cro* service, this is the answer.

status cro*
● crond.service - Command Scheduler
   Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2022-04-15 11:35:48 CEST; 3h 35min ago
 Main PID: 1265 (crond)
   CGroup: /system.slice/crond.service
           └─1265 /usr/sbin/crond -n

Apr 15 11:35:48 not.your.concern systemd[1]: Started Command Scheduler.
Apr 15 11:35:49 not.your.concern crond[1265]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 79% if used.)
Apr 15 11:35:51 not.your.concern crond[1265]: (CRON) INFO (running with inotify support)

@pike thank you for your answer… It works on all my KVMs but for the Container I had to update systemd to get a centos7 container-template up and running under Proxmox.

pct enter YOURCONTAINERID
dhclient
wget https://copr.fedorainfracloud.org/coprs/jsynacek/systemd-backports-for-centos-7/repo/epel-7/jsynacek-systemd-backports-for-centos-7-epel-7.repo -O /etc/yum.repos.d/jsynacek-systemd-centos-7.repo
yum update systemd

Maybe this is the reason that the service cant start, I dont now…

May I assume that you “nethfied” a pre-cooked CentOS7 recipe for ProxMox?

Yes, I used a Centos7 Container-template and installed it under Proxmox, finally Nethserver on it…

Edit: Maybe this script could work

LXC uses the hypervisors time and chronyd wants to change the system clock which isn’t possible, therefore chronyd stops.

You could try to add -x to the chronyd options in /etc/sysconfig/chronyd and restart chronyd to apply the option:

# Command-line options for chronyd
OPTIONS="-x"

From the manpage:

-x

This option disables the control of the system clock. chronyd will not try to make any adjustments of the clock. It will assume the clock is free running and still track its offset and frequency relative to the estimated true time. This option allows chronyd to run without the capability to adjust or set the system clock (e.g. in some containers) in order to operate as an NTP server. It is not recommended to run chronyd (with or without -x) when another process is controlling the system clock.

1 Like

Hi Markus, yes this looks good, also under the GUI:

Thank you!

1 Like