[rabbitmq-discuss] |Spam| |Spam| broker going down, how to troubleshoot?

[Shane Witbeck]

I installed rabbit via the generic unix tar because we don't have access to
the normal OS package manager (one of the joys of being in a strict
corporate env).

I got "rabbitmq-server start -detached" from the documentation (
http://www.rabbitmq.com/install.html#running-generic-unix)

I haven't found anything noteworthy in the system logs yet.


On Fri, Nov 5, 2010 at 3:28 PM, Matthias Radestock <matthias at rabbitmq.com>wrote:

> Shane,
>
>
> Shane Witbeck wrote:
>
>> The rabbit-sasl.log is 5MB but the last entry was from Oct 28.
>>
>
> Right. So clearly something went wrong before that date since the sasl log
> should normally be empty.
>
>
>  Yesterday the broker went down at ~2pm, so not the same time every day.
>> The rabbit started via "rabbitmq-server start -detached"
>>
>
> That's a strange way to start rabbit. Where did you get that from? How did
> you install rabbit? We generally recommend that people install rabbit from
> the package for their o/s and start/stop it using the appropriate system
> commands. On SuSe that should be s.t. like
>
> /sbin/service rabbitmq-server start
>
> (according to http://www.rabbitmq.com/install.html#rpm - I am not a SuSe
> expert)
>
> Though that doesn't quite explain why rabbit would die. Is there anything
> noteworthy in the system logs? Perhaps rabbit is being nuked by the infamous
> OOM Killer.
>
>
> Matthias.
> PS: please keep rabbitmq-discuss cc'ed.
>



-- 
-Shane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101105/b2d3f1d6/attachment.htm>