Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2019 00:39:34 +0900
From:      Takanori Watanabe <takawata@init-main.com>
To:        current@freebsd.org
Subject:   Re: CURRENT >r349150: boot failure in rc.conf.local
Message-ID:  <20190618153934.GA2996@sana.init-main.com>
In-Reply-To: <5baa0c45-6c3c-0156-283e-fce0439b2cfe@FreeBSD.org>
References:  <20190618110226.7a9dbb81@freyja> <5baa0c45-6c3c-0156-283e-fce0439b2cfe@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 18, 2019 at 09:03:17AM -0400, Jung-uk Kim wrote:
> On 19. 6. 18., O. Hartmann wrote:
> > On all CURRENT boxes running CURRENT > r349150 we face the very same boot
> > failure, if /etc/rc.conf.local is present (i.e. on CURRENT, 13.0-CURRENT #7
> > r349169: Tue Jun 18 10:34:13 CEST 2019 amd64):
> > 
> > The box boots and thentries to start services denominated
> > in /etc/rc.conf.local, like net/openldap-server (slapd). The box is then stuck
> > at "startingt slapd", hitting Ctrl-T shows state "running", but Ctrl-C does not
> > show any effect, except Ctrl-Alt-Del (if enabled) is effectively rebooting the
> > box. First I thought it might by a out-of-sync binary, but this phenomenon
> > spreads even over recently via make installed systems. Disabling OpenLDAP's
> > slapd at boot time gives my like rolling a dice the next service, named
> > (dns/bind914) or net/samba48 (samba_server) - you name it. The box gets stuck
> > forever and doesn't even start sshd to provide access. All boxes have IPv6
> > enabled as well as IPFW.
> > 
> > Another server running CURRENT (r349169, also amd64) without
> > utilizing /etc/rc.conf.local but with a bunch of jails is booting as usual!
> > 
> > What happened here? Does anyone do have a hint or might know the cause?
> 
> I had the same problem and reverting r349154 fixed the problem for me.
> 
> https://svnweb.freebsd.org/changeset/base/349154
> 
> FYI...
> 
> Jung-uk Kim

In my machine, some executable, such as chromium, perl will hang like you.
It is also fixed by reverting r349154. Thanks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190618153934.GA2996>