Hi everyone,
From one of my servers, after 5 minutes Logged into Proxmox GUI, the session is invalidated and I have to login again.
I'm using the lastest Proxmox VE 6 and I can confirm that time is synchronized.
I've seen a few other posts here about the same topic, however, none of them have the solution.
From one of my servers, after 5 minutes Logged into Proxmox GUI, the session is invalidated and I have to login again.
I'm using the lastest Proxmox VE 6 and I can confirm that time is synchronized.
Code:
# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-10 (running version: 6.2-10/a20769ed)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.3.13-3-pve: 5.3.13-3
pve-kernel-5.3.13-2-pve: 5.3.13-2
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
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.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-1
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-11
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
Code:
# timedatectl
Local time: Thu 2020-07-30 03:19:18 -03
Universal time: Thu 2020-07-30 06:19:18 UTC
RTC time: n/a
Time zone: America/Bahia (-03, -0300)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Code:
# systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-daemon.conf
Active: active (running) since Thu 2020-07-30 02:11:50 -03; 1h 4min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 2169 (systemd-timesyn)
Status: "Synchronized to time server for the first time 162.159.200.1:123 (2.debian.pool.ntp.org)."
Tasks: 2 (limit: 4915)
Memory: 2.5M
CGroup: /system.slice/systemd-timesyncd.service
└─2169 /lib/systemd/systemd-timesyncd
Jul 30 02:11:50 br08 systemd[1]: Starting Network Time Synchronization...
Jul 30 02:11:50 br08 systemd[1]: Started Network Time Synchronization.
Jul 30 02:12:20 br08 systemd-timesyncd[2169]: Synchronized to time server for the first time 162.159.200.1:123 (2.debian.pool.ntp.org).I've seen a few other posts here about the same topic, however, none of them have the solution.
