On 2016-02-17 13:47, Mark Brown wrote: > Hi, > > There's a bug open in Debian about AICCU not starting when used with > systemd (though it's most likely not that specifically). One of the > last things in the bug log is: > > | Actually, a concise problem statement would be a good thing to have, as > | it seems completely lost in the bug report. > > Let me try to provide that... We now no longer have the problems in the > original report with the boot hanging but we still don't have AICCU > coming up reliably at boot.
You should start AICCU when you have proper connectivity (time synced, DNS resolving works, and you can actually can make connections outbound). Doing it to early is not the way to do it. This is not something that AICCU can do, as it does not know when your system is "connected to the Internet", only the user behind the machine knows this. > There's probably some init based fix for this but I'd also expect AICCU > to handle this more gracefully by retrying resolver failures, it seems > like this is something that is reasonably likely to happen during the > startup process. As AICCU cannot resolve your DNS issue and only an administrator of the machine, or the DNS service, or the connectivity provider etc can, AICCU cannot resolve this and thus restarting it or letting it retry does not resolve the problem. Greets, Jeroen
