[SOLVED] Proxmox VE Incorrect Time

shr · 2025-10-12T06:53:30+0200

I tried

Code:

ln -sf /usr/share/zoneinfo/Etc/UTC /etc/localtime
hwclock --systohc
hwclock --systohc --utc

I also tried dpkg-reconfigure tzdata and set it to UTC

Code:

root@pve:~# timedatectl
               Local time: Thu 2025-06-26 04:42:15 UTC
           Universal time: Thu 2025-06-26 04:42:15 UTC
                 RTC time: Thu 2025-06-26 04:42:15
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
root@pve:~# diff /usr/share/zoneinfo/Etc/UTC /etc/localtime
root@pve:~# systemctl status chrony
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/usr/lib/systemd/system/chrony.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-06-25 15:41:51 UTC; 13h ago
 Invocation: 9a4fd969e5c14b5e9ea5fc059d015f6e
       Docs: man:chronyd(8)
             man:chronyc(1)
             man:chrony.conf(5)
    Process: 664 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
   Main PID: 744 (chronyd)
      Tasks: 2 (limit: 14110)
     Memory: 5.7M (peak: 6.4M)
        CPU: 61ms
     CGroup: /system.slice/chrony.service
             ├─744 /usr/sbin/chronyd -F 1
             └─748 /usr/sbin/chronyd -F 1

Jun 25 15:41:48 pve systemd[1]: Starting chrony.service - chrony, an NTP client/server...
Jun 25 15:41:51 pve chronyd[744]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +R>
Jun 25 15:41:51 pve chronyd[744]: Loaded 0 symmetric keys
Jun 25 15:41:51 pve chronyd[744]: Using leap second list /usr/share/zoneinfo/leap-seconds.l>
Jun 25 15:41:51 pve chronyd[744]: Frequency 11.629 +/- 0.021 ppm read from /var/lib/chrony/>
Jun 25 15:41:51 pve chronyd[744]: Loaded seccomp filter (level 1)
Jun 25 15:41:51 pve systemd[1]: Started chrony.service - chrony, an NTP client/server.
root@pve:~# timedatectl
               Local time: Thu 2025-06-26 04:43:03 UTC
           Universal time: Thu 2025-06-26 04:43:03 UTC
                 RTC time: Thu 2025-06-26 04:43:03
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
root@pve:~# diff /usr/share/zoneinfo/Etc/UTC /etc/localtime
root@pve:~# systemctl status chrony
● chrony.service - chrony, an NTP client/server
     Loaded: loaded (/usr/lib/systemd/system/chrony.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-06-25 15:41:51 UTC; 13h ago
 Invocation: 9a4fd969e5c14b5e9ea5fc059d015f6e
       Docs: man:chronyd(8)
             man:chronyc(1)
             man:chrony.conf(5)
    Process: 664 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
   Main PID: 744 (chronyd)
      Tasks: 2 (limit: 14110)
     Memory: 5.7M (peak: 6.4M)
        CPU: 61ms
     CGroup: /system.slice/chrony.service
             ├─744 /usr/sbin/chronyd -F 1
             └─748 /usr/sbin/chronyd -F 1

Jun 25 15:41:48 pve systemd[1]: Starting chrony.service - chrony, an NTP client/server...
Jun 25 15:41:51 pve chronyd[744]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Jun 25 15:41:51 pve chronyd[744]: Loaded 0 symmetric keys
Jun 25 15:41:51 pve chronyd[744]: Using leap second list /usr/share/zoneinfo/leap-seconds.list
Jun 25 15:41:51 pve chronyd[744]: Frequency 11.629 +/- 0.021 ppm read from /var/lib/chrony/chrony.drift
Jun 25 15:41:51 pve chronyd[744]: Loaded seccomp filter (level 1)
Jun 25 15:41:51 pve systemd[1]: Started chrony.service - chrony, an NTP client/server.
root@pve:~# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx9
intel-microcode: 3.20250512.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.3
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.7
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.9-1
proxmox-backup-file-restore: 4.0.9-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.0
proxmox-widget-toolkit: 5.0.4
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.7
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.16
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1
root@pve:~# dpkg-reconfigure tzdata

Current default time zone: 'Etc/UTC'
Local time is now:      Thu Jun 26 04:50:09 UTC 2025.
Universal Time is now:  Thu Jun 26 04:50:09 UTC 2025.

root@pve:~# timedatectl
               Local time: Thu 2025-06-26 04:51:05 UTC
           Universal time: Thu 2025-06-26 04:51:05 UTC
                 RTC time: Thu 2025-06-26 04:51:05
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
root@pve:~# date
Thu Jun 26 04:51:06 AM UTC 2025
root@pve:~#

On other node in the same cluster with correct time:

Code:

root@kitsune:~# timedatectl
               Local time: Sun 2025-10-12 04:47:35 UTC
           Universal time: Sun 2025-10-12 04:47:35 UTC
                 RTC time: Sun 2025-10-12 04:47:35
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
root@kitsune:~# diff /usr/share/zoneinfo/Etc/UTC /etc/localtime
root@kitsune:~# date
Sun Oct 12 04:47:57 AM UTC 2025
root@kitsune:~#

Onslow · 2025-10-12T10:56:11+0200

Welcome, shr!
What does chronyc sources -a -v return?

janus57 · 2025-10-12T10:59:16+0200

Hi,

Have you checked if the time is correct in BIOS first ?

What is the output of these commands :

chronyc tracking
chronyc sources

Best regards,

shr · 2025-10-12T11:00:24+0200

On incorrect node:

Code:

root@pve:~# chronyc sources -a -v

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^? ID#0000000001                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000002                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000003                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000004                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000005                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000006                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000007                 0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ID#0000000008                 0   6     0     -     +0ns[   +0ns] +/-    0ns
root@pve:~#

On another node with correct time:

Code:

root@kitsune:~# chronyc sources -a -v

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- waktos2.unpak.ac.id           3  10   377   741    +19ms[  +20ms] +/-   91ms
^* ntp.uii.net.id                1   9   377   140  +6783us[+7990us] +/- 6887us
^- 2.ntp.maxindo.net.id          3  10   277   316    +23ms[  +24ms] +/-   73ms
^- ns5.datautama.net.id          3  10   377   420    +30ms[  +32ms] +/-   98ms
root@kitsune:~#

shr · 2025-10-12T11:02:26+0200

janus57 said:
Hi,

Have you checked if the time is correct in BIOS first ?

What is the output of these commands :

Best regards,

I haven't checked the bios menu, it might be wrong

On incorrect node:

Code:

root@pve:~#  chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000026 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 11.629 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised
root@pve:~#  chronyc sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample              
===============================================================================
root@pve:~#

On another node with correct time:

Code:

root@kitsune:~# chronyc tracking
Reference ID    : CAA2200C (12.32.162.202.in-addr.arpa)
Stratum         : 2
Ref time (UTC)  : Sun Oct 12 08:56:23 2025
System time     : 0.001211948 seconds fast of NTP time
Last offset     : +0.001207110 seconds
RMS offset      : 0.000800661 seconds
Frequency       : 25.747 ppm fast
Residual freq   : +0.011 ppm
Skew            : 0.200 ppm
Root delay      : 0.010520995 seconds
Root dispersion : 0.002930732 seconds
Update interval : 1039.8 seconds
Leap status     : Normal
root@kitsune:~# chronyc sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample              
===============================================================================
^- 230.192.169.103.in-addr.>     3  10   377   890    +19ms[  +20ms] +/-   91ms
^* 12.32.162.202.in-addr.ar>     1   9   377   288  +6783us[+7990us] +/- 6887us
^- 102.74.110.119.in-addr.a>     3  10   277   464    +23ms[  +24ms] +/-   73ms
^- 13.31.89.203.in-addr.arpa     3  10   377   567    +30ms[  +32ms] +/-   98ms
root@kitsune:~#

janus57 · 2025-10-12T11:13:58+0200

Hi,

Dumb question, but have you tested that your "incorrect node" has DNS resolution and internet access ?
Can you try (default address on my chrony setup) :

Code:

host 2.debian.pool.ntp.org

Best regards,

shr · 2025-10-12T13:59:03+0200

Sorry, it was DNS.

I tested it again and it works.

Thanks

jdancer · 2025-10-12T14:58:37+0200

shr said:
Sorry, it was DNS...

It's always DNS.

When given the chance, use static IPs.

Search

Search

[SOLVED] Proxmox VE Incorrect Time

shr

New Member

Onslow

Active Member

janus57

Renowned Member

shr

New Member

shr

New Member

janus57

Renowned Member

shr

New Member

jdancer

Renowned Member

We value your privacy