From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 03:55:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F37137B404; Mon, 28 Apr 2003 03:55:24 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id E946A43FD7; Mon, 28 Apr 2003 03:55:22 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 706724; Mon, 28 Apr 2003 05:55:22 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id C6D2578C66; Mon, 28 Apr 2003 05:55:21 -0500 (CDT) Date: Mon, 28 Apr 2003 05:55:21 -0500 From: "Jacques A. Vidrine" To: Vallo Kallaste , freebsd-current@freebsd.org, Tim Robbins Message-ID: <20030428105521.GB2676@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Vallo Kallaste , freebsd-current@freebsd.org, Tim Robbins References: <20030428075916.GA53857@myhakas.internal> <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <20030428075916.GA53857@myhakas.internal> <20030428080505.GA1474@chihiro.leafy.idv.tw> <20030428075916.GA53857@myhakas.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <20030428080505.GA1474@chihiro.leafy.idv.tw> <20030428075916.GA53857@myhakas.internal> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 Subject: Re: Somethings still up with new NSS? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 10:55:24 -0000 On Mon, Apr 28, 2003 at 10:59:16AM +0300, Vallo Kallaste wrote: > Hi > > Some moments ago "lost" all the users on my remote home system. Not > a big problem, but here's what I did. Sources (and world) are from > Apr 26. Seems like a problem with new ondisk format of spwd.db or > similar. > Sequence which broke: > logged on remotely > su to root, changed inetd.conf file to enable ftpd, killall -HUP > inetd > back to normal user, changed my password with passwd(1) > tried to connect to ftpd, no luck > As I had ssh session still up, looked into logfiles and found that > root user does not exist, hmm.. tried to su -, same story, tried su > to normal user.. you got the idea. > On Mon, Apr 28, 2003 at 04:05:05PM +0800, leafy wrote: > This is a *me too* post. > What I did was "portinstall postgresql" and during the install phase, > it complained about "postgre user disappeared during update" and my root > user was gone too. A 'vipw' saved my ass but can I be sure that it won't > happen again? On Mon, Apr 28, 2003 at 07:02:09PM +1000, Tim Robbins wrote: > I had this happen to me. In my case, I changed my shell, logged out, then > tried to log back in again. The console showed that sshd couldn't find my > account, and I don't think it couldn find the privsep account either. I could > not log in as root at the console either. I fixed the problem by booting > single-user and re-running pwd_mkdb. The entries in master.passwd and passwd > were correct, but I think that for some reason they weren't being read > correctly from the database. I thought the relative dearth of critical bug reports so far was too good to be true :-) Sounds like I have introduced a bug into `pwd_mkdb -u', which is the common denominator in your reports. `passwd', `chsh', `pw' all use `pwd_mkdb -u', whereas vipw uses plain `pwd_mkdb'. I will look at it closely today! Meanwhile, if this happens to you, just run `vipw' or `pwd_mkdb' to rebuild your database. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se