Re: [chrony-dev] When will chrony release next?
Le 16/08/2018 à 11:43, FUSTE Emmanuel a écrit : > Le 16/08/2018 à 11:40, Miroslav Lichvar a écrit : >> On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote: >>> No, with chrony the shm refclock seems to be ignored (need to retest >>> precisely) . The observed stratum of my chrony servers were not >>> refclock+1 (0+1) but the defined orphan stratum (3). >> Oh, you mean the servers were not synchronized to their SHM refclocks >> even when they were working correctly? And removing the orphan option >> from chrony.conf fixed that? > Exactly >> That sounds like a bug. If you have a reproducer or have more details, >> please let us know. >> > Ok, will find time to redo some tests and report here. > Thank you. Hello, Tested rapidly with chrony git master of June 22. Work as expected ! If it was a bug, it is gone. Will do some more tests with shm refclock and with lost of ptp link as the actual test is with a PHC type refclock. (A status positioned by writer/ptp4l , readable by the PHC device consumers, and reset on writer close would be great to alleviate the use of shm/phc2sys) Emmanuel.
Re: [chrony-dev] When will chrony release next?
On 16/08/2018 04:40, Miroslav Lichvar wrote: On Thu, Aug 16, 2018 at 12:11:00AM -0300, Gustavo Serra Scalet wrote: I'm building Debian releases for cloud usage and noticed the known-issue[1] regarding `getrandom` hanging when Chrony is called early on system boot (and it does, as DHCP will call it during network configuration). I see it as critical as ithappens every time on current snapshot builds after booting. (`systemd-analyze` reports thgat startup times soared from 15 seconds to 180 seconds!) Yeah, this is an annoying bug. I was hoping it would be addressed on the kernel side as there are other applications affected by it and at least some people seem to think the system call should never block with the urandom source > As I read on Ubuntu cloud[1], there are indeed other ways to handle this and it would mitigate this issue on other projects as well, however it's not the fastest solution so it should be planned accordingly. On my specific workload, chrony is the only one being affected by this behavior. Are you planning to do a new release soon? I was planning to make a new release in about a month, depending on how much time I'll have for chrony. There is just one new feature left on my todo list and then I'll be writing tests for the new code, etc. One month looks good for me. Thanks! If it's blocking me too much, I'll consider patch it downstream then. If people think it's important enough, I could make a quick 3.3.1 bug fix only release. I'm not sure. Also a good solution for me, but it's your call. Regards [1] https://blog.dustinkirkland.com/2014/02/random-seeds-in-ubuntu-1404-lts-cloud.html -- Gustavo Serra Scalet -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-dev] When will chrony release next?
Le 16/08/2018 à 11:40, Miroslav Lichvar a écrit : > On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote: >> No, with chrony the shm refclock seems to be ignored (need to retest >> precisely) . The observed stratum of my chrony servers were not >> refclock+1 (0+1) but the defined orphan stratum (3). > Oh, you mean the servers were not synchronized to their SHM refclocks > even when they were working correctly? And removing the orphan option > from chrony.conf fixed that? Exactly > > That sounds like a bug. If you have a reproducer or have more details, > please let us know. > Ok, will find time to redo some tests and report here. Thank you. Emmanuel.
Re: [chrony-dev] When will chrony release next?
On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote: > No, with chrony the shm refclock seems to be ignored (need to retest > precisely) . The observed stratum of my chrony servers were not > refclock+1 (0+1) but the defined orphan stratum (3). Oh, you mean the servers were not synchronized to their SHM refclocks even when they were working correctly? And removing the orphan option from chrony.conf fixed that? That sounds like a bug. If you have a reproducer or have more details, please let us know. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-dev] When will chrony release next?
Le 16/08/2018 à 10:57, Miroslav Lichvar a écrit : > On Thu, Aug 16, 2018 at 08:47:16AM +, FUSTE Emmanuel wrote: >> NTP servers pool connected to the PTP network and to the organization >> network. >> Each server use the GM on the PTP network. > The servers have a SHM reference clock providing the PTP time (e.g. > phc2sys)? Yes. >> With ntpd, as long as my refclock is running all work normally. >> If I lost my PTP switch, orphan mode kick in and all the servers in the >> pool serve a coherent time. >> >> With chrony, as refclocks are not taken into account in the orphan mode >> decision (status of the refclock, stratum) and as I am not using other >> externals NTP sources I am always in orphan mode. > I'm not sure what is the difference here. The orphan mode should be > active, but with chrony it's not? I.e. the servers are still > synchronized to their SHM refclocks and don't want to select a server > to which all others should synchronize? No, with chrony the shm refclock seems to be ignored (need to retest precisely) . The observed stratum of my chrony servers were not refclock+1 (0+1) but the defined orphan stratum (3). Last time I checked this, it was on an internet connected pool of two servers with ptp refclock, and public ntp sources (pool.ntp.org) and it exhibit the same behavior. The stratum of the chrony servers were orphan stratum or the stratum of a selected Internet ntp source + 1 (if lower than the ophan one) but not the shm + 1 one. Will redo some tests if you want. Emmanuel.
Re: [chrony-dev] When will chrony release next?
On Thu, Aug 16, 2018 at 07:53:24AM +, FUSTE Emmanuel wrote: > have you on your todo list for a future release some work around orphan > mode and refclocks ? I wasn't planning anything in that area. > Taking refclocks into account as other ntp sources for the orphan mode > is the only feature I a missing from ntpd in my use case. Could you please be more specific? I'm not sure what an orphan refclock would be or what is the use case. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
Re: [chrony-dev] When will chrony release next?
Le 16/08/2018 à 09:40, Miroslav Lichvar a écrit :
> I was planning to make a new release in about a month, depending on
> how much time I'll have for chrony. There is just one new feature left
> on my todo list and then I'll be writing tests for the new code, etc.
>
> If people think it's important enough, I could make a quick 3.3.1 bug
> fix only release. I'm not sure.
>
Hello Miroslav,
Semi off-topic question:
As you are doing refactoring to share more code between ntp source and
refclocks,
have you on your todo list for a future release some work around orphan
mode and refclocks ?
Taking refclocks into account as other ntp sources for the orphan mode
is the only feature I a missing from ntpd in my use case.
Regards
Emmanuel.
N�r��y隊W!���u��z!_jh�ʊ��+a�{.n�+�^���y�E��^���j)\��'�ׯ��z�\��'�۱}���*+�����)��.n7��:蹹^f��X��f���܆�'�۱}���*+
Re: [chrony-dev] When will chrony release next?
On Thu, Aug 16, 2018 at 12:11:00AM -0300, Gustavo Serra Scalet wrote: > I'm building Debian releases for cloud usage and noticed the known-issue[1] > regarding `getrandom` hanging when Chrony is called early on system boot > (and it does, as DHCP will call it during network configuration). I see it > as critical as ithappens every time on current snapshot builds after > booting. (`systemd-analyze` reports thgat startup times soared from 15 > seconds to 180 seconds!) Yeah, this is an annoying bug. I was hoping it would be addressed on the kernel side as there are other applications affected by it and at least some people seem to think the system call should never block with the urandom source. > Are you planning to do a new release soon? I was planning to make a new release in about a month, depending on how much time I'll have for chrony. There is just one new feature left on my todo list and then I'll be writing tests for the new code, etc. If people think it's important enough, I could make a quick 3.3.1 bug fix only release. I'm not sure. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
