> -----Original Message-----
> From: Miroslav Lichvar [mailto:mlich...@redhat.com]
> Sent: woensdag 14 december 2016 16:58
> To: email@example.com
> Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
> socket on FreeBSD
> On Wed, Dec 14, 2016 at 03:34:30PM +0000, 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.
> > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
> > timeout for [220.127.116.11:123] 2016-12-14T15:25:22Z
> > ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 18.104.22.168:123
> > from [UNSPEC] fd 7 2016-12-14T15:25:22Z ntp_io.c:668:(process_message)
> > Received 0 bytes from 22.214.171.124: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
> > [126.96.36.199:123] 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket)
> > Sent 48 bytes to 188.8.131.52:123 from [UNSPEC] fd 8
> > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
> > from 184.108.40.206: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.
> Hm, I have it working on FreeBSD 10.1. I guess it might be related to the new
> support for recvmmsg(). Do you see 'HAVE_RECVMMSG 1' in config.h after
> running ./configure? If yes, can you remove that line from config.h,
> recompile chronyd, and see if it works?
I did have 'HAVE_RECVMMSG 1' in config.h.
After removing the line and recompiling, chrony 3.0-pre1 seems to be running OK
and receiving timestamps.
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
Trouble? Email listmas...@chrony.tuxfamily.org.