Adjusting the Debian bug link, I discussed this on
https://bugs.debian.org/809166 already. ifupdown should *not* stop
"manual" interfaces with ifdown, unless you have an explicit "down"
action in /etc/network/interfaces. I assume this is not the case. It was
an explicit decision by the Debian
Alkis Georgopoulos [2016-01-13 8:47 -]:
> An empty line didn't do the trick, "manual" was necessary.
Ah, that's good. "manual" should indeed keep NM from touching it, but
current ifupdown should also not tear down "manual" interfaces on
shutdown. So in theory, with 0.8.8ubuntu1 your shutdown
Well...
This is *not* needed anymore, i.e. the current bug was solved:
# sed '/^ExecStop=/d' -i /lib/systemd/system/ifup@.service
Unfortunately now this is needed, i.e. the same bug appeared elsewhere:
# sed '/^ExecStop=/d' -i /lib/systemd/system/networking.service
The networking.service file
This bug was fixed in the package ifupdown - 0.8.8ubuntu1
---
ifupdown (0.8.8ubuntu1) xenial; urgency=medium
* Merge with Debian unstable. Remaining Ubuntu changes:
- Always call dhclient with -1, Ubuntu carries a patch so that renewal
won't time out.
- link.defn,
> ifupdown should not have a config stanza (or at least only a manual
one) for this.
Hi Martin, yup, when network manager was introduced in Ubuntu I've had added
code to LTSP to dynamically put "iface $DEVICE inet manual" in
/etc/network/interfaces, to prevent network manager from assigning an
These units moved to ifupdown in the meantime, moving component. There
is now a fix for this, by adding Slice=system.slice to ifup@.service.
** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@Alkis: It's possible that this still affects Xenial even with fixing
ifup@.service, as networking.service (which does not do that network
file check any more) might also shut down the interfaces; it just does
it later on.
But this bears the question why on an LTSP system ifupdown has a
Fix sent to Debian bug.
** Package changed: systemd (Debian) => ifupdown (Debian)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on
bisected to https://github.com/systemd/systemd/commit/8c8da0e0cb4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown even when
Reported to https://github.com/systemd/systemd/issues/2189. If this
can't/won't get fixed upstream, we'll drop the ExecStop= as a
workaround.
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.01
** Tags added: regression-release xenial
--
You received this bug notification
This script provides a test case for bisection. Start a schroot with e.
g.
schroot -b -c xenial -n systemd-test
and run the test script on the unpacked schroot dir:
sudo ./systemd-letmelive.sh /var/lib/schroot/unpack/systemd-test/
which will boot the schroot in nspawn and test if
Hi Martin, I've set up remote syslogging and I'm attaching the relevant
lines for the "ltsp33" client.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1492546/+attachment/4534472/+files/syslog
** Changed in: systemd (Ubuntu)
Status: Incomplete =>
Alkis, unfortunately rsyslog stops too early (before stopping
ifup@.service), the log shows no teardown of network at all. Not a
surprise with remote logging :-)
Is it possible for you to mount a local disk on /var/log/, enable
persistent journal (sudo install -d -g systemd-journal
Thank you Martin, I'm attaching journal.txt.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1492546/+attachment/4534902/+files/journal.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown even
Alkis, can you please attach /var/log/syslog after a reboot, so that I
can see what's happening on shutdown?
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Martin, I'm seeing a regression for this with systemd 228-2ubuntu1 in Ubuntu
Xenial.
Now I again have to remove the "ExecStop=/sbin/ifdown %I" stanza in order to
get netbooted clients to shut down.
Maybe something else is stopping the ifup service on shutdown now?
I tried to downgrade to the
** Changed in: systemd (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown
** Changed in: systemd (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown even
Thanks a lot Martin, works fine for me.
/me reverts the LTSP workaround...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown
This bug was fixed in the package systemd - 225-1ubuntu7
---
systemd (225-1ubuntu7) wily; urgency=medium
* Don't restart logind on upgrades any more. This kills X.org (#798097)
while logind doesn't save/restore its open fds (issue #1163), and also
gets confused about being
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: Debian Bug tracker #761909
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761909
** Also affects: systemd (Debian) via
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=7b9a61f1
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492546
Title:
Systemd runs ifdown on shutdown even when it
This also affects LTSP, e.g. Wily clients can't shutdown because
/sbin/poweroff is no longer accessible once ifup@.service unmounts
/dev/nbd0.
If systemd is fixed in Ubuntu before 15.10 is released, problem solved,
otherwise we'll need to commit the following in upstream LTSP.
Script
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ltsp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
27 matches
Mail list logo
