| RE: [chrony-users] Can't synchronise: no majority |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] Can't synchronise: no majority
- From: Niko Delarich <ndelarich@xxxxxxxxxx>
- Date: Thu, 26 Mar 2020 09:48:03 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=loytec.com; dmarc=pass action=none header.from=loytec.com; dkim=pass header.d=loytec.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:X-MS-Exchange-SenderADCheck; bh=zD6e+mIoRbHFekyrlAQswyfGbputWG3ykg0FcE7/T6U=; b=Mj1qxu4OZJzD+CQVhTxYZkIOTjjMj/ya8lgvoA4ymZvHv3mthQULdvP5JSinwtysuh6Ul9+saZ9SK2spXyRaMy8fpT64c8TpyqdqJ0GpClYTjr5Fk5NeroT7hzETJjAk5gnj9F0s0snJxXJlnwz3O5GdO16oYHbni6ehtcpN5rL9K6vcUjqm18tLWqOCVD0yKVG66oR4HAlDBGA1mQwaOKPVsP8IWMem8Yz0CDbMZ3PBF49G3plMQ9wJr0/UpncKE0u/8hxzkIX66erHRgOixStGTA7e9zhPoLJ4juKtoOw24QgzQspjWGLsTRvLpZzIFdGsghgyAOIwsQCzDzhqEA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=He1evV7+TSnq8y5DWBGkUWxcbulRxUcUOxwXkxKx4zi70SEnqZ+zVnqCBCQ6eOB0RelhfaG9MbmlL+nNu5pereeYZzc1WFdVYH/A82ehmVMGUrp/DToUo1GszieFXwYSoryND3irnik9bK1F8EVnl0S3gBNPvC//r8jYGtOB3Z4z9GSDjeUhBfRCF6O7SA2JeLIG+EMHb1dNMh6WLTgCSlj9HErVN8JMSO/CySsV0jE+CJaGliUlRclVbEYVvN8/inWWfeRSuTyo8rgmDl8Ks3y+pzuKE2ozmYRiqg/fJtIuLYIoaREKcGYffRsa5tijF768mO9JHSJsiAvXDc+9Zw==
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=ndelarich@xxxxxxxxxx;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loytec.com; s=Delta2019; t=1585216091; bh=zD6e+mIoRbHFekyrlAQswyfGbputWG3ykg0FcE7/T6U=; h=From:To:Date; b=Zz00bIHnuEiVDnQ/C/8EQ+JmrneRcop0+4MDZ4tNrNUyVMfYpAx3g3OiTJzbDR4Tq AStBcOQYsh9eNnkMCptm/5kTk0RDUSmLMXbK9hLMWvN+VX1RsQCIAhEzj8NNFoHNs+ 0FsSJz7iNRRUVDPImBAAClRCIMTeQ1xKpdZ11Fns=
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=DeltaO365.onmicrosoft.com; s=selector1-DeltaO365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zD6e+mIoRbHFekyrlAQswyfGbputWG3ykg0FcE7/T6U=; b=gI+HirFtY3tH0QOfDAjPSdPG+OZLxa2ymBsxu0wF73I9x8KTjD6devI7wfN52WowUjVf32/8mg0khWYFUxAvUo9VMgXOxzqzATEQaIRzqw/t94uHEWTYlLaXqBy0uIgr2XAxjCow0rIGgFQ43TKi+vLSejjOyauoGGVpQet1sBE=
- Thread-index: AdYCp8+z3831PjiCQ56ikQLoQDOrnwAAt0MAAAF5fNA=
- Thread-topic: [chrony-users] Can't synchronise: no majority
Thank you all for your responses!
I agree that adding a third server or disabling the bad server is probably the best way to fix this but I'm not sure our customer will like this answer since NTP apparently works correctly on a lot of other devices in their network and it even worked with our devices before we switched from openntp to chrony...
I'm going to try to patch the source code to make chrony choose the better server (based on score) in the "no majority" case.
Thanks again!
Niko
> -----Original Message-----
> From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
> Sent: Mittwoch, 25. März 2020 14:39
> To: chrony-users@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [chrony-users] Can't synchronise: no majority
>
> On Wed, Mar 25, 2020 at 01:22:11PM +0000, Niko Delarich wrote:
> > I know the situation is not ideal and the customer should probably just use
> better servers but shouldn't chrony just pick the "better" of the two servers
> in this case (#2 with stratum 3)?
> > There's a comment in sources.c:869 which seems to indicate it should:
> > The first case is just bad luck - we need extra sources to
> > detect the falseticker, so just make an arbitrary choice based
> > on stratum & stability etc.
>
> If I understand that comment correctly, it is for the example with three
> servers, where two and two agree with one another, so that's a different
> case, and the "arbitrary choice" is for selecting the system peer, not a
> falseticker.
>
> > Or is there maybe a configuration option I'm missing? Setting one of the
> sources to "trusted" manually is most likely not an option for us since the
> servers may be assigned by a DHCP server.
>
> No, I don't think there is a non-source option that would force chronyd to
> select a source in this case.
>
> They should disable the bad server.
>
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.