** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic
This bug was fixed in the package systemd - 237-3ubuntu10.33
---
systemd (237-3ubuntu10.33) bionic; urgency=medium
*
d/p/lp1852754/0001-network-do-not-re-set-MTU-when-current-and-requested.patch,
d/p/lp1852754/0002-network-call-link_acquire_conf-and-link_enter_join_n.patch,
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
Hello Neil, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started
> ubuntu@srv-ywz63:~$ sudo dhclient eth0
> RTNETLINK answers: File exists
I think you're trying to start dhclient on an interface that's already
setup.
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
root@lp1805183-b:~#
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44
with dnsmasq server setup to provide dhcp with 1m lease timeout, just
run dhclient on test system:
ubuntu@lp1805183-d:~$ dpkg -l systemd|grep ii
ii systemd240-6ubuntu5.7 amd64system and service manager
ubuntu@lp1805183-d:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14
Hello Neil, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I have tested Ubuntu Focal with systemd 243-3ubuntu1:
https://launchpad.net/ubuntu/+source/systemd/243-3ubuntu1
and the issue I have reported in Bug 1849608, which is marked as the duplicate
of this bug, is gone now. Hence I confirmed the fix works here.
--
You received this bug notification
Hello Neil, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This has been wrongly marked as fixed in eoan. It's not; the fix for
this is still in eoan-proposed in systemd 242-7ubuntu3.2. I don't know
why the separate bug LP: #1849608 was used for that SRU vs this one.
Maybe the argument is that in eoan, systemd-resolved is *never*
restarted, instead of
** Also affects: systemd (Ubuntu Focal)
Importance: Low
Status: Triaged
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status:
I've found the patch applied to Eoan was the broken version where it
used the bash'ism instead of the much more basic (and more portable)
sh'ism of redirecting both STDOUT and STDERR.
I have confirmed this behaviour in Eoan (see bug #1850009) after doing
an upgrade to this release.
I did a quick
Ok, I'll have a look at it; I only backported the Eoan fix to Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded from Xenial
Steve in comment #9 I left a patch against the repo that iirc was
working fine on my machines. Maybe it can be helpful. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
This was also pointed out specifically in comment #8.
I'm reopening the trunk task on this bug as well since the bug is still
there in eoan.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
+ md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir
/isc-dhcp-v6-$interface.conf &> $oldstate
"&>" is a bashism. /sbin/dhclient-script uses /bin/sh as its interpreter.
This does not work as intended.
$ dash
$ echo foo &> output
foo
$ cat output
[1] + Done
@tf8 the patch in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/comments/8
against a live server has been working fine for us on AWS for almost a
year now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This still looks like an issue in Ubuntu 18.04 LTS. At least on systems
that was upgraded from 14.04 release. I will disable systemd-resolved
and revert to good old resolv.conf but what is the actual recommended
workaround while the fix is not released?
--
You received this bug notification
For Info, I'm repearing an SRU upload for Bionic hopefully available by
End Of Day
** Description changed:
[Impact]
Log noise due to needless restart of resolved on lease expiry, maybe loss of
cached state?
+ Application that require Name Resolution may fail while the service is being
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Louis Bouchard (louis)
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because
This bug was fixed in the package systemd - 240-6ubuntu9
---
systemd (240-6ubuntu9) eoan; urgency=medium
* Fix typpo in storage test.
File: debian/tests/storage
Lol
On Thu, 30 May 2019, 20:20 Rafael David Tinoco, <
rafaeldtin...@kernelpath.com> wrote:
> xnox, it looks like you're missing a "$" in md5sum command from:
>
>
> https://launchpadlibrarian.net/426017250/systemd_240-6ubuntu7_240-6ubuntu8.diff.gz
>
> for the -proposed systemd version:
>
>
xnox, it looks like you're missing a "$" in md5sum command from:
https://launchpadlibrarian.net/426017250/systemd_240-6ubuntu7_240-6ubuntu8.diff.gz
for the -proposed systemd version:
/sbin/dhclient-script: 57: /etc/dhcp/dhclient-enter-hooks.d/resolved:
Syntax error: "(" unexpected
Adding it
** Also affects: systemd (Ubuntu Disco)
Importance: Low
Status: In Progress
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
been running for 1 hour, seems to be working as expected
finally got one minute to create a patch against systemd repo instead of
a live server
** Patch added: "0001-avoid-restarting-resolved-on-dhclient.patch"
@juliank
I *believe* this is impacting our AWS ubuntu EC2 machines and causing wild DNS
errors impacting our users, I tried to apply the patch in this thread but it
doesn't work, it complains like this
/etc/dhcp/dhclient-enter-hooks.d/resolved: Syntax error: "("
unexpected
about this line
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded from Xenial
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360989
** Merge proposal linked:
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360990
--
You received this bug notification because you are a member
If we want to backport this to stable releases, we need a test case.
What I came up with, as I was not able to simulate dhcp lease refreshes,
is:
(1) Append make_resolv_conf to the end of the file, so it gets executed
(2) Execute the file with bash -x and different settings and ensure there are
Here's a patch while the git branch is pushing.
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
** Patch added:
"0001-Only-restart-resolved-on-changes-in-dhclient-enter-h.patch"
I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.
--
You received this bug notification because you are a member of
** No longer affects: ubuntu-release-upgrader (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah no, 229, not 239 it seems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded from Xenial
To manage notifications about this
The dbus API is only available in 239, which means we can't use it in
bionic.
We could maybe make the hook just restart resolved if the new files it
wrote are different from the old files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
First of all, dhclient remaining in place is not a bug. Systems are not
switching to netplan and networkd on upgrade.
The restart caused by /etc/dhcp/dhclient-enter-hooks.d/resolved to tell
systemd-resolved about new servers and search domains, and hence
expected to happen (resolved does not
** Tags added: id-5c0011e969ed904c67dda9ee
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded from Xenial
To manage notifications
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded
40 matches
Mail list logo
