crash due to assertion failure on busy VM host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Version: 1:4.2.8p4+
We've observed the following crash on an Ubuntu 16.04 s390x nova-compute host, apparently related to the VMs network interfaces coming and going:
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8 [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542171 qvb8dd4fc29-b8 [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542172 tap3ca379f2-d1 [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542173 tap8dd4fc29-b8 [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542174 qvo92509b39-cf [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542175 qvb92509b39-cf [fe80::
Nov 11 01:40:34 s0lp3 ntpd[2426]: Deleting interface #542166 tap3ca379f2-d1, fe80::fc16:
Nov 11 01:40:34 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
Nov 11 01:40:37 s0lp3 ntpd[2426]: bind(122) AF_INET6 fe80::fc16:
Nov 11 01:40:37 s0lp3 ntpd[2426]: unable to create socket on tap92509b39-cf (542176) for fe80::fc16:
Nov 11 01:40:37 s0lp3 ntpd[2426]: failed to init interface for address fe80::fc16:
Nov 11 01:40:39 s0lp3 ntpd[2426]: Listen normally on 542177 tap92509b39-cf [fe80::
Nov 11 01:40:39 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
Nov 11 01:40:52 s0lp3 ntpd[2426]: Deleting interface #542172 tap3ca379f2-d1, fe80::fc16:
Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542163 qvo3ca379f2-d1, fe80::14ad:
Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542164 qvb3ca379f2-d1, fe80::7cf6:
Nov 11 01:41:05 s0lp3 ntpd[2426]: ./../lib/
Nov 11 01:41:05 s0lp3 ntpd[2426]: exiting (due to assertion failure)
I'm so glad we switched to chrony after 18.04 as ntp server (and systemd-timesyncd as default ntp client) as this is just a pain in NTP.
I think this is the same (a newer version of) bug 1069543 therefore marking it as a dup.