| Re: [chrony-users] Chrony not taking SOCKET data from Application |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony not taking SOCKET data from Application
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 3 May 2023 09:15:34 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683098137; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cwoaklJ2UIk4IXdhNV0enGzxZopav8zpjitcljRw66Q=; b=bRUzCAGNQKWyAgv48poSadWIcxCzAIbiqQ0S61cpMGJRL5tyapSw/FQzH8HiwanE5Gy1wt uhXeh0goZtXV7FG+lPmSEJ6bB3xwbg8BKbvKdpcmjT7e3iGSV2PEL4Fr5jDOkHcfFyOwsQ 9Z+XUoI4hZW2Q2aDhRCpVj8RbygoKOs=
On Wed, May 03, 2023 at 12:25:53PM +0530, sarveshwar k wrote:
> Hi Miroslav,
>
> > The measurement appears before you sent anything to the SOCK socket?
> Yes, before I sent anything to the SOCK.
I don't see that in the logs. The first SOCK sample in refclocks.log is
at "2023-01-01 04:27:32.008264". The first clock update in tracking.log is
"2023-01-01 04:27:35" with an offset of 53 milliseconds. That is the
initial offset you would see in the "chronyc sources" output before
the third sample is received and the clock is updated.
If you see the offset again after chronyd restart, it means there is
something else touching the clock. Maybe chronyd is started with the
-s option to set the clock from RTC?
--
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.