Arch Linux

Wmog

Member

Registered: 2017-09-13

Posts: 25

NTP socket then kernel time error

Hey,

I have an error with my NTP daemon. When I check its status for the first time with

systemctl status ntpd.service

here is the output:

Oct 26 17:14:42 myhost ntpd[377]: unable to create socket on enp2s0 (5) for fe80::493f:8ce3:2992:16b5%2#123
Oct 26 17:14:42 myhost ntpd[377]: failed to init interface for address fe80::493f:8ce3:2992:16b5%2
Oct 26 17:14:42 myhost ntpd[377]: new interface(s) found: waking up resolver
Oct 26 17:14:44 myhost ntpd[377]: bind(24) AF_INET6 xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx#123 flags 0x11 failed: Cannot assign re>
Oct 26 17:14:44 myhost ntpd[377]: unable to create socket on enp2s0 (6) for xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx#123
Oct 26 17:14:44 myhost ntpd[377]: failed to init interface for address xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx
Oct 26 17:14:44 myhost ntpd[377]: Listen normally on 7 enp2s0 [fe80::493f:8ce3:2992:16b5%2]:123
Oct 26 17:14:44 myhost ntpd[377]: new interface(s) found: waking up resolver
Oct 26 17:14:46 myhost ntpd[377]: Listen normally on 8 enp2s0 [xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx]:123
Oct 26 17:14:46 myhost ntpd[377]: new interface(s) found: waking up resolver

It seems to be an IPv6 error.

Then, when I restart the service, and that I check its status again, I get another one:

Oct 26 17:18:13 myhost ntpd[1178]: Listen and drop on 0 v6wildcard [::]:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen normally on 2 lo 127.0.0.1:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen normally on 3 enp2s0 192.168.1.25:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen normally on 4 lo [::1]:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen normally on 5 enp2s0 [xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx]:123
Oct 26 17:18:13 myhost ntpd[1178]: Listen normally on 6 enp2s0 [fe80::493f:8ce3:2992:16b5%2]:123
Oct 26 17:18:13 myhost ntpd[1178]: Listening on routing socket on fd #23 for interface updates
Oct 26 17:18:13 myhost ntpd[1178]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Oct 26 17:18:13 myhost ntpd[1178]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

This time it is a kernel time error.

My configuration file `/etc/ntp.conf`:

# Please consider joining the pool:
#
#     http://www.pool.ntp.org/join.html
#
# For additional information see:
# - https://wiki.archlinux.org/index.php/Network_Time_Protocol_daemon
# - http://support.ntp.org/bin/view/Support/GettingStarted
# - the ntp.conf man page

# Associate to Arch's NTP pool
server 0.fr.pool.ntp.org iburst
server 1.fr.pool.ntp.org iburst
server 2.fr.pool.ntp.org iburst
server 3.fr.pool.ntp.org iburst

# By default, the server allows:
# - all queries from the local host
# - only time queries from remote hosts, protected by rate limiting and kod
restrict default kod limited nomodify nopeer noquery notrap
restrict 127.0.0.1
restrict ::1

# Location of drift file
driftfile /var/lib/ntp/ntp.drift

The output of `ntpq -pn`

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+185.123.84.51   200.98.196.212   2 u   30   64  377   15.617   -0.422  20.934
+80.67.184.40    85.199.214.102   2 u   29   64  377    4.370    0.859   9.489
*2001:bc8:313f:: 145.238.203.14   2 u   26   64  377    4.182    1.177   8.150
+178.32.220.152  138.96.64.10     2 u   25   64  377    7.363    3.703   8.125

Thank you in advance for your help.

Last edited by Wmog (2018-10-26 15:37:04)

loqs

Member

Registered: 2014-03-06

Posts: 17,373

Re: NTP socket then kernel time error

Oct 26 17:18:13 myhost ntpd[1178]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

This seems reasonable when ntpd has just been started.

Lone_Wolf

Forum Moderator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,922

Re: NTP socket then kernel time error

The first errors suggest ntpd is started to early, check https://wiki.archlinux.org/index.php/Ne … col_daemon for alternative ways to start ntp.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)