[rabbitmq-discuss] RabbitMQ dying

[Jerry Kuch]

I realize this might be more of a PITA than you have the stomach for, but
can you scare up debug symbols for that version of Erlang as well as
apt-get the source?  That might let you look at the core file that's
generated during the segfault (assuming you're getting one, are you?) and
see where specifically it's croaking...

It might also be worth running this problem and its history and particulars
by the erlang-bugs mailing list and see if any of the VM maintainers
recognize it...

http://erlang.org/mailman/listinfo/erlang-bugs

Best regards,
Jerry

On Sat, Feb 23, 2013 at 12:08 PM, Christian S. Perone <
christian.perone at gmail.com> wrote:

> I tried to upgrade Erlang but without success, the same segfault appeared
> on the syslog, so I purged everything (config files, log files, etc.)
> related to erlang and Rabbitmq and installed again the 2.7.1 version as
> well the default erlang ubuntu version and the message is still appearing
> after some time of work:
>
> [19955.696882] beam.smp[4356]: segfault at 8 ip 00000000004d8c50 sp
> 00007ff57f8e67a0 error 4 in beam.smp[400000+1af000]
>
> Is there any way to debug this ?
>
> Thanks !
>
>
> On Fri, Feb 22, 2013 at 10:04 PM, Jerry Kuch <jerryk at rbcon.com> wrote:
>
>> On Fri, Feb 22, 2013 at 5:00 PM, Christian S. Perone <
>> christian.perone at gmail.com> wrote:
>>
>>> Hello Jerry, great thanks for the quick reply. I'll try to update the
>>> Erlang VM to a newer one, the directory '/etc/rabbitmq/rabbitmq.conf.d'
>>> didn't exist (I think it was removed on the upgrade process to the 3.0.2
>>> version), but this message is only showing on the version 3.0.2, when I was
>>> using the 2.7.1 the conf.d was present and the same thing happened, so I
>>> think that this couldn't be the cause. I'll upgrade the Erlang and stress
>>> it again to check how it works.
>>>
>>
>> Let us know how you make out.  It sounds like you're in a position where
>> it's safe to scrub your Ubuntu boxes of both Erlang and Rabbit, and build
>> up from fresh...
>>
>> Also, be mindful that there are config file differences between such
>> disparate versions, so leftovers from an old Rabbit may antagonize a new
>> one.  Still, one would expect something less horrendous than a mute
>> segmentation fault....
>>
>> Jerry
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
>
>
> --
> Blog <http://pyevolve.sourceforge.net/wordpress/> | Github<https://github.com/perone>
> | Twitter <https://twitter.com/tarantulae>
> "Forgive, O Lord, my little jokes on Thee, and I'll forgive Thy great big
> joke on me."
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130223/7f38b958/attachment.htm>