incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Cottlehuber <d...@muse.net.nz>
Subject Re: [jira] [Commented] (COUCHDB-536) CouchDB HTTP server stops accepting connections
Date Sun, 10 Apr 2011 21:13:01 GMT
2011/4/11 Stefan Kögl (JIRA) <jira@apache.org>

>
>    [
> https://issues.apache.org/jira/browse/COUCHDB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018086#comment-13018086]
>
> Stefan Kögl commented on COUCHDB-536:
> -------------------------------------
>
> The same just happened to me with version 1.0.2.
>
> [Sun, 10 Apr 2011 14:08:33 GMT] [error] [<0.7746.77>]
> {error_report,<0.30.0>,
>    {<0.7746.77>,crash_report,
>
> [[{initial_call,{mochiweb_socket_server,acceptor_loop,['Argument__1']}},
>       {pid,<0.7746.77>},
>       {registered_name,[]},
>       {error_info,
>           {exit,
>               {error,accept_failed},
>               [{mochiweb_socket_server,acceptor_loop,1},
>                {proc_lib,init_p_do_apply,3}]}},
>
[...]


> >
> > Having 3 Couches all replicating a couple of databases to each other
> (pull replication with a update notification process) the HTTP service on
> any of the Couches stops working at some point (when running for a couple of
> ours with constant changes on all databases and servers).
> > This is the error when a new HTTP request comes in:
> > =ERROR REPORT==== 19-Oct-2009::10:18:55 ===
> >     application: mochiweb
> >     "Accept failed error"
> >     "{error,enfile}"
> > [error] [<0.21619.12>] {error_report,<0.24.0>,
> >     {<0.21619.12>,crash_report,
> >
>  [[{initial_call,{mochiweb_socket_server,acceptor_loop,['Argument__1']}},
>


> > To me this seems like it runs out of threads or sockets to handle the new
> connection or somewhat like this.
>

Correct, in both cases its worth confirming what limit/ulimit (depending on
your platform) is in place for the couch user & seeing if you can bump this,
and then bumping env var ERL_MAX_PORTS as well.

More info @

http://wiki.apache.org/couchdb/Troubleshooting
http://www.erlang.org/doc/efficiency_guide/advanced.html


> > Also i see in this setup that if i put lots of changes in a short time at
> some point the replication process hangs (never finishes) and when trying to
> restart the same replication once again is not possible and resulting in a
> timeout.
>
> This doesn't sound good, can you provide more details?

A+
Dave

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message