Hi Mike, On Sat, Nov 29, 2014 at 04:09:09PM +0000, Mike Crowe wrote: > Package: tftpd-hpa > Version: 5.2+20140608-3 > Severity: important > Tags: patch > > Dear Maintainer, > > When a Wheezy or Jessie machine is fitted with an SSD the machine often > boots so quickly that tftpd-hpa is started before the network is fully > configured. The problem is reproducible with sysvinit (on Wheezy) and > systemd (on Jessie) although it may be easier to reproduce with systemd.
What are you using to set up your network? If it's ifupdown, then for sysvinit I'm going to guess you're hitting a known bug with allow-hotplug, that bites more than just this service. Most people fix that by using 'auto' instead of allow-hotplug. For systemd it's a bit more complicated, but I believe that should also work for Jessie with it too, at least once the udev settle fix is restored to it (if it hasn't been already). If you're using something else, it would probably be good to get that information on the record, since there may still be more than one bug here which people should give some attention to. > The same problem can be observed by attempting to start tftpd-hpa by hand > when no network connections are available. > > When tftpd-hpa fails to start daemon.log contains: > > in.tftpd[881]: cannot resolve local IPv4 bind address: 0.0.0.0, Name or > service not known > > The error appears to be due to getaddrinfo(3) failing when attempting to > look up "0.0.0.0:69". > > The daemon starts successfully when the network is unavailable if the > default /etc/default/tftpd-hpa is changed: > > -TFTP_ADDRESS="0.0.0.0:69" > +TFTP_ADDRESS=":69" > > This has the side effect of making tftpd-hpa also listen on IPv6. Perhaps > that's desirable anyway so changing the default would make sense. > > The attached patch is my attempt to change the default. Thanks for that. I'm going to need to give the consequences of doing this a bit more thought than I have for it right this moment, but I'll try to do that sometime soon. Cheers, Ron -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
