[rabbitmq-discuss] Rabbitmq 2.5.1 Bad argument crash

Chris Larsen clarsen at euphoriaaudio.com
Fri Sep 28 15:41:34 BST 2012


Hey everyone, we had a problem today with 2.5.1 where the broker kept
crashing on us. We think it's just a bad message but wanted to verify that.
The other nodes in our cluster don't seem to be running into any issues. I
found something similar in the post about Stomp packets at
http://groups.google.com/group/rabbitmq-discuss/tree/browse_frm/month/2011-0
2/ce709a4aacac8569?rnum=31
<http://groups.google.com/group/rabbitmq-discuss/tree/browse_frm/month/2011-
02/ce709a4aacac8569?rnum=31&_done=%2Fgroup%2Frabbitmq-discuss%2Fbrowse_frm%2
Fmonth%2F2011-02%3F>
&_done=%2Fgroup%2Frabbitmq-discuss%2Fbrowse_frm%2Fmonth%2F2011-02%3F but
we're not pushing anything through Stomp that we're aware of (though the
plugin is enabled on the system). What do ya'll think? Thanks!

 

Ubuntu 2.6.38-10-server #46~lucid1-Ubuntu

Erlang: 1:13.b.3-dfsg-2ubuntu2.1

 

=CRASH REPORT==== 28-Sep-2012::13:39:19 ===

  crasher:

    initial call: rabbit_writer:mainloop/2

    pid: <0.1778.2>

    registered_name: []

    exception error: bad argument

      in function  size/1

         called as size(2)

      in call from rabbit_binary_generator:encode_property/2

      in call from rabbit_binary_generator:encode_properties/6

      in call from rabbit_binary_generator:ensure_content_encoded/2

      in call from rabbit_binary_generator:build_simple_content_frames/4

      in call from rabbit_writer:assemble_frames/5

      in call from rabbit_writer:internal_send_command_async/3

      in call from rabbit_writer:handle_message/2

    ancestors: [<0.1777.2>,<0.1773.2>,<0.1771.2>,rabbit_tcp_client_sup,

                  rabbit_sup,<0.127.0>]

    messages: [{inet_reply,#Port<0.6160>,ok}]

    links: [<0.1777.2>]

    dictionary: []

    trap_exit: false

    status: running

    heap_size: 610

    stack_size: 24

    reductions: 210

  neighbours:

 

=SUPERVISOR REPORT==== 28-Sep-2012::13:39:19 ===

     Supervisor: {<0.1777.2>,rabbit_channel_sup}

     Context:    child_terminated

     Reason:     badarg

     Offender:   [{pid,<0.1778.2>},

                  {name,writer},

                  {mfa,{rabbit_writer,start_link,

                                      [#Port<0.6160>,1,131072,

 
rabbit_framing_amqp_0_9_1,<0.1774.2>]}},

                  {restart_type,intrinsic},

                  {shutdown,4294967295},

                  {child_type,worker}]

 

 

=SUPERVISOR REPORT==== 28-Sep-2012::13:39:19 ===

     Supervisor: {<0.1777.2>,rabbit_channel_sup}

     Context:    shutdown

     Reason:     reached_max_restart_intensity

     Offender:   [{pid,<0.1778.2>},

                  {name,writer},

                  {mfa,{rabbit_writer,start_link,

                                      [#Port<0.6160>,1,131072,

 
rabbit_framing_amqp_0_9_1,<0.1774.2>]}},

                  {restart_type,intrinsic},

                  {shutdown,4294967295},

                  {child_type,worker}]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120928/3f85bb5d/attachment.htm>


More information about the rabbitmq-discuss mailing list