Search results

@Gaia I think this has nothing to do with the Proxmox version, have a look here, Post 21: https://forum.proxmox.com/threads/wrong-time-wrong-time-synchronisation.55208/page-2 regards, maxprox

HI, I found no solution to this, so I made one myself ;-) EDIT on 2019-07-13: ##shutdown the VM qm shutdown 106 ## edit the VMID in the storage line[for me from local-zfs:vm-106-disk-0 to local-zfs:vm-104-disk-0]: vim /etc/pve/nodes/name/qemu-server/106.conf ## rename the conf file: mv...

we have installed it on two single Servers with Supermicro MB: X11SCM-F, with ZFS Raid10, without any problems (OT: We have to disable the High Precision Event Timer (HPET) Support in the BIOS, otherwise NTP and the Clock is messed up)

Hi Stoiko, this settings I do not found in the BIOS of the X11SCM-F But as you see above, with your help, the problem is solved, Thank you! Has anybody one Tip for me: how to find an overview and the meaning of all the Supermicro Server Boards BIOS features and it settings, in connection with...

Hi, first of all, many thanks to the Proxmox support, without the help from Mr. Stoiko Ivanov, I 'd never find this solution! In short: I went to the BIOS (Supermicro X11SCM-F) ACPI Settings - High Precision Event Timer (HPET), and switched it from enabled (default) to disable... and everything...

Hi Udo, No I don't think so, In the BIOS the only thing I changed -after an BIOS and IPMI Update- was the Boot order. Do you have a special / concrete setting for witch I have to look for in the BIOS? regards, maxprox

okay, Now I install the same Proxmox 5.4 on the concernd Supermcro X11SCM-F Server, (but not on the wiped 4x4TB ZFSRaid10, on a separate SATA SSD) After the fresh installation I copy & past again the same: /etc/systemd/timesyncd.conf On this fresh Proxmox: proxmox-ve: 5.4-1 (running kernel...

Next Test: Now I Install with the same Proxmox 5.4 USB Boot stick on an old Backup-System-PC .... everything is running as it shuld, the time synchronization works with the same (copy & past) /etc/systemd/timesyncd.conf Now the output line: "NTP synchronized: yes" shows "YES" The clock adjust...

again I have a look at the Firewall rules and LOGs - I see nothing that help. try several NTP Server in the /etc/systemd/timesyncd.conf and have a look at the tcpdump (represented below). Restart the timesyncd many times and so on, but with the problem nothing changed ... root@electroprox ~ #...

No, not on the Proxmox installaiton. The command "timedatectl set-ntp true" only change the output line before: " from "Network time on: no" to Network time on: yes. But the output line "NTP synchronized: no" stay always / ever: root@electroprox ~ # timedatectl status Local time: Tue...

On our Debian Buster Test System we get: root@debianTEST:~# timedatectl show root@debianTEST:~# timedatectl show Timezone=Europe/Berlin LocalRTC=no CanNTP=yes NTP=yes NTPSynchronized=yes TimeUSec=Tue 2019-06-18 17:16:14 CEST RTCTimeUSec=Tue 2019-06-18 17:05:19 CEST everything like it should...

Hi Aaron, I thank you for following this (fucking) issue! :) in the past, this command we try more than once with: timedatectl set-ntp true timedatectl set-ntp on timedatectl set-ntp 1 but it only change the line: System clock synchronized: no to System clock synchronized: yes an not the line...

Restart, without an answer: root@electroprox ~ # systemctl restart systemd-timesyncd.service timedatectl status: root@electroprox ~ # timedatectl status Local time: Tue 2019-06-18 15:48:51 CEST Universal time: Tue 2019-06-18 13:48:51 UTC RTC time: Tue 2019-06-18 13:48:58...

root@electroprox ~ # cat /etc/systemd/timesyncd.conf ... [Time] NTP=172.21.8.200 ## our local NTP Server (Debian Samba4 DC) FallbackNTP=0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org ##NTP=0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org...

Thank you for pointing that out. However, it's not because the connections all work without problems. root@electroprox ~ # 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...

Hello Aaron, thanks for your reply. it may also be important: - our Firewall has a "deny all" rule, for time sync only the default udp port 123 is open. - the time synchronization in Proxmox is only for itself We changed from chrony to the time synchronization like described in the wiki and...

Hello, We have a very strange Problem on two same new Serverinstallations: The three Times form hwclock, date and NTP are changing more or less, for which I can not see any reason. Hardware (two servers with the same Supermicro board): 2x a new Supermicro Board X11SCM-F with the last BIOS only...

da bin ich dann leider raus, ich arbeite zur Zeit immer von ZFS nach ZFS dann ist die Technik klar und funktioniert Aber guck doch mal ob das hilft, die Synchronisieren in die Amazon Cloud: https://forum.rclone.org/t/recommended-setup-for-cold-storage-archive/5925

HI Erwin Müller, bei so einem Porblem würde ich zuerst mal über das Proxmox WebGUI, das in den Letzten VersionsUpdates immer mächtiger geworden ist, bemühen. Schau mal, ob all deine gewünschten Storages unter: Server-View - Datacenter - Storage zu sehen sind? Wenn nein per Schaltfläche Add...

VMs aus Snapshots Wiederherstellen Das war doch mehr Arbeit als gedacht, umso besser, das unbedingt VOR dem Ernstfall durchgetestet zu haben. Zum Beispiel habe ich so erst bemerkt, dass ich meine selbstbenannten Volumes auf der Backup-Maschine für Proxmox zunächst unbrauchbar gemacht hatte...