Hello,
This morning , one of my node suddendly changed is time going 5 hours back.
Here is the log :
syslog:Jan 20 09:39:26 X systemd-timesyncd[1646]: Timed out waiting for reply from 138.236.128.36:123 (2.debian.pool.ntp.org).
syslog:Jan 20 03:47:01 X systemd-timesyncd[1646]: Synchronized to time server for the first time 86.108.190.23:123 (2.debian.pool.ntp.org).
syslog:Jan 20 04:31:52 X systemd[1]: systemd-timesyncd.service: Succeeded.
syslog:Jan 20 10:24:17 X systemd-timesyncd[29261]: Synchronized to time server for the first time 94.23.2.80:123 (0.debian.pool.ntp.org).
I have restarted manualy systemd-timesyncd at 10h24, and date time synced right... 10h24.
The IP 86.108.190.23 is resolved as testntp2.superonline.net, this maybe explain that...
I checked this server specific NTP service after 1h, time was ok... so it was very punctual problem.
Any experience on this ?
Having wrong time setted , kills https, proxmox auth, this can just stop many online service, license server, ect...
You can check NTP is syncing with timedatectl, but in my case it was always synced...
systemd-timesyncd is configured statically by default with 4 NTP servers, but how is this possible , trusting juste one for 5h drift ?
Thanks for your comments
Regards
This morning , one of my node suddendly changed is time going 5 hours back.
Here is the log :
syslog:Jan 20 09:39:26 X systemd-timesyncd[1646]: Timed out waiting for reply from 138.236.128.36:123 (2.debian.pool.ntp.org).
syslog:Jan 20 03:47:01 X systemd-timesyncd[1646]: Synchronized to time server for the first time 86.108.190.23:123 (2.debian.pool.ntp.org).
syslog:Jan 20 04:31:52 X systemd[1]: systemd-timesyncd.service: Succeeded.
syslog:Jan 20 10:24:17 X systemd-timesyncd[29261]: Synchronized to time server for the first time 94.23.2.80:123 (0.debian.pool.ntp.org).
I have restarted manualy systemd-timesyncd at 10h24, and date time synced right... 10h24.
Code:
systemctl restart systemd-timesyncd
The IP 86.108.190.23 is resolved as testntp2.superonline.net, this maybe explain that...
I checked this server specific NTP service after 1h, time was ok... so it was very punctual problem.
Any experience on this ?
Having wrong time setted , kills https, proxmox auth, this can just stop many online service, license server, ect...
You can check NTP is syncing with timedatectl, but in my case it was always synced...
systemd-timesyncd is configured statically by default with 4 NTP servers, but how is this possible , trusting juste one for 5h drift ?
Thanks for your comments
Regards