[
https://issues.apache.org/jira/browse/COUCHDB-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165339#comment-13165339
]
Pete Vander Giessen commented on COUCHDB-1357:
----------------------------------------------
@Dave and @Filipe: thank you for the advice. I've been playing around with
limits on my Linux server. It looks like I can get things pretty high by
juggling the stuff in ulimit, as well as the overall limits in security.conf,
in combination w/ ERL_MAX_PORTS and +P ...
One more question: is there are generic way to tell when a view server has
crashed, and we may need to restart couchdb? It sounds like I can make the
problem I ran into less likely to occur by increasing file/process limits, but
I'd like to add some sort of watchdog process that will let me know that I've
hit a limit, and that my _users view server, for example, may be crashed ...
Thank you,
~ Pete
> 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
