| Re: [chrony-users] RE: Chrony is making NTP Server offline on the system boot |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] RE: Chrony is making NTP Server offline on the system boot
- From: "Kevin P. Fleming" <lists.chrony-users@xxxxxxxxxxxxx>
- Date: Sun, 08 Jan 2023 06:53:19 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=km6g.us; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1673178821; x=1673265221; bh=QKNci/eOBb E8YnH+NzS9s+KPyTCnIcCxArCxJfnWON8=; b=TnkZWJmS/AGh8CPm/kGaQPK4KF 5RcVOL7s3Ypk+u8m03NEt4CkRglWiQO1SKOjbgIIDeVveNFgUi/bsXXY2ZEEY4ht HPbvArudVOcAu7Zi8UZTfJw0KDAFt4j+2qFLrNyg2JCU6xf7QR2ccpRo4iQsFWw1 elBwWj0Hv5GTtwDuf4ar+UfUMhfC2ewFef9ZBqRXDnfpci8ebLE5hTZls4hZ0jcQ 83ddjSrxbLJvBA36qNO6KULDyQbztojCqLV0GED6Qir0dBSWkpK6y/NhUr4ynzGn H8swHUQ86NqwfrP9lr+zLhwSeqdOScrkxccJX8goUouRANggk7/zlbtlX6tA==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1673178821; x=1673265221; bh=QKNci/eOBbE8YnH+NzS9s+KPyTCn IcCxArCxJfnWON8=; b=D2HKo+3vW13PbHESiUAXGFwQebZQJIQUXsvcww5/DRf3 w3tGvg/0hBnm3KVVwhMMzzuZmvAZDPyLar41oTqLcEQlD4M9TFRsTwggdPMQhQxY rChkqF8oyzFl4Z0BlDg66UPgxKZO9iw/2JfxqncJmb/veruYAxKxdKd3wB/iEJx3 oXODEuNFdXZCXcWXF5O0BRXuMCtpW973YZdaXBMuRw4wDn8LLGYF4zcGBoXUTnzd xOjyUwic8TBd+KDgqV4C3lCrtKuLq8lLA5csTMqtxL5+7yM7HWtftGVOi13M61Aq 2M0h9zaY3MlFFiDFVodKFKoEHS+o1H/zlth1yHpPlw==
- Feedback-id: i1309466e:Fastmail
On Sun, Jan 8, 2023, at 03:35, Iqbal Singh Aulakh -X (iaulakh - HCL AMERICA INC at Cisco) wrote:
> I can see from the dmesg log the eth1 port is up before the NTP
> client/server is started:
> demsg
> [Fri Oct 28 05:09:45 2022] vmxnet3 0000:05:00.0 eth1: NIC Link is Up
> 10000 Mbps
> [Fri Oct 28 05:09:45 2022] vmxnet3 0000:0b:00.0: # of Tx queues : 8, #
> of Rx queues : 8
"Link is Up" means only that the layer 1 (physical) link has been established. It does not mean that any addresses have been assigned to the interface or that any routes through it are available. For example, if the interface is configured to use DHCP to obtain its network information, it may be 5-30 seconds after "Link is Up" before the interface can actually handle traffic.
> At this point we can see chronyd continually retrying to connect to
> both NTP sources, which is what is expected but for some reason it
> marks the NTP sources as offline:
>
> Oct 28 05:09:50 gsvlfl4plb02va chronyd[925]: 2022-10-28T05:09:50Z
> ntp_io.c:316:(connect_socket) Could not connect NTP socket to
> 10.37.9.162:123 : Network is unreachable
The "some reason" is very clear: when chrony attempted to send a packet to 10.37.9.162 it got a reply from the network stack that no route to that address was available.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.