[SOLVED] ntp issue with proxmox 7

[Runningman2552]

I have a small private proxmox 7 running on a micro server. latey I am seeing more and more ntp errors from my check_mk monitoring on the proxmox server:

Host    host (host)
Service    NTP Time
Event    OK → WARNING
Address    192.168.1.200
Date / Time    Wed Mar 22 07:06:53 CET 2023
Summary    Offset: 0.3375 ms, Stratum: 2, Time since last sync: 30 minutes 3 seconds (warn/crit at 30 minutes 0 seconds/1 hour 0 minutes)WARN
Details    NTP servers: (131.188.3.223)
Reference ID: 83BC03DF (131.188.3.223)
Offset: 0.3375 ms
Stratum: 2
Time since last sync: 30 minutes 3 seconds (warn/crit at 30 minutes 0 seconds/1 hour 0 minutes)WARN
Host Metrics    rta=0.677ms;200.000;500.000;0; pl=0%;80;100;; rtmax=1.508ms;;;; rtmin=0.404ms;;;;
Service Metrics    offset=0.33748;200;500;0;

what kind of issue is this on the proxmox side ?

 

[Chris]

Hi,
seems your system time is drifting because there is no resync of the time via NTP. Proxmox uses chorny for time sychronization, please check the status of the service via systemctl status chrony.service and post the output here.

 

[Runningman2552]

root@host:~# systemctl status chrony.service
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-03-20 14:36:26 CET; 2 days ago
       Docs: man:chronyd(8)
             man:chronyc(1)
             man:chrony.conf(5)
    Process: 2569 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
   Main PID: 2680 (chronyd)
      Tasks: 2 (limit: 38277)
     Memory: 2.6M
        CPU: 660ms
     CGroup: /system.slice/chrony.service
             ├─2680 /usr/sbin/chronyd -F 1
             └─2689 /usr/sbin/chronyd -F 1

Mar 20 14:36:26 host systemd[1]: Starting chrony, an NTP client/server...
Mar 20 14:36:26 host chronyd[2680]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN>
Mar 20 14:36:26 host chronyd[2680]: Frequency 0.367 +/- 0.005 ppm read from /var/lib/chrony/chrony.drift
Mar 20 14:36:26 host chronyd[2680]: Using right/UTC timezone to obtain leap second data
Mar 20 14:36:26 host chronyd[2680]: Loaded seccomp filter
Mar 20 14:36:26 host systemd[1]: Started chrony, an NTP client/server.
Mar 20 14:36:34 host chronyd[2680]: Selected source 131.188.3.223 (2.debian.pool.ntp.org)
Mar 20 14:36:34 host chronyd[2680]: System clock TAI offset set to 37 seconds
Mar 21 10:46:54 host chronyd[2680]: Selected source 167.235.228.35 (2.debian.pool.ntp.org)
Mar 21 16:49:35 host chronyd[2680]: Selected source 131.188.3.223 (2.debian.pool.ntp.org)

 

[Chris]

root@host:~# systemctl status chrony.service
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-03-20 14:36:26 CET; 2 days ago
       Docs: man:chronyd(8)
             man:chronyc(1)
             man:chrony.conf(5)
    Process: 2569 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
   Main PID: 2680 (chronyd)
      Tasks: 2 (limit: 38277)
     Memory: 2.6M
        CPU: 660ms
     CGroup: /system.slice/chrony.service
             ├─2680 /usr/sbin/chronyd -F 1
             └─2689 /usr/sbin/chronyd -F 1

Mar 20 14:36:26 host systemd[1]: Starting chrony, an NTP client/server...
Mar 20 14:36:26 host chronyd[2680]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN>
Mar 20 14:36:26 host chronyd[2680]: Frequency 0.367 +/- 0.005 ppm read from /var/lib/chrony/chrony.drift
Mar 20 14:36:26 host chronyd[2680]: Using right/UTC timezone to obtain leap second data
Mar 20 14:36:26 host chronyd[2680]: Loaded seccomp filter
Mar 20 14:36:26 host systemd[1]: Started chrony, an NTP client/server.
Mar 20 14:36:34 host chronyd[2680]: Selected source 131.188.3.223 (2.debian.pool.ntp.org)
Mar 20 14:36:34 host chronyd[2680]: System clock TAI offset set to 37 seconds
Mar 21 10:46:54 host chronyd[2680]: Selected source 167.235.228.35 (2.debian.pool.ntp.org)
Mar 21 16:49:35 host chronyd[2680]: Selected source 131.188.3.223 (2.debian.pool.ntp.org)

Okay, in that case your time should be correctly synced.

According to this post https://forum.checkmk.com/t/disable-ntp-time-warning-in-checkmk-2-0/28415, you will get an alert if the time is not synced within a configured threshold value (it seems like 30 min in your case). So probably that is the case then, you can follow their suggestion and increase it to a higher value (they give 36min as value for a chrony default of maxpoll 10)

 

[Runningman2552]

Thx for your help, will try this.

 

[Runningman2552]

I set maxpoll to 8 as stated in the post you linked, seems ok now.

 

[Chris]

I set maxpoll to 8 as stated in the post you linked, seems ok now.

Glad to hear, please mark the thread as solved if you think the issue is fixed by the config change.