Your message dated Tue, 12 Jan 2016 23:20:11 +0000
with message-id <[email protected]>
and subject line Bug#810656: fixed in ifupdown 0.8.8
has caused the Debian Bug report #810656,
regarding ifupdown: deadlocks: A start job is running for LSB: Raise network
interfaces
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
810656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.7.53.1
Severity: normal
Dear Maintainer,
I am reporting from a different computer because the affected computer
is still deadlocked, but the system information below is largely the
same because both (64-bit Intel) computers have been updated today to the latest
version of jessie after not updating for roughly a month in each case.
I was going to add this additional report to
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218>, but that one
has been closed so apparently I have to start a new bug report for this
on-going issue.
This fairly modest recent update made the other computer unbootable. The
last message in the boot sequence is
"A start job is running for LSB: Raise network interfaces. (HHh MMmin SSsec /
no limit)
where HH is now up to 3 (hours). Ctrl-C doesn't break the deadlock
and if I type ctrl-alt-del, then the boot sequence is gone through
again until this same deadlock is reached.
>From skimming through the comments in bug 754218 I had the impression
that jessie had been fixed in this regard in the sense that when
deadlocks like this occurred, it would eventually timeout. That
appears not to be the case from both HH being so high above and also
the "no limit" in the message.
So can we have an immediate Jessie fix for that unlimited timeout at
least? A slowly booting machine is far preferable to one that won't
boot at all. :-)
Also, could someone here give clear directions about how to get out of
the current deadlock so I can use that other computer or is a rescue
distro like RIP necessary to get that computer working again? Note
again, ctrl-C has no effect and ctrl-alt-del just reboots into the
same deadlock again.
>From previous experience with this deadlock on my current computer, I
suspect this deadlock was caused because of the following stanza in
/etc/network/interfaces on the currently deadlocked system (with the
pre-up commands commented out on my current computer to avoid the
deadlock).
auto eth0
iface eth0 inet dhcp
pre-up [ -f /etc/init.d/ferm ]
pre-up /etc/init.d/ferm start >| /tmp/ferm.out 2>&1
The point of those two pre-up commands (which I have used on Debian
for a very long time) was to work around a slight ferm issue where the
configured firewall is put into place by ferm after networking is up,
and I prefer to do that before (on at least non-NFS systems like this
one where /etc/init.d/ferm is available regardless of networking) to
avoid that small gap in firewall coverage.
Up to today's modest update the above pre-up commands were not causing
any trouble on that system (which has a USB stick drive rather than
a normal HD) so I did not comment them out.
Could you advise me how to get the above ferm workaround to work on
non-NFS systems like this one (and also my present one) without generating a
deadlock?
In sum I need (1) a quick fix so the timeout is not indefinite, (2) a
cookbook how to get out of this deadlock without resorting to a rescue
distro, and (3) advice on how to use pre-up like above without
running into deadlock trouble.
Thanks in advance for your help with these issues.
Alan
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ifupdown depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii iproute 1:3.16.0-2
ii iproute2 3.16.0-2
ii libc6 2.19-18+deb8u1
ii lsb-base 4.1+Debian13+nmu1
Versions of packages ifupdown recommends:
ii isc-dhcp-client [dhcp-client] 4.3.1-6
Versions of packages ifupdown suggests:
ii net-tools 1.60-26+b1
ii ppp 2.4.6-3.1
pn rdnssd <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ifupdown
Source-Version: 0.8.8
We believe that the bug you reported is fixed in the latest version of
ifupdown, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guus Sliepen <[email protected]> (supplier of updated ifupdown package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 12 Jan 2016 23:50:29 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source amd64
Version: 0.8.8
Distribution: unstable
Urgency: medium
Maintainer: Guus Sliepen <[email protected]>
Changed-By: Guus Sliepen <[email protected]>
Description:
ifupdown - high level tools to configure network interfaces
Closes: 761909 810656 810779
Changes:
ifupdown (0.8.8) unstable; urgency=medium
.
[ Martin Pitt ]
* Fix ifquery crash if interface state file does not exist yet.
(Closes: #810779, LP: #1532722)
* [email protected]: Avoid stopping on shutdown via stopping system-ifup.slice
(changed behaviour in systemd 228). (Closes: #761909, LP: #1492546)
.
[ Guus Sliepen ]
* Remove quotes around TimeoutStartSec parameter. Closes: #810656
Checksums-Sha1:
eabd26ed94cfee0bbf854978b9c06e63614b23c9 1536 ifupdown_0.8.8.dsc
0a51eb8b21a450dda1f63406e5bd12558a870372 71384 ifupdown_0.8.8.tar.xz
d3f161fa34a9d23d57834f79d4b4991e7194c441 60084 ifupdown-dbgsym_0.8.8_amd64.deb
52dcadb8bf50188a55d33c4dc90c40c984e73cf4 72590 ifupdown_0.8.8_amd64.deb
Checksums-Sha256:
75e84414680d7075116a92d582e78592a418dc7c66ddbb811d8913fbf172f156 1536
ifupdown_0.8.8.dsc
180edaaa6de99e4e74de7229481edf74361b8e8468462842618a42a952a26c0e 71384
ifupdown_0.8.8.tar.xz
300a239b82f898625571fb102cfe96b3f4c787622ffd8393a5818f420ef03ed8 60084
ifupdown-dbgsym_0.8.8_amd64.deb
6b7d9157bb801d578fc18e3567f942dff92e7e786ccfacc170eed760c3a905cb 72590
ifupdown_0.8.8_amd64.deb
Files:
9d5e60a170d5f4a1d67cd8dca47cac33 1536 admin important ifupdown_0.8.8.dsc
1aae907459a1bb030aae1b3249830009 71384 admin important ifupdown_0.8.8.tar.xz
21f953ec69fdfd4115b28320a8bfaaa5 60084 debug extra
ifupdown-dbgsym_0.8.8_amd64.deb
6080b35d845d1202257d2bca2d1255a2 72590 admin important ifupdown_0.8.8_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWlYNWAAoJED9JDeuHHvn6l+MQAJMe+Mr+wiS1dfo9yOdbI6Nm
ZNuHL+5WHj7hyYufQjNKsA2kwLHWWFcOKqh7+RwhHUEBC2EllrQiNugiAW0VSq73
0bA/7WBpqbRGdXeu9QOdUJox+koBPsI9+LZnKSJrU24W9DSS3CCDJTc9Dqr9Hb5P
8876+GG26+DIQkJzsdrNXpWBSUVBu5Gt/bG6TaVp6SL2XXx2yGBdDSDxdRRW90+q
JZLz8uD/C/D1FbTPoM6ZJl9yZnFBM1mL0WVUywtAOVBjPM0aKdygdU4qAI4SVOnw
4Dpb5mz2RzOjruMKS2cfIBk0sLHcA9QXQEAmbyRpTEmJvr90eQTVcHj1GU8KFW1Q
TEl9Qfsg7u72parB4LMV2R/vm59ElJTXDSNEYCjR4tgEv7jLyOC4O6AiWZwLmj5s
4KseBQ9r43YVHDAD3RTt4XDuBA0z16keyEY/ysv41xumM1Xq8/cDQyQTHalndilb
kF1UqXHtTnWNCsPNcqfsRG1sbywWZWWxWSSH90SUX2yNnBBzcJ/DlPbaCLcBc8VJ
cd90qnUGnxORfxR16IRm1nVVw0wXkYXl3RA5/fBIuo7vL5ozXCAKu/0nVNY4w1Qs
gPlDWjsxuDX1TfaNOLpfSfzDmUkDSPgIWZpq4q38aS0VCoti4si4xPEWqUEG2mWW
XhUG8f9rbK36MFg+M3xL
=lHyo
-----END PGP SIGNATURE-----
--- End Message ---
