Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of randall.leeds@gmail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=ZrVLnFRW7SHJAz+7VRMtA+XJDB6FBrA4BOY3tLEczxUR+aV/ISxIzf97+A0XWf9mZl
         JbuX/j5R13KLvf9vYuhA28frYXLDUXjetPIO9WLBuxLEY9thUr2ZuUnX2oD1EGfS1gcu
         IFS1L0Jz/LP1LOATJqfCLykee5V5TSfqagr/E=
MIME-Version: 1.0
In-Reply-To: <AANLkTikjSJ1e9t9Fu=H1QWwNAUp6YyjK17J5gs00Fdm-@mail.gmail.com>
References: <AANLkTi=e2YwHA8BB-9M2zDq2G8uBFJS08tTkhRDYh6E=@mail.gmail.com>
	<AANLkTind7WVvhBdAbjrzNxs0_+kJGXg5NQJyn4ZjmasN@mail.gmail.com>
	<AANLkTikjSJ1e9t9Fu=H1QWwNAUp6YyjK17J5gs00Fdm-@mail.gmail.com>
Date: Wed, 1 Dec 2010 13:47:36 -0500
Message-ID: <AANLkTi=ZeZeC-JULZ53=eXOKDFm6n3DdgTHJS_ZxybvC@mail.gmail.com>
Subject: Re: Too many open files
From: Randall Leeds <randall.leeds@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Also check the value of the ERL_MAX_PORTS environment variable, which
is the erlang runtime's limit on how many files/sockets can be opened.

See also: http://wiki.apache.org/couchdb/Performance#Resource_Limits

On Wed, Dec 1, 2010 at 13:29, Robert Newson <robert.newson@gmail.com> wrote=
:
> ignore the '-f' bit.
>
> On Wed, Dec 1, 2010 at 6:29 PM, Robert Newson <robert.newson@gmail.com> w=
rote:
>> look in /proc/<pid/limits to see if your tweak to limits.conf works. I
>> doubt it does.
>>
>> The way I increase fd limits from the miserly Linux default of 1024 is
>> with this run script, where couchdb is launched by runit;
>>
>> #!/bin/bash
>> exec 2>&1
>> export HOME=3D<dir>
>> ulimit -n 10000
>> exec chpst -u <user> couchdb -f
>>
>> B.
>>
>>
>>
>>
>> On Wed, Dec 1, 2010 at 6:21 PM, Jonathan Johnson <jon@core-apps.com> wro=
te:
>>> Our couch setup has around 100 databases with a significant number of
>>> views in each database. Every once in a while, couch takes a dive. I
>>> happened to be around this time, and saw this in the logs:
>>>
>>>
>>> [Wed, 01 Dec 2010 18:09:19 GMT] [error] [<0.102.0>] {error_report,<0.31=
.0>,
>>> =C2=A0 =C2=A0{<0.102.0>,std_error,
>>> =C2=A0 =C2=A0 {mochiweb_socket_server,225,{acceptor_error,{error,accept=
_failed}}}}}
>>>
>>> [Wed, 01 Dec 2010 18:09:19 GMT] [error] [<0.10711.1125>] {error_report,=
<0.31.0>,
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0{<0.10711.1125>,std_err=
or,
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [{application,mochiweb=
},
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"Accept failed e=
rror","{error,emfile}"]}}
>>>
>>> [Wed, 01 Dec 2010 18:09:19 GMT] [error] [<0.10711.1125>] {error_report,=
<0.31.0>,
>>> =C2=A0 =C2=A0{<0.10711.1125>,crash_report,
>>> =C2=A0 =C2=A0 [[{initial_call,{mochiweb_socket_server,acceptor_loop,['A=
rgument__1']}},
>>> =C2=A0 =C2=A0 =C2=A0 {pid,<0.10711.1125>},
>>> =C2=A0 =C2=A0 =C2=A0 {registered_name,[]},
>>> =C2=A0 =C2=A0 =C2=A0 {error_info,
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 {exit,
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 {error,accept_failed},
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [{mochiweb_socket_serv=
er,acceptor_loop,1},
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0{proc_lib,init_p=
_do_apply,3}]}},
>>> =C2=A0 =C2=A0 =C2=A0 {ancestors,
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [couch_httpd,couch_secondary_service=
s,couch_server_sup,<0.32.0>]},
>>> =C2=A0 =C2=A0 =C2=A0 {messages,[]},
>>> =C2=A0 =C2=A0 =C2=A0 {links,[<0.102.0>]},
>>> =C2=A0 =C2=A0 =C2=A0 {dictionary,[]},
>>> =C2=A0 =C2=A0 =C2=A0 {trap_exit,false},
>>> =C2=A0 =C2=A0 =C2=A0 {status,running},
>>> =C2=A0 =C2=A0 =C2=A0 {heap_size,233},
>>> =C2=A0 =C2=A0 =C2=A0 {stack_size,24},
>>> =C2=A0 =C2=A0 =C2=A0 {reductions,202}],
>>> =C2=A0 =C2=A0 =C2=A0[]]}}
>>>
>>> [Wed, 01 Dec 2010 18:09:19 GMT] [error] [<0.102.0>] {error_report,<0.31=
.0>,
>>> =C2=A0 =C2=A0{<0.102.0>,std_error,
>>> =C2=A0 =C2=A0 {mochiweb_socket_server,225,{acceptor_error,{error,accept=
_failed}}}}}
>>>
>>> I had run into an open files limit before, and had adjusted a few
>>> settings. Here are some of the config values I think are relevant:
>>>
>>> max_dbs_open =3D 100
>>> max_connections =3D 2048
>>>
>>> From /etc/security/limits.conf
>>> couchdb =C2=A0 =C2=A0 =C2=A0 =C2=A0 hard =C2=A0 =C2=A0nofile =C2=A04096
>>> couchdb =C2=A0 =C2=A0 =C2=A0 =C2=A0 soft =C2=A0 =C2=A0nofile =C2=A04096
>>>
>>> The installed version is 1.0.1.
>>>
>>> I'm not sure how to debug this issue further. It only happens after
>>> several days of usage, and once it happens, I can't even ask for the
>>> stats page to see what the current numbers are :)
>>>
>>> Thanks in advance for any help!
>>> -Jon
>>>
>>
>