Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Sun, 10 Apr 2011 14:17:05 +0000 (UTC)
From: =?utf-8?Q?Stefan_K=C3=B6gl_=28JIRA=29?= <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <863467219.47815.1302445025727.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-536) CouchDB HTTP server stops
 accepting connections
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COUCHDB-536?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D130=
18086#comment-13018086 ]=20

Stefan K=C3=B6gl 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}]}},
       {ancestors,
           [couch_httpd,couch_secondary_services,couch_server_sup,<0.31.0>]=
},
       {messages,[]},
       {links,[<0.102.0>]},
       {dictionary,[]},
       {trap_exit,false},
       {status,running},
       {heap_size,233},
       {stack_size,24},
       {reductions,200}],
      []]}}


> CouchDB HTTP server stops accepting connections
> -----------------------------------------------
>
>                 Key: COUCHDB-536
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-536
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 0.10
>         Environment: Ubuntu Linux 8.04 32bit and 64bit with Erlang R13B01
>            Reporter: Simon Eisenmann
>            Priority: Critical
>
> Having 3 Couches all replicating a couple of databases to each other (pul=
l replication with a update notification process) the HTTP service on any o=
f the Couches stops working at some point (when running for a couple of our=
s with constant changes on all databases and servers).
> This is the error when a new HTTP request comes in:
> =3DERROR REPORT=3D=3D=3D=3D 19-Oct-2009::10:18:55 =3D=3D=3D
>     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'=
]}},
>        {pid,<0.21619.12>},
>        {registered_name,[]},
>        {error_info,
>            {exit,
>                {error,accept_failed},
>                [{mochiweb_socket_server,acceptor_loop,1},
>                 {proc_lib,init_p_do_apply,3}]}},
>        {ancestors,
>            [couch_httpd,couch_secondary_services,couch_server_sup,<0.1.0>=
]},
>        {messages,[]},
>        {links,[<0.66.0>]},
>        {dictionary,[]},
>        {trap_exit,false},
>        {status,running},
>        {heap_size,233},
>        {stack_size,24},
>        {reductions,202}],
>       []]}}
> [error] [<0.66.0>] {error_report,<0.24.0>,
>     {<0.66.0>,std_error,
>      {mochiweb_socket_server,225,{acceptor_error,{error,accept_failed}}}}=
}
> To me this seems like it runs out of threads or sockets to handle the new=
 connection or somewhat like this.
> 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 message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira