Re: Chrony without daemon

--000000000000c882c9063b99ec20
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'll try to elaborate more about what I'm trying to achieve.
First of all, I'm very grateful for the detailed and well-explained
comments you made.
My objective is to monitor a drift between 3 NTP servers.

`chronyc sources` provides a wonderful and simple output just for that
purpose.
The issue I'm having is the following:
I'm using Openshift as my base, and my solution was to simply set a pod
with a chrony image and run the command,
sadly to my understanding, openshift pods doesn't have access to systemd,
meaning I can't set a chronyd daemon on the Pod it self.

"chrony tracking" also returns the error message "506 can't talk with
daemon".
Honestly I really think that because of that Openshift limitation I won't
find any way to actually run "chronyc sources".

I'm not completely understanding what it means to run `chronyd -U -x`.
I actually run it successfully, and it created a chronyd.pid, but "chronyc
sources" still return "506 Cannot talk to daemon"
Am I missing something?

=E2=80=AB=D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=9D =D7=92=D7=
=B3, 5 =D7=91=D7=90=D7=95=D7=92=D7=B3 2025 =D7=91-11:04 =D7=9E=D7=90=D7=AA =
=E2=80=AARob Janssen=E2=80=AC=E2=80=8F <=E2=80=AA
chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]=E2=80=AC=E2=80=8F>:=E2=80=AC

> My guess was that he was attempting monitoring of an existing chronyd
> outside
> his container.
> I have done that (way) in the past to monitor time service using nagios.
> I just installed (copied) the chronyc binary to the monitoring system,
> which
> itself was running ntpd, and made a check_chrony script that did a
> chronyc call (from a perl skeleton available for nagios).
> Probably not the most efficient way, but it works.  I used "chronyc
> tracking",
> of course with a -h parameter.
>
> But maybe I am completely wrong guessing his objectives... it is not very
> clear from the explanation.
>
> Rob
>
> On 2025-08-05 09:20, Mingye Wang wrote:
>
> So uh Rob gave a good explanation of how chrony works, but honestly:
> this smells like an "XY problem" to me. What are you attempting to do,
> actually, by getting `chronyc sources`? In other words, what
> information do you *really* need?
>
>
>

--000000000000c882c9063b99ec20
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"rtl"><div dir=3D"ltr">I&#39;ll try to elaborate more about what=
 I&#39;m trying to achieve.<br></div><div dir=3D"ltr">First of all, I&#39;m=
 very grateful for the detailed and well-explained comments you made.<br></=
div><div dir=3D"ltr">My objective is to monitor a drift between 3 NTP serve=
rs.<br><br></div><div dir=3D"ltr">`chronyc sources` provides a wonderful an=
d simple output just for that purpose.<br></div><div dir=3D"ltr">The issue =
I&#39;m having is the following:<br></div><div dir=3D"ltr">I&#39;m using Op=
enshift as my base, and my solution was to simply set a pod with a chrony i=
mage and run the command,</div><div dir=3D"ltr">sadly to my understanding, =
openshift pods doesn&#39;t have access to systemd, meaning I can&#39;t set =
a chronyd daemon on the Pod it self.<br><br></div><div dir=3D"ltr">&quot;ch=
rony tracking&quot; also returns the error message &quot;506 can&#39;t talk=
 with daemon&quot;.<br></div><div dir=3D"ltr">Honestly I really think that =
because of that Openshift limitation I won&#39;t find any way to actually r=
un &quot;chronyc sources&quot;.<br><br></div><div dir=3D"ltr">I&#39;m not c=
ompletely understanding what it means to run `chronyd -U -x`. <br></div><di=
v dir=3D"ltr">I actually run it successfully, and it created a chronyd.pid,=
 but &quot;chronyc sources&quot; still return &quot;506 Cannot talk to daem=
on&quot;</div><div dir=3D"ltr">Am I missing something?=C2=A0</div></div><br=
><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"rtl" class=3D=
"gmail_attr">=E2=80=AB=D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=
=9D =D7=92=D7=B3, 5 =D7=91=D7=90=D7=95=D7=92=D7=B3 2025 =D7=91-11:04 =D7=9E=
=D7=90=D7=AA =E2=80=AARob Janssen=E2=80=AC=E2=80=8F &lt;=E2=80=AA<a href=3D=
"mailto:chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]">chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]</a>=E2=80=AC=E2=80=
=8F&gt;:=E2=80=AC<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><u></u>

 =20
   =20
 =20
  <div>
    My guess was that he was attempting monitoring of an existing
    chronyd outside<br>
    his container.<br>
    I have done that (way) in the past to monitor time service using
    nagios.<br>
    I just installed (copied) the chronyc binary to the monitoring
    system, which<br>
    itself was running ntpd, and made a check_chrony script that did a<br>
    chronyc call (from a perl skeleton available for nagios).<br>
    Probably not the most efficient way, but it works.=C2=A0 I used &quot;c=
hronyc
    tracking&quot;,<br>
    of course with a -h parameter.<br>
    <br>
    But maybe I am completely wrong guessing his objectives... it is not
    very<br>
    clear from the explanation.<br>
    <br>
    Rob<br>
    <br>
    <div>On 2025-08-05 09:20, Mingye Wang wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <pre>So uh Rob gave a good explanation of how chrony works, but hones=
tly:
this smells like an &quot;XY problem&quot; to me. What are you attempting t=
o do,
actually, by getting `chronyc sources`? In other words, what
information do you *really* need?

</pre>
    </blockquote>
  </div>

</blockquote></div>

--000000000000c882c9063b99ec20--

-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]