Public bug reported:
The following is repeated periodically in the syslog:
Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
Feb 28 20:25:02 em-cel1 systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...
There is no log anywhere to indicate why the service failed.
The service stopped failing when we downgraded iproute2 from
4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.
The DHCPClient seems to be involved in the chain of events.
At the same frequency as the service failures, we do an ifup on a non-
auto dhcp interface. The ifup results in a DHCP request, which in this
case does not get a response (the link to the DHCP server is down.
When we stop the process that does the periodic ifup, the service
remains up (with iproute2 4.15.0-2ubuntu1.3).
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1919003
Title:
Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3
Status in iproute2 package in Ubuntu:
New
Bug description:
The following is repeated periodically in the syslog:
Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
Feb 28 20:25:02 em-cel1 systemd[1]: Starting
resolvconf-pull-resolved.service...
Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...
There is no log anywhere to indicate why the service failed.
The service stopped failing when we downgraded iproute2 from
4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.
The DHCPClient seems to be involved in the chain of events.
At the same frequency as the service failures, we do an ifup on a non-
auto dhcp interface. The ifup results in a DHCP request, which in this
case does not get a response (the link to the DHCP server is down.
When we stop the process that does the periodic ifup, the service
remains up (with iproute2 4.15.0-2ubuntu1.3).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
