NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Error when starting NetBSD



Not necessary.  A second later, ntpd auto-recovers by picking up the new
local address and successfully resolving 2.netbsd.pool.ntp.org into the
pool members and their addresses:


> Sep  1 08:02:27 gandalf ntpd[817]: Listen normally on 7 wm0 75.129.79.232:123
> Sep  1 08:03:26 gandalf ntpd[817]: Soliciting pool server
> Sep  1 08:03:27 gandalf ntpd[817]: Soliciting pool server
> Sep  1 08:03:28 gandalf ntpd[817]: Soliciting pool server 2602:f9ba:69::210
> Sep  1 08:03:29 gandalf ntpd[817]: Soliciting pool server 2607:ff50:0:1a::10
> Sep  1 08:03:30 gandalf ntpd[817]: Soliciting pool server 152.67.232.7
> [...]

ntpdate=YES
ntpd=YES             ## 'ntp' == Network TIME Protocal

I did this, and it  change the time in the xclock --
How do I reset xclock?

Will the stuff I see get fixed in the future? It looks like a timing
prob.

On Mon, Sep 2, 2024 at 9:13 PM Martin Neitzel
<neitzel%hackett.marshlabs.gaertner.de@localhost> wrote:
>
> > Below is my  /var/log/messages.
> > Why do I get:
> >      Sep  1 08:02:20 gandalf ntpd[817]: error resolving pool
> >       2.netbsd.pool.ntp.org: Temporary failure in name resolution (2)
>
> Your /var/log/messages filtered down using  grep -E 'ntpd|dhcp'
> shows more clearly what happens.
>
> First signs of each:
>
> > Sep  1 08:02:17 gandalf ntpd[822]: ntpd 4.2.8p15-o Thu Mar 28 08:33:33
> > Sep  1 08:02:18 gandalf dhcpcd[496]: wm0: carrier acquired
>
> ntpd rightfully complains
>
> > Sep  1 08:02:20 gandalf ntpd[817]: error resolving pool [...]
>
> because it takes dhcpd a bit longer to establish the network:
>
> > Sep  1 08:02:21 gandalf dhcpcd[496]: wm0: adding default route via [IPv6...]
> > Sep  1 08:02:26 gandalf dhcpcd[496]: wm0: adding default route via 75.129.79.1
>
> and also probably also a nameserver entry in /etc/resolv.conf (depending
> on you running or not running your own name server).
>
> > Can it be fixed?
>
> Not necessary.  A second later, ntpd auto-recovers by picking up the new
> local address and successfully resolving 2.netbsd.pool.ntp.org into the
> pool members and their addresses:
>
>
> > Sep  1 08:02:27 gandalf ntpd[817]: Listen normally on 7 wm0 75.129.79.232:123
> > Sep  1 08:03:26 gandalf ntpd[817]: Soliciting pool server
> > Sep  1 08:03:27 gandalf ntpd[817]: Soliciting pool server
> > Sep  1 08:03:28 gandalf ntpd[817]: Soliciting pool server 2602:f9ba:69::210
> > Sep  1 08:03:29 gandalf ntpd[817]: Soliciting pool server 2607:ff50:0:1a::10
> > Sep  1 08:03:30 gandalf ntpd[817]: Soliciting pool server 152.67.232.7
> > [...]
>
>                                                 Martin Neitzel


Home | Main Index | Thread Index | Old Index