Erwan David wrote: > I have a problem that services are started on a server I manage before > link is UP. This leads to some services failing, or not bound to every > addresses :
Please say what release track you are using? Unstable, Testing, Stable? Please say whether you are using parallel boot or not. Running 'insserv' manually and noting any errors and reporting them would be very useful. # insserv -v insserv: creating .depend.boot insserv: creating .depend.start insserv: creating .depend.stop > You can see that ntpdate is started before network is ready. What is > more annoying is that I get an IPv6 prefix through dhcpv6 prefix > delegation, and even though the logs do not appear here, it seems the > dhcpv6 request is sent (by dibbler-client) before NIc is UP, which leads > to my prefix not being routed to my server. > > Against which package should I report a bug, and is there a workaround > for next reboot ? The 'ntpdate' package is obsolete. You should remove it and let ntpd do the task itself. I think that is very likely the problem. I think you have an old ntpdate package installed when it should have been removed. I think this old package is one (of possibly several) that is causing the boot sequence to be legacy mode instead of the current parallel mode controlled by insserv. I think because of those things the boot order is unhappy on your system. If the above guesses are correct then you will need to remove ntpdate. Then clean up other leftover files in /etc/init.d from packages that are possibly removed but not purged leaving the config files behind. dpkg -l | grep ^rc Then when 'insserv' is clean with no errors that things will be working correctly. Bob
signature.asc
Description: Digital signature
