Your message dated Mon, 11 Jan 2016 22:22:16 +0000
with message-id <[email protected]>
and subject line Bug#810656: fixed in ifupdown 0.8.7
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.7

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: Mon, 11 Jan 2016 22:58:44 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source amd64
Version: 0.8.7
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: 311054 318577 365114 378506 419139 471926 482405 488315 597274 810656
Changes:
 ifupdown (0.8.7) unstable; urgency=medium
 .
   * Impose a 5 minute timeout for starting network services.
     Closes: #318577, #810656
   * Give an error when trying to up a dhcp interface when no DHCP client is
     installed. Closes: #471926, #419139
   * Add a section in the manual about extensions provided by other packages.
     Closes: #482405, #597274
   * Use absolute paths to binaries called by ifup/ifdown. Closes: #365114
   * Return an error when trying to ifup/ifdown/ifquery an unknown interface
     (unless it is ignored due to --allow or --exclude).
   * Ignore SIGPIPE. Closes: #311054
   * Update the bridge example. Closes: #488315
   * Use the onlink option when adding a gateway route. Closes: #378506
   * Also allow the metric option for tunnels and IPv6 interfaces.
Checksums-Sha1:
 2046256b81e023b2346392d9b22e16b032662bf3 1536 ifupdown_0.8.7.dsc
 8d5b719cb0fde00c90738b6ec12c3a0600e0ef4d 71236 ifupdown_0.8.7.tar.xz
 e0a2c8d6ba3d147d48a50b30b6d158bbc8fd5c0a 60042 ifupdown-dbgsym_0.8.7_amd64.deb
 237b25129f3b324b40904d421ee2bd6bffab1a27 72410 ifupdown_0.8.7_amd64.deb
Checksums-Sha256:
 42a38cf1a646f1a393f273c10c04376f8589e906ca0a5303d95b04199fe6f07a 1536 
ifupdown_0.8.7.dsc
 1ace4054ceeb64b4987c3bf99b9317ea6c4ae89da4a58ce5e33a0cbc218b8058 71236 
ifupdown_0.8.7.tar.xz
 14ccc723e89e08fccd170b2182a43059aaeddb37ad20e739e475c00ed8e8fc8d 60042 
ifupdown-dbgsym_0.8.7_amd64.deb
 d37cac4b9346f7a171d6fb329b93cd872f25080226224061af2692d3d17cee7f 72410 
ifupdown_0.8.7_amd64.deb
Files:
 4e2bb9404c3346de4948d4d4bea823f2 1536 admin important ifupdown_0.8.7.dsc
 0160c6c6b2cc627758fd8909a8139f9d 71236 admin important ifupdown_0.8.7.tar.xz
 3d7ba6cba423fcfd26a0bf9a092de6ff 60042 debug extra 
ifupdown-dbgsym_0.8.7_amd64.deb
 fc4e3c0d95bcd6429b5fecacc2281ad0 72410 admin important ifupdown_0.8.7_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWlCW6AAoJED9JDeuHHvn6w7MP+gMR8R3FC/2FDoDjcwV72ZKe
wY9qz+j9OsHAA8MNCVcTbqoBkf3PfvfaWRhBSUwbMRgW4jWMYqx0XzAIy4ite4Az
1D68hmd7dOr9CRWsFDk1EkYUzXWwfRwHNQ6QIbBnf+NnpfQkS7apXaNtw7iLqOPQ
EhpYxoQoRwY7X0jF/8azWYD0BLWWFpph636+wHcPN93eLNu6orJ7AfyTxVSKOHwV
4Qup/yDO17Eku4m0Uma1XZqQaNUNcjEhgIEc+cAxEhOYIXuQdNNdk9jpOpjmpqDM
iZF/jBqTrfsEWcM3siY4FkXW9bpM3pzbCby2nhS+OirQMK3UNT9dn5SJaqHhgamO
i/8aha5Fv4YlmrLKjne87N+R8PHtSGHqAYE8nWJqd4GjYAq96f8l+T9ltiVBdJ7D
nLYok1AyjZlrI0+I9z9dxry+/b/TvH7+1HYvtkgWycSMXt37e5+kaGLg5oT6zooR
1JxogSP5fcZ2LdM9e4cXgV+zy7iBEmk0KIsV2ZHstFu3ZpF3PK3vMYV0xrLLIWlY
MIhWYTV+moQK44XXVlLeroeHdK5pa4VPFNsnb5OvfuOOtRVUEAGZ0zJ2J1zRVtBU
9r8Z/9A0JX+HLkpiLrXjMTvDndQyyyZCXTvHg7yxL4CHGc1iEBeuHoTdGI6vk/N9
j1YGmlEi6+0L8iFB4Jm/
=xXoW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to