Hi, Christian:<br><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, I'm facing some problems with different versions of RabbitMQ (2.7.1 and 3.0.2), and I couldn't�</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">
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:</div>
</div></blockquote><div><br></div><div>That's pretty tiny load... one wouldn't expect a Rabbit to stress much under that.</div><div>�</div><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"></div><div class="gmail_default"><font face="tahoma, sans-serif">[38178.105567] beam.smp[1514] general protection ip:4d8b48 sp:7f979f41e7a0 error:0 in beam.smp[400000+1af000]</font><br>
</div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif">... 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:</font></div>
</div></blockquote><div><br></div><div>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.</div>
<div>�</div><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">ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory</div><div class="gmail_default">
<div class="gmail_default"><font face="tahoma, sans-serif">Segmentation fault (core dumped)</font></div></div></div></blockquote><div><br></div><div>Does the rabbitmq.conf.d directory and any of its contents exist? �What's the story on permissions?</div>
<div>�</div><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"><div style="font-family:tahoma,sans-serif;font-size:small">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.</div>
<div style="font-family:tahoma,sans-serif;font-size:small">
<br></div><div style="font-family:tahoma,sans-serif;font-size:small">I'm using Ubuntu server 12.04.2 (LTS) with kernel 3.2.0 (x86_64) and Erlang v.5.8.5.</div><div style="font-family:tahoma,sans-serif;font-size:small">
<br></div><div style="font-family:tahoma,sans-serif;font-size:small">Does anyone already faced this problem or have any clue about what could be causing this ?</div></div></div></blockquote><div><br></div><div>I'd:</div>
<div><br></div><div>1. Upgrade Erlang</div><div>2. Possibly reinstall Rabbit</div><div><br></div><div>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....</div>
<div><br></div><div>Best regards,</div><div>Jerry</div><div><br></div></div>