From owner-freebsd-hackers@freebsd.org Sun Aug 7 15:07:04 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 473FEBB02C7 for ; Sun, 7 Aug 2016 15:07:04 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E02E2127B for ; Sun, 7 Aug 2016 15:07:03 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-wm0-f67.google.com with SMTP id i5so11135726wmg.2 for ; Sun, 07 Aug 2016 08:07:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=ONl8V0CfuozCQucdwMcXXlQMFvUxdRY2VmqJA5rf9/w=; b=dSYgIEQbFEH/2egsOf2+NEQ85tT/tWTAQCDzZYCmHTyiPa2jgaoubb0ESrTmPxp0M8 xeEcXSC4+1tahhSWN+I1Od7MwyGBiKbU7QqYp2tSZA4M4s9qfj4sCXJ+eKB4mwoBysFq wwtVX2HV+Y4otF2WXV3pcs/SDqzM9XiBzIF/5HK8rI9JPmQQ16Q2dBBEniq8TtRv6rBf wIJXajaPeu5cHVm1sS0etuvetQtx4TTtfrnX8k2KWqXJ0bLK0W3HaYXCFIi8Urg6Xiii xdObSNjj8IrStvkiVZ5SgE1xTiBqL3GxadTzS8vmD34C5QfyS+5g5sBiLqUX5lX2s3N6 FCqA== X-Gm-Message-State: AEkoouuMKvmfYq45mgpFN+i1CKIoCobm3GSbHX96s/LERMej4aZV7+Ogp8AWlzM+4/TPlA== X-Received: by 10.28.63.21 with SMTP id m21mr12451829wma.77.1470582416133; Sun, 07 Aug 2016 08:06:56 -0700 (PDT) Received: from maka.fritz.box (dslb-178-005-164-211.178.005.pools.vodafone-ip.de. [178.5.164.211]) by smtp.gmail.com with ESMTPSA id v134sm18955134wmf.10.2016.08.07.08.06.54 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 07 Aug 2016 08:06:55 -0700 (PDT) From: Mateusz Piotrowski <0mp@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Cannot login in after running freebsd-update install Message-Id: <225F271C-004E-4A9B-B9EA-0CEA29961EE6@FreeBSD.org> Date: Sun, 7 Aug 2016 17:06:56 +0200 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2016 15:07:04 -0000 Hello, I just run `freebsd-update fetch && freebsd-update install`. Everything = went=20 rather smoothly except one error message which I ignored (I guess it was=20= cap_mkdb: potential reference loop detected but I am not sure). Unfortunately, I was unable to `login`, `su` and = `sudo`.=20 I was getting log messages like login_getclass: 'tc=3D' reference loop 'root' pam_acct_mgmt: error in service module I rebooted and booted in single user mode (since I couldn't log in when = I=20 started in multiuser mode). I tried to run cap_mkdb /etc/login.conf but I was getting the "cap_mkdb: potential reference loop detected" = every time. Apart from that I ran `mergemaster` and `freebsd-update rollback` but it = didn't=20 solve the issue. Finally, I fixed the issue by removing ":tc=3Ddefault:" from the = default login=20 class in /etc/login.conf and running `cap_mkdb /etc/login.conf` = afterwards. Why did `freebsd-update install` broke /etc/login.conf? Is there = anything I did wrong/could have done better? Cheers, -mateusz