edubuntu-bugs team mailing list archive

[Diego Morales <morales@xxxxxxxxxxxxx>]

I have the same problem, using lucid latest package (5.0-11ubuntu2.1).

I have many interfaces configured in this machine, and nic bonding
configured. Upstart seems to raise tftp when the first bond interface
starts:

syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.923760] bnx2: eth1: using MSI
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.924441] bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full.
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.924451] bonding: bond0: enslaving eth1 as an active interface with an up link.
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.925317] bonding: bond0: setting mode to 802.3ad (4).
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.925348] bonding: bond0: Setting MII monitoring interval to 100.
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    3.925395] bonding: bond0: Setting LACP rate to fast (1).
syslog.2.gz:Jun 13 14:17:02 <hostname> in.tftpd[842]: cannot resolve local IPv4 bind address: 0.0.0.0, Name or service not known
syslog.2.gz:Jun 13 14:17:02 <hostname> init: tftpd-hpa main process (842) terminated with status 66
syslog.2.gz:Jun 13 14:17:02 <hostname> init: tftpd-hpa main process ended, respawning
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    4.129433] 802.1Q VLAN Support v1.8 Ben Greear <greearb@xxxxxxxxxxxxxxx>
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    4.129436] All bugs added by David S. Miller <davem@xxxxxxxxxx>
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    4.134009] bonding: bond0: link status definitely down for interface eth0, disabling it
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    4.134012] bonding: Warning: bond0: link status changed for uninitialized port on eth0
syslog.2.gz:Jun 13 14:17:02 <hostname> kernel: [    4.134017] bonding: bond0: now running without any active interface !

The "status tftpd-hpa" says the job is running, when it's not (should
THAT happen?). stop/start raises the program just fine.

I tried to change the condition to "(filesystem  and and started
networking)", but that seems to start it even earlier. I've changed it
to "(filesystem and net-device-up IFACE=bond0.80)" (bond0.80 is the last
bond interface) and then it worked.

But the problem may actually be that bondX is !=lo, and it may come up before any of its slaves be available, resulting in the 
"cannot resolve local IPv4 bind address: 0.0.0.0" error.

Should I open a new bug? If so, should it be on tftpd-hpa, or some other
package?

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/522509

Title:
  [FFE] tftpd-hpa doesn't start on boot

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