incubator-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 Tue, 06 Dec 2011 22:52:40 GMT


Pete Vander Giessen commented on COUCHDB-1357:

We ran into a similar issue, with 1.1.1. The problem seemed to start with a log entry that
looked like so:

[Thu, 01 Dec 2011 19:22:48 GMT] [error] [<0.31233.1889>] Uncaught
error in HTTP request: {error,system_limit}
[Thu, 01 Dec 2011 19:22:48 GMT] [info] [<0.31233.1889>] Stacktrace:

We had a cluster of 7 or so Windows users replicating 2 databases apiece from a "master" server
running on a Red Hat box. Each user also has a separate "user" database that they use to fetch
oauth credentials, so there were perhaps 16 databases in use at the time.

Next time this happens, I'll run netstat on the machine and save the output. For now, I've
saved off the logs, and can provide more complete logs upon request.
> 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: COUCHDB-1357-master.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