| Re: Re: [chrony-dev] Issue about chronyd synchronize to local clock |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
As mentioned, do you have the option rtcsync in your chrony.conf file?
Synchronizing to itself as Miroslav mentioned is not a good idea, as it keeps
ratchting up its stratum.
Is your server linked to the internet? Ie, do you have outside sources for the
time? Of is yours a little isolated island of machines? You say "my database".
Did you write the database program, in which case you could remove the test
for ntp sync, since you apparently do not really care if it is synced or not.
Or as Miroslav suggests, just turn the sync flag on with adjtimex every
minute.
On Thu, 25 Jun 2020, xqmeng80@xxxxxxxxxxx wrote:
I have a server cluster made of a number of machines, and I just choose one from them to be the NTP server. then all
other machines synchronize time to
the server. My application runs on every machine of the cluster, and the app will not work if it detected 'NTP not
synchronized status', so I have to make
the machine which act the role the NTP server synchronize to itself, but the status of the machine will be not
synchronized after several hours and will not become synchronized any more.
________________________________________________________________________________________________________________________
From: Bill Unruh
Date: 2020-06-25 23:10
To: chrony-dev
Subject: Re: Re: [chrony-dev] Issue about chronyd synchronize to local clock
On Thu, 25 Jun 2020, xqmeng80@xxxxxxxxxxx wrote:
> Is there a way or some configuration to make chronyd client always successfully synchronize to itself.
Why? Your database program is designed to only work if the system clock is
synchronized to UTC. It seems that you want to break that, and wnat to use
chrony to help you do that. The directive rtcsync should switch on that flag
when the system clock really is synchronized. Is that not what you want? Or
you can take Miroslav's advice and periodically (eg every minute if necessary)
use adjtimex to switch off that flag. Or hack the kernel code to never
switch it off. Or hack the database code to stop checking on that flag.
>
>
_____________________________________________________________________________________________________________________
>
> From: Miroslav Lichvar
> Date: 2020-06-25 22:54
> To: chrony-dev
> Subject: Re: Re: [chrony-dev] Issue about chronyd synchronize to local clock
> On Thu, Jun 25, 2020 at 10:44:29PM +0800, xqmeng80@xxxxxxxxxxx wrote:
> > As the application runs on the NTP server machine, time on the machine is thinked accurate. I just can't
> figure out why synchonizing to itself will make
> > the NTP synchronization status becomes No after several hours.
>
> Because the NTP stratum will increase with each iteration in the loop
> and the client will stop synchronizing when it reaches 16. Then
> it will just drift and when the root dispersion is too large, the
> clock will be considered "unsynchronized".
>
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
> For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
>
>
>