From nobody Thu Dec 23 01:20:37 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E73D2190C3CF for ; Thu, 23 Dec 2021 01:20:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JKC794TZRz3q13 for ; Thu, 23 Dec 2021 01:20:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7B1802776D for ; Thu, 23 Dec 2021 01:20:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1BN1Kb4n051885 for ; Thu, 23 Dec 2021 01:20:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1BN1KbDg051884 for bugs@FreeBSD.org; Thu, 23 Dec 2021 01:20:37 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260628] FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?) Date: Thu, 23 Dec 2021 01:20:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: osho@pcc-software.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1640222437; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=YsBRHa84AHICCzI8Mxri47UnUhMzuGzk6oiuOGZUEAw=; b=AmkhgGOhNz7/swPIEbg6owUhqxPuYfzDuh3oYw6CJHKU2AorT84vhIzjhjuhaw49naDceV 9txK/hxmBqs1V/uaexDG/QyMbXD3gydKr8H+3Jei36bkb9oKXRVI3wV2imdxNpATWGmUpv NP0sT+pAUnQiuLceIDcw+KmgPNddwf4sihvlQSg4JWX6bWDz35kjte1dRDDpjnP3ny/OD2 eiEdkQqYxghOM1dn3BGRAw+7gWr7I/vgKI1x+bOz+fva7sKAyvKCeGqGtqQLBhU/1l6SU5 R+28qgHMnfU0Dtw7TRd+8BfQxpF6scqJeF5okKmugJiC2juMA885R9aCut58Yg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1640222437; a=rsa-sha256; cv=none; b=G/ypNXTMy0YfnQ+UImOwz3/rJlSNDVR33HVJTw4oDiQsPEqg8sErxA8LkYRXe6+Ajuuci+ G5t3ebkekKO1+cVc+XdBkERL0qkerLv3lnVSYIrgRl3sWz/WsquXEQGZmDYGwVvdk5L/Um JspCVzx+SssHhL2R/OEFSKBxqA2TmnTdmt8FUXhQBrbXaYYfZRkPHQy3K1RTl1+wzLpR50 aZWE+nN+aP7uB9qU22PoSSI1otloU+xoGv1VnkOBRG3cDWr3iaozNH/u9v57cq+KWqgEyZ 5wfKtayM6BIKJrLUl8z/Ya3QqddGnjbraw/pg83xbrMwcn9eqLzgPZO0U+PfWg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260628 Bug ID: 260628 Summary: FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?) Product: Base System Version: 12.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: osho@pcc-software.org What is the issues? 1. FreeBSD 12.3R got stuck during the boot. 2. password database seems not be referred after I made password database to skip reading compat. What is the expected behavior? 1. FreeBSD 12.3R should boot without getting stuck even if ldap is configur= ed. 2. when I type a user's password, FreeBSD should recognize it and allow the user to login. When I made the user's password blank, FreeBSD should allow them to login without typing password. That should also be true for root. What happened? 1. I used freebsd-update to update from 12.2-Release to 12.3-Release. I typ= ed following commands to upgrade. # freebsd-update -r 12.3-RELEASE upgrade (typed 'y' twice because the shown message looked reasonable) # freebsd-update install As mentioned, I have rebooted the computer. # reboot FreeBSD booted with 12.3R kernel. To make all packages use the latest library, I force upgraded packages. # portmaster -a -f Then, I typed freebsd-update again to finalize the install. # freebsd-update install # reboot During the reboot, it got stuck on booting after starting devd. Since it did not respond about 10 minutes, I hit power button. The computer seems to understand power button and started the shutdown procedure. I felt ACPI working well. I booted the computer and in the first count-down menu, I typed 's' to make= it go into the single user mode. I could go into the single user mode shell eventually. I saw the message saying: 2021-12-22T17:13:00.321721+09:00 init 28 - - NSSWITCH(_nsdispatch): ldap, passwd_compat, endpwent, not found, and no fallback provided. I supposed something wrong with nsswitch. I typed following command to mount all with writable. # mount -u -a However, as far as I checked with mount / seems to be read-only. I explicit= ly asked it to mount '/' with writable. # mount -u / Since I supposed boot process got stuck for fails to access LDAP, I removed +::: in password and groups. # vipw # vi /etc/group Then, I exited and made it goes into multi-user mode. During RC execution,= I saw several suspicious messages like: /etc/mail/submit.cf: 441: readcf: option RunAsUser: unknown user smmsp (snip) Mail submission program must have RunAsUser set to non root user /etc/rc: WARNING: failed to start sendmail_msp_queue (snip) Performing sanity check on sshd configuration. Privilege separation user sshd does not exist /etc/rc: WARNING: failed precmd routine for sshd (snip) Starting jails: jail: : unknown uid 0 (snip) I felt password database cannot be read on 12.3R. Moreover, nsswitch might have some issues with 12.3R. I gave up on updating and chose to rollback. i.e. reboot with single user m= ode, mount / with writable and executed the following command. # freebsd-update rollback Here, rollback got stuck (no progress for 30 minutes) but I decided to rebo= ot anyway. The system booted and I typed the command again to rollback and reb= oot. It seems to work well. Anything special for your config? The machine use ldap for extra password and group. It has a ldap server in= side a jail running on the same machine, and to avoid getting stuck on reading l= daps during the boot, it does not refer ldap for groups. However, the issue continued after I removed +:::... lines in password, it might not be related. --=20 You are receiving this mail because: You are the assignee for the bug.=