[rabbitmq-discuss] RabbitMQ dying

Sat Feb 23 01:00:34 GMT 2013

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.

On Fri, Feb 22, 2013 at 9:55 PM, Jerry Kuch <jerryk at rbcon.com> wrote:

> Hi, Christian:
>
> Hello, I'm facing some problems with different versions of RabbitMQ (2.7.1
>> and 3.0.2), and I couldn't
>> find any trace of problem in the logs (perhaps I'm looking the wrong log
>> file), anyway, the rabbitmq is dying after running well for some time, I'm
>> using only two queues and the messages are working on a rate of 132
>> msgs/sec, but after 2 or 3 hours the rabbitmq simple dies and the only log
>> I can see is from the kernel log (dmesg), with RabbitMQ 3.0.2:
>>
>
> That's pretty tiny load... one wouldn't expect a Rabbit to stress much
> under that.
>
>
>> [38178.105567] beam.smp[1514] general protection ip:4d8b48
>> sp:7f979f41e7a0 error:0 in beam.smp[400000+1af000]
>>
>> ... which looks pretty bad. The same message appeared with version 2.7.1
>> and all logs in /var/log/rabbitmq didn't showed anything that could be an
>> error, just info about connections, etc. Also, after I updated it to the
>> version 3.0.2, the only log that RabbitMQ touched was
>> /var/log/rabbitmq/startup_err, which contained the messages:
>>
>
> Egads...  that's your Erlang VM crashing hard.  Erlang R14B04 is a little
> bit old, but was a pretty solid release.  You might try upgrading your
> Erlang release to one of the newer R15s, although bits of this make me
> wonder if something worse is afoot on this machine.
>
>
>> ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
>> Segmentation fault (core dumped)
>>
>
> Does the rabbitmq.conf.d directory and any of its contents exist?  What's
> the story on permissions?
>
>
>> Besides the conf error message the server worked for nearly 2 hours and
>> then died, but now it is showing the segfault message that wasn't show on
>> the 2.7.1 version.
>>
>> I'm using Ubuntu server 12.04.2 (LTS) with kernel 3.2.0 (x86_64) and
>> Erlang v.5.8.5.
>>
>> Does anyone already faced this problem or have any clue about what could
>> be causing this ?
>>
>
> I'd:
>
> 1. Upgrade Erlang
> 2. Possibly reinstall Rabbit
>
> Segmentation faults of the Erlang VM are relatively rare, and it's not
> easy to cause one from Rabbit's own code...  Usually if one sees one
> something more wretched is afoot on the system....
>
> Best regards,
> 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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130222/aa6d2cd1/attachment.htm>