couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pete Vander Giessen (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1357) Authentication failure after updating password in user document
Date Thu, 08 Dec 2011 23:43:40 GMT


Pete Vander Giessen commented on COUCHDB-1357:

I managed to reproduce the bug :-)

I started couch w/ the following in the invocation:
-env ERL_MAX_PORTS 256 +P 256

(I tried setting the ports lower, but couch wouldn't start at all if I set it too low.)

Then I visited futon on a linux server with about 100 databases. This opened enough files/ports
to trigger the system limit. 

Here's what I saw:
1) Couch continued to run, and my admin user could log in, but I couldn't log in with any
users in the _users database. 
2) The log got ... noisy. Here's the first error:
[Thu, 08 Dec 2011 23:36:00 GMT] [error] [<0.84.0>] Unexpected message, restarting couch_server:

> Authentication failure after updating password in user document
> ---------------------------------------------------------------
>                 Key: COUCHDB-1357
>                 URL:
>             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:
> 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:!default.jspa
For more information on JIRA, see:


View raw message