rabbitmq frequently fails to start due to permissions error

[Paul Bourke]

On bringing up a fresh rabbitmq instance (all-in-one or multinode), the container will go into the restarting state with:

$ docker logs rabbitmq
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied
mkdir: cannot create directory '/var/lib/rabbitmq/mnesia': Permission denied

At first I thought this was due to an incomplete bootstrap but it appears to happen on a clean startup also. On stopping all containers, rm'ing the data container and re running ansible it seems to start.

[Sam Yaple (s8m)]

Paul,

I am unable to reproduce this at all. Can you give more info on how to reproduce this? Im hesitant to chown everything each run due to different permissions that rabbitmq uses throughout. Let's solve this correctly.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Paul Bourke (<email address hidden>) on branch: master
Review: https://review.openstack.org/218890
Reason: Superseded by I6a00aaef38b4ab6a60dcfb5ed2f808513b9f8c84