Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 005587946 for ; Wed, 7 Dec 2011 13:31:04 +0000 (UTC) Received: (qmail 27102 invoked by uid 500); 7 Dec 2011 13:31:03 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 26940 invoked by uid 500); 7 Dec 2011 13:31:03 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 26932 invoked by uid 99); 7 Dec 2011 13:31:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 13:31:03 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2011 13:31:00 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id EE86F104C75 for ; Wed, 7 Dec 2011 13:30:39 +0000 (UTC) Date: Wed, 7 Dec 2011 13:30:39 +0000 (UTC) From: "Dave Cottlehuber (Commented) (JIRA)" To: dev@couchdb.apache.org Message-ID: <312284594.49315.1323264639978.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1370482061.47244.1323210160003.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (COUCHDB-1357) Authentication failure after updating password in user document MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COUCHDB-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164383#comment-13164383 ] Dave Cottlehuber commented on COUCHDB-1357: ------------------------------------------- @pete the following might help. There are notes on raising # of FDs on both linux and windows in this thread http://erlang.org/pipermail/erlang-questions/2011-October/thread.html#61859 Try updating this in couchdb.bat assuming you're not running as a service: echo CouchDB %version% - prepare to relax... %ERL% -sasl errlog_type error -s couch +A 4 +W w -env ERL_MAX_PORTS 100000 +P 1000000 If you're running as a service then you'll need to use erlsrv.exe http://wiki.apache.org/couchdb/Quirks_on_Windows and http://www.erlang.org/doc/man/erlsrv.html instead. There is also a short test file in http://erlang.org/pipermail/erlang-questions/2011-October/061895.html to help confirm your changes were successful. I'm not by my windows box to confirm; I'll check back later. > Authentication failure after updating password in user document > --------------------------------------------------------------- > > Key: COUCHDB-1357 > URL: https://issues.apache.org/jira/browse/COUCHDB-1357 > Project: CouchDB > Issue Type: Bug > Affects Versions: 1.1.1 > Reporter: Filipe Manana > Attachments: 0001-Let-the-credentials-cache-daemon-crash-if-_users-db-.patch > > > From the report at the users mailing list: > http://s.apache.org/9OG > Seems like after updating the password in a user doc, the user is not able to login with the new password unless Couch is restarted. Sounds like a caching issue. > The only case of getting the cache consistent with the _users database content is if the _users database processes crash and after the crash user documents are updated. The cache daemon is ignoring the database crash. > The following patch updates the daemon to monitor the _users database and crash (letting the supervisor restart it) if the database process crashes. > Etap test included. > This might be related to COUCHDB-1212. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira