Hi,

As I reply in the users list, since this is an Erlang problem, I think it can be solved by imposing a higher maximum ports limit with ERL_MAX_PORTS environment variable or/and +P option at erl command. The default limit is 1024 and Erlang chose that number for compatibility with all the operating systems. Maybe it would be a good idea for this option to be set in the .ini file by the users... (just a suggestion)

I hope this information will help.

Cheers,
CGS



On 12/07/2011 01:04 PM, Filipe Manana (Commented) (JIRA) wrote:
     [ 
https://issues.apache.org/jira/browse/COUCHDB-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164343#comment-13164343
 ]

Filipe Manana commented on COUCHDB-1357:
----------------------------------------

Pete, I'm not sure this issue relates directly yo your issue.
 From the error {error,system_limit, it seems your system reached the maximum 
limit of available file descriptors. I have no idea how to increase this limit 
on Windows, perhaps Dave can help here.

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



Reply via email to