You are right, there was about 30 of these:
tcp 0 0 localhost.localdo:60607 localhost.localdom:5984
TIME_WAIT -
I'll let the CouchRest team know.
-
Tommy
On Jul 24, 2009, at 3:58 PM, Paul Davis wrote:
> Tommy,
>
> When you get into a connection refused error, try doing:
>
> $ netstat -tap tcp
>
> To see if its a crap load of open sockets. If so, my money is on your
> client library not properly closing connections.
>
> Paul Davis
>
> On Fri, Jul 24, 2009 at 6:51 PM, Tommy
> Chheng<tommy.chheng@gmail.com> wrote:
>> If i have couchdb running for a period of time, it returns back a
>> "Connection refused" when i simply curl it.
>>
>> I did a ps and found the beam process is still running. If I
>> restart it,
>> it'll work again.. but only for a period of time before it gives
>> back a
>> connection refused.
>>
>> I gisted some error output in more detail here:
>> http://gist.github.com/154594
>>
>> I'm running on a ubuntu 8.10 EC2 instance.
>>
>> Any ideas why it reverts to a "connection refused' error and how
>> can i fix
>> it?
>>
>> Thanks,
>> tommy
|