[ https://issues.apache.org/jira/browse/COUCHDB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548682#comment-13548682 ]
James Howe commented on COUCHDB-536: ------------------------------------ Think I've hit the same thing in 1.2.0. After making lots of view queries (triggering a reindex on every one on the server with a script) the server got into a state where it would abort a random selection of requests (made at a more leisurely rate), including a number of those used by Futon. Didn't have a chance to investigate socket states on the server unfortunately. The first error was this: [Wed, 09 Jan 2013 16:00:03 GMT] [error] [<0.1528.3109>] {error_report,<0.32.0>, {<0.1528.3109>,std_error, [{application,mochiweb}, "Accept failed error", "{error,enfile}"]}} Lots of these: [Wed, 09 Jan 2013 16:43:46 GMT] [error] [<0.617.3110>] {error_report,<0.32.0>, {<0.617.3110>,crash_report, [[{initial_call, {mochiweb_acceptor,init, ['Argument__1','Argument__2', 'Argument__3']}}, {pid,<0.617.3110>}, {registered_name,[]}, {error_info, {exit, {error,accept_failed}, [{mochiweb_acceptor,init,3}, {proc_lib,init_p_do_apply,3}]}}, {ancestors, [couch_httpd,couch_secondary_services, couch_server_sup,<0.33.0>]}, {messages,[]}, {links,[<0.124.0>]}, {dictionary,[]}, {trap_exit,false}, {status,running}, {heap_size,233}, {stack_size,24}, {reductions,209}], []]}} And then eventually lots of these as well: [Wed, 09 Jan 2013 16:43:46 GMT] [error] [<0.124.0>] {error_report,<0.32.0>, {<0.124.0>,std_error, {mochiweb_socket_server,254, {acceptor_error,{error,accept_failed}}}}} > 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, 1.1 > Environment: Ubuntu Linux 8.04 32bit and 64bit with Erlang R13B01 > or Ubuntu Linux 8.04 64bit with Erlang R14B02 > Reporter: Simon Eisenmann > Attachments: couchdb_database_open-week.png, > couchdb_httpd_request_methods-week.png, couchdb_httpd_response_codes-week.png > > > 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']}}, > {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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira