[rabbitmq-discuss] |Spam| |Spam| broker going down, how to troubleshoot?
shane at digitalsanctum.com
Fri Nov 5 20:10:19 GMT 2010
Here's the env vars we set prior to starting the broker:
Not running as root but using a shared login (I know it's bad but out of my
The only thing I've noticed about the mgmt plugin is that it has a nasty
memory leak in the IE browser (if left open over night, it accumulates over
1GB of memory). This probably has nothing to do with the broker going down
but thought I'd mention it since you asked :)
Since it's happened twice now in as many days I will be keeping a closer eye
on it and report back with whatever I find.
On Fri, Nov 5, 2010 at 3:51 PM, Matthias Radestock <matthias at rabbitmq.com>wrote:
> Shane Witbeck wrote:
>> 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).
> ok. Did you have to set any env vars / modify the startup scripts in any
> way? And are you running rabbit as root, a dedicated 'rabbitmq' user, or
> I got "rabbitmq-server start -detached" from the documentation (
> There is no "start" in there. Shouldn't cause any harm though.
> Is there an erl_crash.dump in the directory from which you started rabbit?
> I haven't found anything noteworthy in the system logs yet.
> I see your rabbit is running the management plugin. Have you been keeping
> an eye on it through that? And did anything odd crop up - high memory or fd
> use, for example - just before the death?
> It is quite rare for rabbit to die, and very unusual indeed for it to do so
> without a trace. For that to happen the most likely cause of death is that
> something/body is killing it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss