On Fri, Feb 22, 2013 at 5:00 PM, Christian S. Perone <span dir="ltr"><<a href="mailto:christian.perone@gmail.com" target="_blank">christian.perone@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">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.</div>
</div></blockquote><div><br></div><div>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...</div><div>
<br></div><div>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....</div>
<div><br></div><div>Jerry</div><div><br></div></div>