Falsche Systemzeit Edomi-Server

[eimax]

Ich hoffe das mir jemand weiterhelfen kann. Mein Edomi hat seit kurzem ein Zeitproblem, was sich dahingehend äußert, dass die EDOMI-Systemzeit falsch ist. Nach einem Neustart ist sie anfangs korrekt, läuft dann jedoch weg. Hat einer noch eine Idee was das Problem sein kann? Edomi als VM im Proxmox. HWClock läuft laut Ausgabe korrekt.

hier der Auszug aus der /etc/ntp.conf

# For more information about this file, see the man pages

# ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5).




driftfile /var/lib/ntp/drift




# Permit time synchronization with our time source, but do not

# permit the source to query or modify the service on this system.

restrict default kod nomodify notrap nopeer noquery

restrict -6 default kod nomodify notrap nopeer noquery




# Permit all access over the loopback interface. This could

# be tightened as well, but to do so would effect some of

# the administrative functions.

restrict 127.0.0.1

restrict ::1




# Hosts on local network are less restricted.

#restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap




# Use public servers from the pool.ntp.org project.

# Please consider joining the pool (http://www.pool.ntp.org/join.html).

#server 0.centos.pool.ntp.org iburst

#server 1.centos.pool.ntp.org iburst

#server 2.centos.pool.ntp.org iburst

#server 3.centos.pool.ntp.org iburst




#server ptbtime1.ptb.de

#server ptbtime2.ptb.de

#server ptbtime3.ptb.de




#broadcast 192.168.1.255 autokey # broadcast server

#broadcastclient # broadcast client

#broadcast 224.0.1.1 autokey # multicast server

#multicastclient 224.0.1.1 # multicast client

#manycastserver 239.255.254.254 # manycast server

#manycastclient 239.255.254.254 autokey # manycast client




# Enable public key cryptography.

#crypto




includefile /etc/ntp/crypto/pw




# Key file containing the keys and key identifiers used when operating

# with symmetric key cryptography.

keys /etc/ntp/keys




# Specify the key identifiers which are trusted.

#trustedkey 4 8 42




# Specify the key identifier to use with the ntpdc utility.

#requestkey 8




# Specify the key identifier to use with the ntpq utility.

#controlkey 8




# Enable writing of statistics records.

#statistics clockstats cryptostats loopstats peerstats




# Disable the monitoring facility to prevent amplification attacks using ntpdc

# monlist command when default restrict does not include the noquery flag. See

# CVE-2013-5211 for more details.

# Note: Monitoring will not be disabled with the limited restriction flag.

disable monitor




server 192.168.0.1

NTP-Server spielt hierbei eine Fritzbox, bisher gab es hier nie Probleme. Selbst wenn ein öffentlicher NTP-Server verwendet wird läuft die Zeit davon:

[root@edomi ~]# timedatectl status

Local time: Mo 2022-03-21 10:46:26 CET

Universal time: Mo 2022-03-21 09:46:26 UTC

RTC time: Mo 2022-03-21 09:51:20

Time zone: Europe/Berlin (CET, +0100)

NTP enabled: yes

NTP synchronized: no

RTC in local TZ: no

DST active: no

Last DST change: DST ended at

So 2021-10-31 02:59:59 CEST

So 2021-10-31 02:00:00 CET

Next DST change: DST begins (the clock jumps one hour forward) at

So 2022-03-27 01:59:59 CET

So 2022-03-27 03:00:00 CEST

[root@edomi ~]# hwclock

Mo 21 Mär 2022 10:51:26 CET -0.453342 Sekunden

[root@edomi ~]# ntpq -pn

remote refid st t when poll reach delay offset jitter

================================================== ============================

192.168.0.1 40.95.204.66 3 u 50 64 1 0.988 294204. 0.000

[root@edomi ~]# ntpstat

unsynchronised

polling server every 8 s