incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1357) Authentication failure after updating password in user document
Date Wed, 07 Dec 2011 13:30:39 GMT


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

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
and instead.

There is also a short test file in
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:
>             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