Re: [Linuxptp-users] pmc:: uds: sendto failed: No such file or directory

[David M. <dav...@gm...>]

Thanks Richard, for the concise and helpful reply!
I'll look into what switching to 1.7 would take as a preference (in
addition to making my stuff more robust anyway), but it's good to
understand what the underlying cause was.
Also for the notes on the master's dataset - I'll take a closer look at
what it's actually saying and go from there, worst case sounds like I can
ignore the logs.

Thanks again,
David M

On Fri, Nov 4, 2016 at 7:56 PM, Richard Cochran <ric...@gm...>
wrote:

> On Fri, Nov 04, 2016 at 08:25:04AM +1100, David Mirabito wrote:
> > Very occasionally I'm noticing that this fails, and I have a message in
> > syslog:
> >
> > user.err pmc: [94758.014] uds: sendto failed: No such file or directory
>
> This is a regression in v1.6 that was fixed in v1.7:
>
>    3938cbc uds: Prevent unintentional announce message timeouts.
>
> You can cherry pick that onto v1.6 or just switch to v1.7.
>
> > And it periodically logs (with gaps of 158, 28, 168, 56, 168 seconds
> > between the messages that I looked at) that:
> >
> > Oct 20 21:13:23 user.notice ptp4l: [94820.538] selected best master clock
> > 000cec.fffe.08046f
> >
> > Is this expected, the constant reminder that the same BMC is chosen time
> > after time, or would this be considered strange?
>
> This effect is normal, caused by any change in the master's data set.
> Honest GPS masters will update the grandmasterClockAccuracy field
> according to the current state of the GPS.
>
> Thanks,
> Richard
>