[Bug 580319] Re: init.d controlled services launch before all interfaces are up, thus failing to start

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.3-0ubuntu6

---------------
upstart (1.3-0ubuntu6) oneiric; urgency=low

  [ Steve Langasek ]
  * Fix maintainer field to be compliant with policy definition

  [ Clint Byrum ]
  * conf/rc.conf: document events that are emitted by sysvinit
    jobs to quiet 'initctl check-config'
  * extra/conf/upstart-udev-bridge.conf: narrow definition to
    only the events actually emitted. (LP: #819928)
  * debian/conf/failsafe.conf: new job for critical services to
    start on.
  * conf/rc-sysinit.conf: start after static-network-up or failsafe
    so that runlevel 2 is only entered with all static net interfaces
    up. (LP: #580319)
 -- Clint Byrum <clint at ubuntu.com>   Wed, 10 Aug 2011 08:44:43 -0500

** Changed in: upstart (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/580319

Title:
  init.d controlled services launch before all interfaces are up, thus
  failing to start

Status in “dhcp3” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “dhcp3” source package in Lucid:
  Triaged
Status in “upstart” source package in Lucid:
  Confirmed
Status in “dhcp3” source package in Maverick:
  Triaged
Status in “upstart” source package in Maverick:
  Confirmed
Status in “dhcp3” source package in Natty:
  Invalid
Status in “upstart” source package in Natty:
  Triaged

Bug description:
  My server's (primarily a NAT box/802.11g hotspot) network
  configuration:

  Ubuntu release: 10.04 LTS
  External interface: eth3
  Internal interface: br0 (bridging eth2 and wlan0)

  I run dhcp3-server on my internal interface to supply private
  (192.168.*) IP addresses to wired and wireless devices throughout my
  apartment.

  I recently upgraded this server from 8.04 LTS to 10.04 LTS. After the
  upgrade I've faced some problems with the startup process. The issue
  I'm reporting here has to do with dhcp3-server failing to start during
  boot.

  From what I can tell, upstart begins bringing up br0, which takes perhaps 15 seconds. While br0 is coming up (and still has an address of 0.0.0.0), the dhcp3-server init script is started, but fails because 0.0.0.0 is not a declared network and dhcpd fails to start, reporting:
  May 13 22:29:40 firewall dhcpd: No subnet declaration for br0 (0.0.0.0).
  May 13 22:29:40 firewall dhcpd: ** Ignoring requests on br0.  If this is not what
  May 13 22:29:40 firewall dhcpd:    you want, please write a subnet declaration
  May 13 22:29:40 firewall dhcpd:    in your dhcpd.conf file for the network segment
  May 13 22:29:40 firewall dhcpd:    to which interface br0 is attached. **
  May 13 22:29:40 firewall dhcpd:
  May 13 22:29:40 firewall dhcpd:
  May 13 22:29:40 firewall dhcpd: Not configured to listen on any interfaces!

  It seems that dhcpd should start (or restart) when upstart brings up
  the interfaces it is configured to listen on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/580319/+subscriptions