how to troubleshoot services startup on reboot

[Sergei G]

I know about the service -e command.  However, that's of little help when
it comes to service startup order.

I've had this problem in the past with FreeBSD Hyper-V guest, because it
was taking too long to obtain IP from DHCP.  I even had to set a setting to
make it wait to obtain IP prior to proceeding with the rest of boot.

On Mon, Mar 28, 2016 at 11:05 AM, Kevin P. Neal <kpn at neutralgood.org> wrote:

> On Mon, Mar 28, 2016 at 10:57:00AM -0700, Sergei G wrote:
> > I have service startup failure probably due to DNS resolution.  I think
> > that local unbind is not available during some services startup.  For
> > example, nginx reports failure to resolve network names and fails to
> start.
> >
> > However, there is little I can obtain about service startup order from
> > logs, because there is no entry like "starting local unbind" in
> > /var/log/messages.
>
> Use the 'service' command. Try 'service -e', but I'm not 100% sure if it
> will print all enabled services. But 'service -r' will show you everything
> including the stuff that is turned off.
> --
> Kevin P. Neal                                http://www.pobox.com/~kpn/
>
> "It sounded pretty good, but it's hard to tell how it will work out
> in practice." -- Dennis Ritchie, ~1977, "Summary of a DEC 32-bit machine"
>