[rabbitmq-discuss] Help pinpointing an error
Jaime Herazo B.
jherazo at beverlydata.com
Fri Aug 31 12:32:46 BST 2012
I just checked on the machine with "rabbitmqctl list_queues name
durable", and all show "false". Seems like someone here made a mistake
and forgot to make the queues durable, which was something we all had
assumed. Sorry for the alarm.
Is it possible to change the parameters of the queues and make them
durable without having to make a new one with a different name as
suggested in the Python tutorial?
Also the broker still crashed, so i'm posting the info asked anyway:
* rabbitmq-server 2.8.4-1 on Debian Stable (6.0.3)
* The service crashed, so i did a "service rabbitmq-server restart".
Naturally, since now we know that the queues are not durable as we
expected, all was lost.
* No HA, no clustering, 2 machines sending information to each other,
and a couple dozen clients consuming the messages put on the queues by
the one that crashed.
And for the logs, here's the pastebin:
The sasl log has far more information, but it was almost 1Mb of
information on that crash alone, so initially i'm just pasting this and
if needed i'll just add the other one.
On 31/08/12 12:13, Matthias Radestock wrote:
> On 31/08/12 10:56, Tim Watson wrote:
>> 1. how did your rabbit go down (crashed, accidentally restarted, etc)?
>> 2. exactly what steps did you take to restart it
>> 3. what kind of configuration do you have (is it clustered, any HA
>> queues, etc)
> The most important question of all is "What version of rabbit are you
> We fixed numerous bugs in the persister, but that was a long time ago
> and we have not seen any problem reports since.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss