Firestarter breaks networking during bootup

Bug #932485 reported by Benjamin Kerensa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firestarter (Ubuntu)
High
Unassigned

Bug Description

During bootup FIrestarter is causing my networking to hang by causing a "Waiting 60 more seconds for network configuration" message which causes my system about 3-5 minutes of extra boot time.

Here is a helpful bit from logs:
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything.
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail!
invoke-rc.d: initscript firestarter, action "restart" failed.
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
Failed to bring up lo.
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything.
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail!
invoke-rc.d: initscript firestarter, action "restart" failed.
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
Failed to bring up lo.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firestarter 1.0.3-10
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 14 17:52:47 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firestarter
UpgradeStatus: Upgraded to precise on 2012-02-10 (4 days ago)

Revision history for this message
Benjamin Kerensa (bkerensa) wrote :
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

This is similar to bug #132039, but the severity is much worse now because ifupdown in precise will error out when a hook script fails and not process the rest of the hooks. This means that any number of integration scripts will fail to run correctly when firestarter is misconfigured (or unconfigured, since /etc/init.d/firestarter restart by default tries to call a script that's not created on package install!), which could be a much more serious problem than a 60-second boot delay.

Changed in firestarter (Ubuntu):
status: New → Triaged
importance: Undecided → High
importance: High → Critical
importance: Critical → High
Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in firestarter (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers