clock skew detected

[powersupport]

Hi,

Please have a look at the error we are getting. May I know how can we resolve the isuue?

satonapx-sg1-n7.domain.com/Ceph Health Check is WARNING:
WARNING: MON_CLOCK_SKEW( clock skew detected on mon.satonapx-sg1-n4 )

Regards,

 

[mira]

Please provide the output of pveversion -v and systemctl status systemd-timesyncd.service.

 

[powersupport]

Linux satapx-sg1-n1 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Dec 4 11:23:05 2021 from 103.147.208.71
root@satapx-sg1-n1:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.4: 6.4-7
pve-kernel-5.3: 6.1-6
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph: 16.2.6-pve2
ceph-fuse: 16.2.6-pve2
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.6-pve1~bpo10+1

 

[powersupport]

zfsutils-linux: 2.0.6-pve1~bpo10+1
root@satapx-sg1-n1:~# systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-10-19 21:39:12 +08; 1 months 17 days ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 899 (systemd-timesyn)
Status: "Initial synchronization to time server 23.106.249.200:123 (3.debian.pool.ntp.org)."
Tasks: 2 (limit: 77090)
Memory: 1.4M
CPU: 6.638s
CGroup: /system.slice/systemd-timesyncd.service
└─899 /lib/systemd/systemd-timesyncd

Oct 19 21:39:12 satapx-sg1-n1 systemd[1]: Starting Network Time Synchronization...
Oct 19 21:39:12 satapx-sg1-n1 systemd[1]: Started Network Time Synchronization.
Oct 19 21:39:49 satapx-sg1-n1 systemd-timesyncd[899]: Initial synchronization to time server 159.138.166.199:123 (3.deb>
Oct 21 20:53:33 satapx-sg1-n1 systemd-timesyncd[899]: Timed out waiting for reply from 159.138.166.199:123 (3.debian.po>
Oct 21 20:53:33 satapx-sg1-n1 systemd-timesyncd[899]: Initial synchronization to time server 23.106.249.200:123 (3.debi>
lines 1-17/17 (END)

 

[icehq]

I'm new and I'm not an expert in Proxmox, but when I have clock skew, I remove the mon on this node and add it again - the clock skew disappears.

 

[mira]

Try switching to chrony [0]. With PVE 7 it is the new default for time synchronization as systemd-timesyncd only supports SNTP and users sometimes had clock skew issues because of that.

[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_time_synchronization