Chrony 1.29 was working without problems on FreeBSD 10. The new 1.30pre1 doesn't work at all, getting no samples from remove ntp servers. When I start 'chronyd -d -d', it seems there is a problem transmitting packets.
2014-06-25T11:57:23Z main.c:428:(main) chronyd version 1.30-pre1 starting 2014-06-25T11:57:23Z local.c:137:(calculate_sys_precision) Clock precision 0.000001000 (-20) 2014-06-25T11:57:23Z local.c:561:(lcl_RegisterSystemDrivers) Local freq=0.000ppm 2014-06-25T11:57:23Z sys_sunos.c:347:(setup_kernel) Cannot write to _dosynctodr 2014-06-25T11:57:23Z reference.c:193:(REF_Initialise) Frequency -9.241 +/- 0.161 ppm read from /var/db/chrony.drift 2014-06-25T11:57:23Z ntp_sources.c:312:(resolve_sources) resolving chime1.surfnet.nl 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) chime1.surfnet.nl resolved to 192.87.106.2 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving chime2.surfnet.nl 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) chime2.surfnet.nl resolved to 192.87.36.4 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving chime4.surfnet.nl 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) chime4.surfnet.nl resolved to 145.145.170.84 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving chime5.surfnet.nl 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) chime5.surfnet.nl resolved to 194.171.167.130 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving chime6.surfnet.nl 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) chime6.surfnet.nl resolved to 192.87.106.3 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving tt52.ripe.net 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) tt52.ripe.net resolved to 213.136.0.252 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving tt165.ripe.net 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) tt165.ripe.net resolved to 193.0.0.229 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving ntp2.oma.be 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) ntp2.oma.be resolved to 193.190.230.66 2014-06-25T11:57:23Z ntp_sources.c:274:(name_resolve_handler) resolving ntp1.belwue.de 2014-06-25T11:57:23Z ntp_sources.c:244:(name_resolve_handler) ntp1.belwue.de resolved to 129.143.2.23 2014-06-25T11:57:23Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [192.87.106.3:123] 2014-06-25T11:57:23Z ntp_io.c:678:(send_packet) Could not send to 192.87.106.3:123 : Socket is already connected 2014-06-25T11:57:23Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [129.143.2.23:123] 2014-06-25T11:57:23Z ntp_io.c:678:(send_packet) Could not send to 129.143.2.23:123 : Socket is already connected 2014-06-25T11:57:23Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [193.0.0.229:123] 2014-06-25T11:57:23Z ntp_io.c:678:(send_packet) Could not send to 193.0.0.229:123 : Socket is already connected 2014-06-25T11:57:23Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [194.171.167.130:123] 2014-06-25T11:57:23Z ntp_io.c:678:(send_packet) Could not send to 194.171.167.130:123 : Socket is already connected 2014-06-25T11:57:24Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [213.136.0.252:123] 2014-06-25T11:57:24Z ntp_io.c:678:(send_packet) Could not send to 213.136.0.252:123 : Socket is already connected 2014-06-25T11:57:24Z ntp_core.c:759:(transmit_timeout) Transmit timeout for [192.87.36.4:123] 2014-06-25T11:57:24Z ntp_io.c:678:(send_packet) Could not send to 192.87.36.4:123 : Socket is already connected This continues forever and chronyd never receives valid samples. Does anyone have an idea on how to continue, getting chronyd to run on FreeBSD 10? Chronyc 1.30-pre1 works fine and is able to communicate with a running 1.29 chronyd daemon. Adri. -- 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.