[Nix-dev] Upstart and networking events

Ludovic Courtès ludo at gnu.org
Thu Aug 28 09:40:24 CEST 2008


Hi,

Several Upstart jobs have "start on network-interfaces/started", notably
avahi-daemon, portmap and bitlbee.  Most of the time, these services get
correctly started.  However, sometimes, part of them don't get started,
and /var/log/messages reads this:

  Aug 28 09:10:04 nixey dhclient: Internet Systems Consortium DHCP Client V3.0.6

  ...

  Aug 28 09:10:05 nixey portmap[5321]: cannot bind udp: Address already in use

  ...

  Aug 28 09:10:06 nixey avahi-daemon[5375]: Registering HINFO record with values 'I686'/'LINUX'.
  Aug 28 09:10:06 nixey init: avahi-daemon process ended, respawning

  ...

  Aug 28 09:10:06 nixey init: avahi-daemon process ended, respawning
  Aug 28 09:10:06 nixey init: avahi-daemon process (5384) terminated with status 255

  ...

  Aug 28 09:10:07 nixey bitlbee[5350]: Couldn't parse address `127.0.0.1': Address family for hostname not supported
  Aug 28 09:10:07 nixey init: bitlbee process (5350) terminated with status 255
  Aug 28 09:10:07 nixey init: bitlbee process ended, respawning

  ...

  Aug 28 09:10:20 nixey dhclient: bound to XX.XX.XX.XX -- renewal in 769 seconds.


IOW, these services are started before `dhclient' completes, i.e.,
before the network interface is up.

I just noticed that the NTP job uses "start on ip-up" instead, and that
seems to do the right thing, i.e., ntpd is launched once the interface
is actually up.  However, there's no `ip-up' job, so where does that
name come from?

Thanks,
Ludo'.




More information about the nix-dev mailing list