[rabbitmq-discuss] Debugging rabbitmq crash

[Matt Calder]

The second run stopped in the same manner. I was running rabbitmq
1.7.2 and erlang 13B03. I had started before I got Matthias's
suggestion to upgrade rabbit.  This time I captured the stack traces
of the two processes when they stopped.

The server process:

...
    self._mq_channel.basic_publish(amqp.Message(body), exchange =
self._mq_exchange, routing_key = "reply")
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/channel.py",
line 2223, in basic_publish
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/abstract_channel.py",
line 70, in _send_method
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/method_framing.py",
line 240, in write_method
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/transport.py",
line 125, in write_frame
  File "<string>", line 1, in sendall
socket.error: [Errno 32] Broken pipe

The client process:
...
    self.clientProcess._mq_channel.wait()
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/abstract_channel.py",
line 89, in wait
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/connection.py",
line 198, in _wait_method
  File "build/bdist.linux-i686/egg/amqplib/client_0_8/method_framing.py",
line 215, in read_method
IOError: Socket closed

I will rerun with rabbit 1.8.0.

Matt



2010/6/23 Nicolás César <nico at nicocesar.com>:
> Simon told me once, It was helpful for me that time.:
> -------------------------------------------
> Well, there's erlang:memory/0.
>
> If you're using the Debian packages, type:
>
> $ sudo -u rabbitmq -H erl -remsh rabbit@`hostname` -sname foo
>
> to establish a connection to the RabbitMQ Erlang process then at the Erlang
> prompt:
>
> memory().
>
> to give some high level statistics about what's using memory.
> ---------------------------------------
>
> My 2 cents.
>
> 2010/6/23 Matt Calder <mvcalder at gmail.com>
>>
>> Matthias,
>>
>>
>> On Wed, Jun 23, 2010 at 2:52 PM, Matthias Radestock
>> <matthias at rabbitmq.com> wrote:
>> > I strongly recommend you upgrade to rabbit 1.8.0 as well.
>> >
>>
>> Will do.
>>
>> > That's the producer and consumer, right? So actually rabbit might still
>> > be
>> > running happily? Did you try restarting the clients?
>> >
>>
>> I believe it was still running because I recall seeing a message that
>> it was being stopped during the upgrade of erlang (I know, flimsy
>> evidence at best). I will be more diligent if I run into problems
>> again.
>>
>> Matt
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>