Network startup locks during init

Bug #6637 reported by Ulrik Mikaelsson
22
Affects Status Importance Assigned to Milestone
zeroconf (Ubuntu)
Fix Released
Medium
MOTU Reviewers Team

Bug Description

A day ago, I experienced a strange freeze during network initialization (preventing normal system startup). After some investigation I found out that the problem were in "ifup -a" and more specifically "ifup lo".

Further looking into the problem revealed that the problem seems to originate from /etc/network/if-up.d/zeroconf-up.

Changed in zeroconf:
assignee: nobody → motu
Revision history for this message
Jérémie Corbier (jcorbier) wrote :

Thank you for your bug report. Do you still experience this bug? The current version of zeroconf works fine for me.

Changed in zeroconf:
status: Unconfirmed → Needs Info
Revision history for this message
Ulrik Mikaelsson (rawler) wrote :

I've switched hardware and reinstalled since posting this bug. I have not experienced the problem since then, so I guess it's fixed. :)

Revision history for this message
Jérémie Corbier (jcorbier) wrote :

This problem is caused by the if-up.d script name change which occured between version 0.3-1 and 0.6-1. The previous one zeroconf-up is not deleted and causes problems with loopback interfaces.

Changed in zeroconf:
status: Needs Info → In Progress
Revision history for this message
Jérémie Corbier (jcorbier) wrote : Debdiff

It adds a postinst script which removes /etc/network/if-up.d/zeroconf-up if it exists.

Changed in zeroconf:
assignee: motu → motureviewers
Revision history for this message
Sebastian Dröge (slomo) wrote :

This will be fixed by bug #39555 so please don't upload this debdiff yet

Changed in zeroconf:
status: In Progress → Confirmed
Revision history for this message
Jérémie Corbier (jcorbier) wrote :

This is an adaptation of what the Debian maintainer does in his package but it contains a Debian policy violation:

http://www.us.debian.org/doc/debian-policy/ch-files.html#s10.7.3

Revision history for this message
Jérémie Corbier (jcorbier) wrote :

In fact, according to the Debian maintainer it may not be a policy violation.

Anyway, package is waiting for sync with Debian unstable zeronconf 0.8-2.

Changed in zeroconf:
status: Confirmed → In Progress
Revision history for this message
Jérémie Corbier (jcorbier) wrote :

Fixed with zeroconf 0.8-3.

Changed in zeroconf:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.