Re: Chrony without daemon
Remush <[email protected]> Tue, 5 Aug 2025 16:31:46 +0300
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <CAMEWNSFWNxcRHTb8EYdtynck5rh5-txwCznzdTJuuBWb1-F+pg@mail.gmail.com> |
--000000000000912a56063b9e3f8b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable So it means I have to set up something, a vm, a pod, a server, something that has chronyd running? It kind of beats the point, no? If I have a place that runs chronyd why not run chornyc from there? =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-12:28 =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 > You need to provide the -h parameter to chronyc. > > E.g. chronyc -h 1.2.3.4 sources > Or: chronyc -h 1.2.3.4 tracking > (when the chronyd you want to watch is on a system with IP address 1.2.3.= 4) > > Again, you DO NOT need to run the daemon on the system (pod) where you ru= n > chronyc. > You only need to provide IP connectivity between the two, and to use > "cmdallow" in the > chronyd configuration file(s) to allow the IP address where chronyc is > used. > > Example: chronyc -h 44.137.72.10 tracking > Reference ID : 50505300 (PPS) > Stratum : 1 > Ref time (UTC) : Tue Aug 05 09:27:29 2025 > System time : 0.000000054 seconds slow of NTP time > Last offset : +0.000000108 seconds > RMS offset : 0.000001205 seconds > Frequency : 10.403 ppm fast > Residual freq : -0.000 ppm > Skew : 0.025 ppm > Root delay : 0.000000001 seconds > Root dispersion : 0.000025486 seconds > Update interval : 16.0 seconds > Leap status : Normal > > Rob > > On 2025-08-05 10:22, Remush wrote: > > 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 "chrony= c > 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 ver= y >> 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? >> >> >> > --000000000000912a56063b9e3f8b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"rtl"><div dir=3D"ltr">So it means I have to set up something, a= vm, a pod, a server, something that has chronyd running?<br></div><div dir= =3D"ltr">It kind of beats the point, no? If I have a place that runs chrony= d why not run chornyc from there?</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-12:28 =D7=9E=D7=90=D7=AA =E2=80=AARob = Janssen=E2=80=AC=E2=80=8F <=E2=80=AA<a href=3D"mailto:chrony-users@pe1ch= l.nl">chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]</a>=E2=80=AC=E2=80=8F>:=E2=80=AC<br></div><= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex"><u></u> =20 =20 =20 <div> You need to provide the -h parameter to chronyc.<br> <br> E.g. chronyc -h 1.2.3.4 sources<br> Or: chronyc -h 1.2.3.4 tracking<br> (when the chronyd you want to watch is on a system with IP address 1.2.3.4)<br> <br> Again, you DO NOT need to run the daemon on the system (pod) where you run chronyc.<br> You only need to provide IP connectivity between the two, and to use "cmdallow" in the<br> chronyd configuration file(s) to allow the IP address where chronyc is used.<br> <br> Example: chronyc -h 44.137.72.10 tracking<br> Reference ID=C2=A0=C2=A0=C2=A0 : 50505300 (PPS)<br> Stratum=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 1<br> Ref time (UTC)=C2=A0 : Tue Aug 05 09:27:29 2025<br> System time=C2=A0=C2=A0=C2=A0=C2=A0 : 0.000000054 seconds slow of NTP t= ime<br> Last offset=C2=A0=C2=A0=C2=A0=C2=A0 : +0.000000108 seconds<br> RMS offset=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0.000001205 seconds<br> Frequency=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 10.403 ppm fast<br> Residual freq=C2=A0=C2=A0 : -0.000 ppm<br> Skew=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = : 0.025 ppm<br> Root delay=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0.000000001 seconds<br> Root dispersion : 0.000025486 seconds<br> Update interval : 16.0 seconds<br> Leap status=C2=A0=C2=A0=C2=A0=C2=A0 : Normal<br> <br> Rob<br> <br> <div>On 2025-08-05 10:22, Remush wrote:<br> </div> <blockquote type=3D"cite"> =20 <div dir=3D"rtl"> <div dir=3D"ltr">I'll try to elaborate more about what I'm = trying to achieve.<br> </div> <div dir=3D"ltr">First of all, I'm very grateful for the detail= ed and well-explained comments you made.<br> </div> <div dir=3D"ltr">My objective is to monitor a drift between 3 NTP servers.<br> <br> </div> <div dir=3D"ltr">`chronyc sources` provides a wonderful and simple output just for that purpose.<br> </div> <div dir=3D"ltr">The issue I'm having is the following:<br> </div> <div dir=3D"ltr">I'm using Openshift as my base, and my solutio= n was to simply set a pod with a chrony image and run the command,</div> <div dir=3D"ltr">sadly to my understanding, openshift pods doesn= 9;t have access to systemd, meaning I can't set a chronyd daemon on the Pod it self.<br> <br> </div> <div dir=3D"ltr">"chrony tracking" also returns the error= message "506 can't talk with daemon".<br> </div> <div dir=3D"ltr">Honestly I really think that because of that Openshift limitation I won't find any way to actually run "chronyc sources".<br> <br> </div> <div dir=3D"ltr">I'm not completely understanding what it means= to run `chronyd -U -x`. <br> </div> <div dir=3D"ltr">I actually run it successfully, and it created a chronyd.pid, but "chronyc sources" still return "5= 06 Cannot talk to daemon"</div> <div dir=3D"ltr">Am I missing something?=C2=A0</div> </div> <br> <div class=3D"gmail_quote"> <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 <=E2=80=AA<a href=3D"mailto:chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]" target=3D"_bl= ank">chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]</a>=E2=80=AC=E2=80=8F>:=E2=80=AC<br> </div> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex= ;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <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 "chronyc tracking",<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, b= ut honestly: this smells like an "XY problem" 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> </blockquote> <br> </div> </blockquote></div> --000000000000912a56063b9e3f8b-- -- 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]