[lug] Debugging a startup problem

[Davide Del Vento]

If the problem is reproducible, try also removing and reattaching the eth
cable and see if that makes the 30 minutes wait become "as soon as the
cable goes out-and-then-in". Watch the logs for clues while doing so...

On Sun, Jul 8, 2018 at 8:09 PM, Jed S. Baer <blug at jbaer.cotse.net> wrote:

> On Sun, 8 Jul 2018 19:42:09 -0600
> Lee Woodworth wrote:
>
> > If you don't already have some kind of verbose logging enabled
> > for init scripts during boot, I would turn that on.
> >
> > Maybe this would help (search terms linux upstart verbose logging):
> >      https://serverfault.com/questions/601806/upstart-
> script-not-logging-to-file
>
> Hey, that looks like fun. Just add --debug to the end of the kernel
> command line at boot. grep will be my friend.
>
> > I had a machine hang during boot because it was mounting a
> > non-existent nfs export. Ntp can also cause hangs (e.g. ntp-client),
> > dns lookup failures can also cause issues.
>
> No NFS here, and ntp (I use chrony, actually) would come later, after the
> network starts.
>
> > You probably know this already, but in my experience power supplies
> > and their fans are the root causes of many system failures. So
> > if you start vacuuming, the power supply and case fans may also
> > benefit from attention.
>
> Been there, done that. Too many times. Wore out the t-shirt. I don't
> suspect it in this case. It'll be Wednesday at the soonest before I try
> to tackle this.
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20180708/6efef39c/attachment.html>