From owner-freebsd-ports@FreeBSD.ORG Thu Jun 2 10:17:51 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D679716A41C; Thu, 2 Jun 2005 10:17:51 +0000 (GMT) (envelope-from mark@antsclimbtree.com) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D06943D55; Thu, 2 Jun 2005 10:17:51 +0000 (GMT) (envelope-from mark@antsclimbtree.com) Received: from lilbuddy.antsclimbtree.com (adsl-69-232-30-131.dsl.snfc21.pacbell.net [69.232.30.131]) by pimout4-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j52AHjPA111632; Thu, 2 Jun 2005 06:17:50 -0400 Received: from 212.229.216.81.s-s.vf.siwnet.net ([81.216.229.212] helo=[10.11.11.32]) by lilbuddy.antsclimbtree.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.51 (FreeBSD)) id 1DdmmX-000GBY-Ga; Thu, 02 Jun 2005 03:19:09 -0700 In-Reply-To: <790a9fff050601150173d7bd34@mail.gmail.com> References: <790a9fff050601150173d7bd34@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <94f6a6f4db839f65d907d729e14a15ad@antsclimbtree.com> Content-Transfer-Encoding: 7bit From: Mark Edwards Date: Thu, 2 Jun 2005 12:17:19 +0200 To: Scot Hetzel X-Mailer: Apple Mail (2.622) X-Spam-Score: -5.9 (-----) X-Scan-Signature: f63531aa0682aad547f9b9ea86e9d875 Cc: ports@freebsd.org Subject: Re: FreeBSD Port: cyrus-sasl-2.1.21 -- Couldn't update db X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 10:17:52 -0000 On Jun 2, 2005, at 12:01 AM, Scot Hetzel wrote: > On 5/30/05, Mark Edwards wrote: >> When I use saslpasswd2 to set or change a password, I always get a log >> item saying that saslpasswd2 "Coudn't update db" even though the >> password is changed successfully, the db file is modified, and >> subsequent authentication with the new password succeeds just fine. >> >> An example: >> >> May 30 03:46:13 lilbuddy saslpasswd2: setpass succeeded for >> cyrus@mail.antsclimbtree.com >> May 30 03:46:13 lilbuddy saslpasswd2: Couldn't update db >> > Been a while since I used the cyrus-sasl ports, but when I was > updating them, I had added to pkg-install: > > echo "test" | ${PKG_PREFIX}/sbin/saslpasswd2 -p -c ${CYRUS_USER} > ${PKG_PREFIX}/sbin/saslpasswd2 -d ${CYRUS_USER} > > It would issue a warning, but still create a blank sasldb file. Then > as you add new users to the sasldb file, it shouldn't give you any > further warnings. > > NOTE: If you install with BATCH=yes, then pkg-install will not create > the blank sasldb file, and you will get a warning on the first user > added. > > Does the warning occur with the first user added (no previous > sasldb/sasldb2 file) or with every additional user added? It occurs every time saslpasswd2 updates the db. The db is successfully updated, but there is a warning issued. When saslauthd updates the db, no warning. I also get the following non-sensical warnings in /var/log/auth.log: Jun 2 02:03:49 lilbuddy imaps[61325]: no user in db Jun 2 02:18:30 lilbuddy exim: no user in db These occur when a user is SUCESSFULLY authenticated via an imaps connection, or via exim. In other words, just before these messages, there is a logged message declaring a successful authentication, so either sasl is just nuts, or there is some component of the authentication that is failing but not causing authentication to ultimately fail. Again, I have seen many complaints about this in Google searches, so I think it is a common issue. It doesn't seem to affect me adversely, its just annoying and log-cluttering. -- Mark Edwards mark@antsclimbtree.com cell: +46704070332