From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: gaio@lilliput.linux.it
Cc: Alwin Antreich <alwin@antreich.com>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] NTP on PVE8...
Date: Mon, 19 Aug 2024 14:57:52 +0000 [thread overview]
Message-ID: <mailman.313.1724079504.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <46ebpk-rqm.ln1@leia.lilliput.linux.it>
[-- Attachment #1: Type: message/rfc822, Size: 5582 bytes --]
From: "Alwin Antreich" <alwin@antreich.com>
To: gaio@lilliput.linux.it
Cc: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] NTP on PVE8...
Date: Mon, 19 Aug 2024 14:57:52 +0000
Message-ID: <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com>
Hi Marco,
August 19, 2024 at 11:00 AM, "Marco Gaiarin" <gaio@lilliput.linux.it> wrote:
>
> Running 'pve7to8' i've catch:
>
> INFO: Checking for supported & active NTP service..
> WARN: systemd-timesyncd is not the best choice for time-keeping on servers, due to only applying updates on boot.
> While not necessary for the upgrade it's recommended to use one of:
> * chrony (Default in new Proxmox VE installations)
> * ntpsec
> * openntpd
>
> This is indeed mostly true, and in a cluster using a NTP daemon is a must.
> No doubt on that.
>
> But for a standalone server, systemd-timesyncd seems sufficient to me; and
> surely NOT 'only applying updates on boot': systemd-timesyncd sync time at
> regilar interval!
>
> PollIntervalMinSec=, PollIntervalMaxSec=
> The minimum and maximum poll intervals for NTP messages. Polling starts at the minimum poll interval, and is adjusted within the specified limits in response to received
> packets.
>
> Each setting takes a time span value. The default unit is seconds, but other units may be specified, see systemd.time(5). PollIntervalMinSec= defaults to 32 seconds and
> must not be smaller than 16 seconds. PollIntervalMaxSec= defaults to 34 min 8 s (2048 seconds) and must be larger than PollIntervalMinSec=.
>
systemd-timesyncd only uses one server to update its time, which can lead to time jumps when this NTP can't be accessed reliably. NTPs (eg. ntpd/chrony) are usually using 3+ servers to calculate a mean time and compensate for jitter and other delays. This allows to keep the time more stable and especially helps when Ceph or HA is enabled. ;)
I do recommend chrony for servers (physical or virtual).
Cheers,
Alwin
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-08-19 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 9:00 Marco Gaiarin
2024-08-19 14:57 ` Alwin Antreich via pve-user [this message]
[not found] ` <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com>
2024-08-19 15:50 ` Marco Gaiarin
2024-08-19 16:34 ` DERUMIER, Alexandre
2024-08-19 18:45 ` Olivier Benghozi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.313.1724079504.302.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.com \
--cc=gaio@lilliput.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox