[chrony-users] Decision algorithm, compatibility

[chrony-users] Decision algorithm, compatibility

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]

To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
Subject: [chrony-users] Decision algorithm, compatibility
From: Uwe Fechner <uwe.fechner@xxxxxxxxxx>
Date: Wed, 15 Sep 2021 16:18:02 +0000
Accept-language: en-US
Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nl.abb.com; dmarc=pass action=none header.from=nl.abb.com; dkim=pass header.d=nl.abb.com; arc=none
Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LZ+eI6tY5NZn92jtrgF+ZteTMBrgGB2YWB6fxgEr9Zk=; b=Skjad1wP2zfXH19GomZPCQoHyYcb6dgZT2QTBbTy7TxxayFapVZDMGLf3rpGb5xdJNW2hQXDZzOtaO8CtHLmVgbTGtQCttAUVfCbpOmugDu0cP+Rw32SqEaBqwuZyQ/+HzT+3Ha7Xs/s6WK0eW0Dp3LYLQi8cKEEpC0z8r1sRB782r60Dw68d+yKJCP9ZfHfHny071MB1rNIukmoZPkgnjcpVmdFTXSlGbv3mEZo/GdKhYVA2MNSUwfloHrDRjouhuLYddgCEQfopzBdl+YzQBgMpgzhmHpjKqcyejBueTdeFRtqOikRbFb7eMPa2Ruvz45eMxKRyNeBSH1YcV8T2A==
Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Hn2lyjFt3EPtlnDdZBNOcaKlI2hatjXm5wXoirrZ2+vWRljtOX8/JIbWnT/ZkA7ahrQJQxFK8fBa6BUQBSQhBrf3cQsLG3VNE4NFvEL+a99h4cbTkT46y1CPrytlgKUMaYWL0C/VLXBxP8L9DTxs0RwE93QwCRKS0+yebywRun/UyxuhxexWF1/4U2dDOtFBqkm97t3nvivGzmy/eKY0LWsF6v5pIv+rGDqU6feXDgzHoNnlMUlEZt4qUsVBQLc/NBjHKPm77hG0tzCIlkA8tTU30XUeYZMFtKF8V4iHYFtqrbs6Ay8wfSG8JFzavOiC9iTuWLOYDuxcLgIEt+ry5g==
Authentication-results: chrony.tuxfamily.org; dkim=none (message not signed) header.d=none;chrony.tuxfamily.org; dmarc=none action=none header.from=nl.abb.com;
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nl.abb.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LZ+eI6tY5NZn92jtrgF+ZteTMBrgGB2YWB6fxgEr9Zk=; b=VC0Jaml7zXNHT10WC69D2LmWax1jnPvgB9ZTho1K5DsPXfR+ZhXihWJhkqLk7BdFl8xFCFGDT0musuGk6vkYQRIrapY3LB28kH5ZzDuchOd8KGqUTPEcZGAWo1551NEeLD2HeYkVPEogjHMfF8YAKMyIgOvpNuHFrTptLLFVV++sc4I4UUYk9wYqQuXYiD/VSsH51XaHIqkEdvfVZ+Wvt4HipRP2GcTz1YzBRQFkH9MLtCJLWT4SsLGZcQ3ul/tcPbtnxsUQJZbyzUWv3bTqSGxqa9+JCVeaDLNB59F9AoZr1zJnXKgWTEBMJpL+WEksEtNTo1Hq5+HTkjHpvQksXA==
Suggested_attachment_session_id: bb674441-4e2c-7013-e59a-87cad5c50332
Thread-index: AQHXqkz6PNYMtFFkXUyD1R+LCzF5EQ==
Thread-topic: Decision algorithm, compatibility

Hello,

I am using the following chrony.conf file:

server time..cloudflare.com nts offline

server nts1..time.nl iburst nts offline

server ptbtime1.ptb.de nts offline

server nts.sth1.ntp.se iburst nts offline

server nts.sth2.ntp.se iburst nts offline

driftfile /var/lib/chrony/drift

makestep 1.0 3

rtcfile /var/lib/chrony/rtc

rtconutc

rtcautotrim 30

Ten hours after starting chrony I get the following status:

chronyc sources

MS Name/IP address Stratum Poll Reach LastRx Last sample

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

^* time.cloudflare.com 3 10 42 41m +2690us[+3783us] +/- 26ms

^- nts1.time.nl 2 9 377 389 +2364us[+2364us] +/- 67ms

^+ ptbtime1..ptb.de 1 10 20 95m +439us[+1470us] +/- 24ms

^+ sth1-ts.nts.netnod.se 2 10 377 201 -2001us[-2001us] +/- 35ms

^+ sth2-ts.nts.netnod.se 2 10 377 927 +1983us[+1983us] +/- 25ms

Why is cloudfare selected? It has the worst stratum AND a bad reach.

Any ideas?

Second question:

Why is the reach for cloudfare and ptbtime1 so bad? Is it a compatibility problem

or are the servers overloaded?

Thanks a lot for your good work!

Uwe

Follow-Ups:
- Re: [chrony-users] Decision algorithm, compatibility
  - From: Miroslav Lichvar

Messages sorted by: [ date | thread ]
Prev by Date: Re: [chrony-users] How to detect internet becoming available
Next by Date: Re: [chrony-users] Decision algorithm, compatibility
Previous by thread: Re: [chrony-users] How to detect internet becoming available
Next by thread: Re: [chrony-users] Decision algorithm, compatibility

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/