PROXMOX 6.1-2 on Dell 1950 can't fix time

[joceravolo]

Hi,

I am testing Proxmox with some Dell Servers.
On the Dell PowerEdge 1950 I can't fix the time. The BIOS time is correct, the TimeZone is correct.
I tried to look for information on the web and I could not find anything applicable.
Thanks in advance!

Version:

Last login: Fri May 15 11:42:32 EDT 2020 on pts/0
Linux mox1 5.3.10-1-pve #1 SMP PVE 5.3.10-1 (Thu, 14 Nov 2019 10:43:13 +0100) 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.
root@mox1:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

TimeDateCtl Status:

root@mox1:~# timedatectl status
               Local time: Fri 2020-05-15 12:03:32 EDT
           Universal time: Fri 2020-05-15 16:03:32 UTC
                 RTC time: Fri 2020-05-15 16:03:32
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

tcpdump:

root@mox1:~# tcpdump udp port 123 -t
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), capture size 262144 bytes
IP 192.168.1.168.ntp > 51.137.137.111.ntp: NTPv3, Client, length 48
IP 51.137.137.111.ntp > 192.168.1.168.ntp: NTPv3, Server, length 48
^C
2 packets captured
2 packets received by filter
0 packets dropped by kernel

 

[LnxBil]

I'm missing what the system should do or in what way the time is wrong. Can you elaborate?

 

[joceravolo]

I'm missing what the system should do or in what way the time is wrong. Can you elaborate?

I am sorry. The time is consistently 4 hours behind.

 

[CRCinAU]

Time zone: America/New_York (EDT, -0400)

That'd be why.

 

[joceravolo]

That'd be why.

I don't understand. I installed another node and the same Time Zone has the correct time.

 

[CRCinAU]

I'm guessing the UTC time you have set is correct as the local time - so when the timezone conversion happens, you end up getting the timezone correction twice...

Make sure your BIOS time is in UTC and try that...

 

[joceravolo]

One thing that I noticed is this
on the node with a problem:

System clock synchronized: no

On the new node


System clock synchronized: yes