compat: upstart not starting /etc/init.d/firehol and no log available

Bug #490286 reported by ceg
258
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NULL Project
Invalid
Undecided
Unassigned
firehol (Ubuntu)
New
Undecided
Unassigned
upstart (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Package firehol installs with an /etc/init.d/firehol script and it used to nicely start firehol if enabled in /etc/default/firehol.

This does not work in 9.10, iptables remain empty after boot. And I could not find or enable any bootlogs.

Revision history for this message
ceg (ceg) wrote :

I have checked that symlinks in /etc/rc?.d exist.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Upstart does not start /etc/init.d init scripts unless your distribution provides some kind of compatibility scripts (usually just the old sysvinit script). Please file a bug with your distribution.

Changed in upstart:
status: New → Invalid
affects: upstart → null
Revision history for this message
ceg (ceg) wrote :

Thanks for pointing out that the bug belongs to the compat scripts then.

affects: firehol (Ubuntu) → ubuntu
description: updated
summary: - upstart not starting /etc/init.d/firehol and no log available
+ compat: upstart not starting /etc/init.d/firehol and no log available
Revision history for this message
ceg (ceg) wrote :

affects set to upstart-compat-sysv (ubuntu)

Revision history for this message
Victor Vargas (kamus) wrote :

I have reassigned this to a better package, instead firehol.

affects: ubuntu → firehol (Ubuntu)
Changed in upstart (Ubuntu):
status: New → Invalid
Revision history for this message
Johnathon (kirrus) wrote :

Scott, If the distribution is Ubuntu, Karmic Koala, then where should this bug be listed? Just invalidating it isn't that helpful ;-)

Revision history for this message
Johnathon (kirrus) wrote :

Firewall not coming up on system boot is a critical security issue.

security vulnerability: no → yes
Revision history for this message
ceg (ceg) wrote :

AFAIK the firehol init script is present and has not changed. (And works as expected when called.)

The suspecting package IMHO may well be an incomplete/broken upstart / -compat init procedure.

Revision history for this message
ceg (ceg) wrote :
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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