Eric's fix works for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tftp-hpa in Ubuntu.
https://bugs.launchpad.net/bugs/972845
Title:
after upgrade to precise, service did not start
To manage notifications about this bug go
Nikolay has spotted the problem, same here...
terra in.tftpd[1397]: cannot resolve local IPv4 bind address: 0.0.0.0, Name or
service not known
I though upstart was supposed to have a dependencies system that
prevents things like this.
--
You received this bug notification because you are a
This service is not starting correctly at boot every time. A restart
will fix it.
jonsmirl@terra:~$ sudo service tftpd-hpa restart
tftpd-hpa stop/waiting
tftpd-hpa start/running, process 4178
jonsmirl@terra:~$
This is probably the problem I experienced on upgrade.
--
You received this bug
Public bug reported:
I had this service running under oneiric. After upgrade to precise it
didn't start. Trying to start it manually:
jonsmirl@terra:/etc/init.d$ service tftpd-hpa start
start: Rejected send message, 1 matched rules; type=method_call,
sender=:1.94 (uid=1000 pid=6233 comm=start
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tftp-hpa in Ubuntu.
https://bugs.launchpad.net/bugs/972845
Title:
after upgrade to precise, service did not start
To manage notifications about this bug go to:
