Re: ntpdate problem

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Will Senn <will.senn%gmail.com@localhost> writes:

> During boot up, I get the following message:
>
> The following components reported failures:
>     /etc/rc.d/ntpdate
> See /var/run/rc.log for more information.
>
> uname -a
> NetBSD loki.sentech.home 10.0_STABLE NetBSD 10.0_STABLE (GENERIC) #0: 
> Sat Jul 20 16:11:27 UTC 2024 
> mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>
> When I look in rc.log:
> --snip
> [running /etc/rc.d/unbound]
> [running /etc/rc.d/named]
> [running /etc/rc.d/rtclocaltime]
> [running /etc/rc.d/ntpdate]
> Setting date via ntp.
> Exiting, name server cannot be used: Temporary failure in name 
> resolution (2)/etc/rc.d/ntpdate exited with code 1
> [running /etc/rc.d/rpcbind]
> [running /etc/rc.d/ypserv]
> --snip
>
> looking in /etc/ntp.conf
> pool 2.netbsd.pool.ntp.org iburst
>
> but after logging in:
> ntpdate -q 2.netbsd.pool.ntp.org
> server 72.30.35.89, stratum 2, offset +0.476852, delay 0.07233
> server 168.235.69.132, stratum 2, offset +0.477450, delay 0.07291
> server 5.161.44.72, stratum 2, offset +0.479573, delay 0.06693
> server 72.30.35.88, stratum 2, offset +0.475984, delay 0.07390
> 24 Jul 11:32:10 ntpdate[1068]: adjust time server 5.161.44.72 offset 
> +0.479573 sec
>
> Any ideas as to why it's failing during startup?
>
> Thanks,
>
> Will


The network wasn't ready when ntpdate ran.  This can happen on more than
just wireless networks.  I have personally seen it on wired RPI devices
that use dhcp and on virtual machines that have higher than usual
latency (i.e. full CPU and device emulation on a slower server).  In
some cases, I ended up putting a sleep in /etc/rc.d/ntpdate to
compensate for this behavior.  You can also do some clever stuff with
/etc/ifconfig.* in that you can run a command there, and that command
could be "sleep".



-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org