ntpd hangs on boot but works afterwards

[Scott Gasch]

Hi,

I have a system I recently upgraded to FreeBSD 12 and started getting a
weird problem with ntpd.  What happens is, on boot, rc.ntpd seems to hang
requiring me to go to the console and hit ^C.  When I do so it says
something like "/etc/rc.d/ntpd interrupted" and continues to boot
successfully (including starting sshd later in the process and letting me
ssh into the machine).

When I ssh in, ntpd is not running.  If I just do a /etc/rc.d/ntpd start at
that point it works just fine as does a service ntpd start.

I am setting the ntpd_sync_on_start rc variable and I do see the -g option
on the ntpd process when it starts.  The machine clock should be pretty
close to the actual time... so I don't suspect this is due to a huge clock
skew.  It does seem like the network is up and running by the time it hangs
-- I see some DHCP messages earlier in the boot process making me believe
that we have an IP address and should not be stuck trying to talk to the
ntp peers.

Does anyone have ideas or seen this before?  Thanks in advance.

Here are some relevant configs:

# *uname -a*
FreeBSD wannabe 12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC  amd64

# *grep ntp rc.conf*
ntpd_enable="YES"
ntpd_sync_on_start="YES"

# *cat ntp.conf | grep -v "^#"*
server 127.127.1.0     # local clock
fudge  127.127.1.0 stratum 10
server 0.us.pool.ntp.org iburst
server 1.us.pool.ntp.org
server ntp.ucsd.edu
server ns.nts.umn.edu
server 0.freebsd.pool.ntp.org iburst
server 1.freebsd.pool.ntp.org

restrict default limited kod nomodify notrap nopeer noquery
restrict 10.0.0.0 mask 255.255.255.0 nomodify notrap
restrict -6 default limited kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
restrict 127.127.1.0

driftfile /var/lib/ntp/ntp.drift
leapfile "/var/db/ntpd.leap-seconds.list"