RE: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

On Wed, 14 Dec 2016, Adri Koppes wrote:

> Bill,
>
> If you read the original message, chrony 2.4.1 is running without problems.
>
> This implies the network is working, name resolutions is fine and the firewall isn't blocking stuff.
> I am the network and systems administrator, so I know it's ok!
> The test with chrony 3.0-pre1 is also using the same /etc/chrony.conf.

OK, sorry to have made a silly observation. I note that Miroslav seems to have found the
problem.

> Adri.
>
>
> > -----Original Message-----
> > From: Bill Unruh [mailto:unruh@xxxxxxxxxxxxxx]
> > Sent: woensdag 14 december 2016 16:58
> > To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
> > socket on FreeBSD
> >
> >
> >
> > William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273
> > Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324
> > UBC, Vancouver,BC _|_ Program in Cosmology |____ unruh@xxxxxxxxxxxxxx
> > Canada V6T 1Z1 ____|____ and Gravity ______|_
> > www.theory.physics.ubc.ca/
> >
> > On Wed, 14 Dec 2016, Adri Koppes wrote:
> >
> > > Miroslav,
> > >
> > >
> > >
> > > I have chronyd 2.4.1 running on FreeBSD 11.0 release and itʼs working fine.
> > >
> > > All refclocks are internet servers and data is received normally.
> > >
> > > I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp
> > data from the internet refclocks.
> > > I tried again with the latest master from git and it fails in the same
> > > way,
> > >
> > > This is some debug output from the git master version and it seems
> > > there is an almost immediate timeout on both send and receiving data
> > from any socket.
> >
> >
> > This may be a silly question, but are you sure you have networking working.
> > Can you browse with a browser for example.
> > Are you sure your firewall will let you send and receive ntp packets?
> >
> >
> > > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
> > > timeout for [194.171.167.130:123]
> > >
> > > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
> > > 194.171.167.130:123 from [UNSPEC] fd 7
> > >
> > > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
> > > from 194.171.167.130:123 to [UNSPEC] fd=7
> > > if=-1 tss=1 delay=0.000104191
> > >
> > > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
> > > timeout for [80.94.65.10:123]
> > >
> > > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
> > > 80.94.65.10:123 from [UNSPEC] fd 8
> > >
> > > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
> > > from 80.94.65.10:123 to [UNSPEC] fd=8 if=-1
> > > tss=1 delay=0.000099536
> > >
> > >
> > >
> > > If there is anything I can do to test or provide more information, please let
> > me know.
> > >
> >  > Adri,.
> > >
>
> --
> To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
> For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
> Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.