fails if network is not yet configured at runlevel 2

[Serge Hallyn]

If network is not yet configured at runlevel 2, then the upstart job thinks tftpd is running, but ps -ef shows it is not. This happens on my laptop which normally comes up with wireless, and on which I set up wired by hand later. It can trivially be reproduced with a container where the lxc.network bits are replaced with

lxc.network.type = empty

If I then try

'sudo start tftpd-hpa'

this fails because it thinks it is running, but if I do

sudo restart tftpd-hpa

that works.

[Serge Hallyn (serge-hallyn)]

more detailed reproduction instructions:

lxc-create -t ubuntu -n 1
lxc-start -n q1
  (inside container) sudo apt-get -y install tftpd-hpa; sudo poweroff
sudo sed -i '/lxc.network/d' /var/lib/lxc/q1/config
echo "lxc.network.type = empty" | sudo tee -a /var/lib/lxc/q1/config
sudo lxc-start -n q1
  (inside container) sudo status tftpd-hpa; ps -ef | grep tftp; sudo start tftpd-hpa; sudo restart tftp-hpa

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Steve Langasek (vorlon)]

Does this generate any output in /var/log/upstart/tftpd-hpa.log?

Chances are, the service is exiting at an unexpected moment during startup. This may be an upstart bug rather than a tftpd bug.