[rabbitmq-discuss] Durable queues not surviving broker restart

[Greg Rice]

Emile,

Nope, this is a super simple setup, with no tasks hanging around
deleting queues.

Here's rabbitmqctl report:

[{pid,12367},
 {running_applications,
     [{rabbitmq_management,"RabbitMQ Management Console","2.7.1"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","2.7.1"},
      {rabbit,"RabbitMQ","2.7.1"},
      {os_mon,"CPO  CXC 138 46","2.2.8"},
      {mnesia,"MNESIA  CXC 138 12","4.6"},
      {amqp_client,"RabbitMQ AMQP Client","2.7.1"},
      {sasl,"SASL  CXC 138 11","2.2"},
      {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.7.1"},
      {webmachine,"webmachine","1.7.0-rmq2.7.1-hg"},
      {mochiweb,"MochiMedia Web Server","1.3-rmq2.7.1-git"},
      {inets,"INETS  CXC 138 49","5.8"},
      {stdlib,"ERTS  CXC 138 10","1.18"},
      {kernel,"ERTS  CXC 138 10","2.15"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang R15B (erts-5.9) [source] [64-bit] [smp:4:4]
[async-threads:30] [hipe] [kernel-poll:true]\n"},
 {memory,
     [{total,104012472},
      {processes,12749519},
      {processes_used,12748683},
      {system,91262953},
      {atom,561761},
      {atom_used,544256},
      {binary,393528},
      {code,15189917},
      {ets,1107192}]},
 {vm_memory_high_watermark,0.39999999997623376},
 {vm_memory_limit,6732236390}]
...done.


There's nothing in the broker logs suggesting any errors. I'm going to
try a fresh install of RabbitMQ 2.8.1 on another server, but for now,
this is driving me a little bonkers.

Thanks,
Greg Rice


On Wed, Apr 18, 2012 at 3:28 AM, Emile Joubert <emile at rabbitmq.com> wrote:
> Hi Greg,
>
> On 18/04/12 00:20, Greg Rice wrote:
>> The durable *exchanges* I've created are still there, but the durable
>> *queues* are not.
>
> I'm unable to reproduce what you are seeing. I assume the queues are not
> being deleted by some background task? Is there anything of note in the
> broker logfiles? Can you provide the output of "rabbitmqctl report"?
>
>
> -Emile
>