[rabbitmq-discuss] Erlang has closed?

[tyler at echonest.com]

On Tue, 18 May 2010, Matthias Radestock wrote:

> tyler at echonest.com wrote:
>> I'm running the latest stable version of rabbitmq (1.7.2) and the latest 
>> erlang (R13B04) on a ubuntu server machine (2.6.31-14-server x86_64).
>> 
>> I'm having a problem where if I load rabbitmq heavily, it will die with the 
>> console message: "Erlang has closed." I still see beam.smp running, but I 
>> can't connect to rabbit at all, and there is nothing in rabbit.log or 
>> rabbit-sasl.log.
>
> Is there really *nothing* in these logs? If there is, please upload the 
> contents somewhere we can see it.
>
> Also, what client library are you using?
>
> Regards,
>
> Matthias.
>


rabbit-sasl.log is completely empty. rabbit.log has a few of the 
following:

=ERROR REPORT==== 18-May-2010::14:22:52 ===
exception on TCP connection <0.2078.0> from 192.168.1.138:63015
{handshake_timeout,handshake}

=INFO REPORT==== 18-May-2010::14:22:53 ===
closing TCP connection <0.2078.0> from 192.168.1.138:63015

I've posted the last 1000 lines here: http://pastebin.com/bPChQrgN

For a client library, I'm using py-amqplib (.5).


Thanks,

Tyler