Container not starting

[Zeebzog]

Hi,

My computer ran out of disk whilst rabbit was running (Ubuntu 20.04.02 LTS, x86_64, Docker 20.10.7 with runc 1.0.1)
I could not get rabbit to start even after clearing disk space (it was stuck on reindexing)
In the end I docker pruned my machine and ensured that rabbit image, container and volumes were removed
I then tried to bring up rabbit using the following docker-compose

services:
rabbitqueue:
image: rabbitmq:3-management
hostname: rabbit
ports:
- 15672:15672
- 5672:5672
container_name: messaging
volumes:
#- ~/.docker-conf/rabbitmq/data/:/var/lib/rabbitmq/
#- ~/.docker-conf/rabbitmq/log/:/var/log/rabbitmq
- ./.docker/rabbitmq/etc/:/etc/rabbitmq/
- ./.docker/rabbitmq/data/:/var/lib/rabbitmq/
- ./.docker/rabbitmq/logs/:/var/log/rabbitmq/

I have also tried it with the volumes being the ones #'d out.

No matter what I do I get an access denied error from rabbit in the log file. See log output below.
If I run this from docker command line with the simple:

docker run -d --hostname my-rabbit --name some-rabbit -p 15672:15672 rabbitmq:3-management

Then rabbit does start. Please help I cannot figure out how to get this to work, and so far it has been foolproof.

---

Log file out put.

BOOT FAILED

===========

failed to open log file at '/var/log/rabbitmq/rabbit@rabbit_upgrade.log', reason: permission denied

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> crasher:

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> initial call: application_master:init/4

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> pid: <0.221.0>

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> registered_name: []

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> exception exit: {{cannot_log_to_file,

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> "/var/log/rabbitmq/rabbit@rabbit_upgrade.log",

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> eacces},

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> {rabbit,start,[normal,[]]}}

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> in function application_master:init/4 (application_master.erl, line 142)

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> ancestors: [<0.220.0>]

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> message_queue_len: 1

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> messages: [{'EXIT',<0.222.0>,normal}]

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> links: [<0.220.0>,<0.44.0>]

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> dictionary: []

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> trap_exit: true

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> status: running

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> heap_size: 987

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> stack_size: 29

2021-08-01 23:06:18.775056+00:00 [erro] <0.221.0> reductions: 178

[wglambert]

Seems your mounted volumes might have some malformed data from that out of disk space incident. I'm not sure how you'd go about trying to repair that data, but if you use new volumes for those that you're bind-mounting then it should work fine:

- ./.docker/rabbitmq/etc/:/etc/rabbitmq/
- ./.docker/rabbitmq/data/:/var/lib/rabbitmq/
- ./.docker/rabbitmq/logs/:/var/log/rabbitmq/

You could also try asking a rabbitmq-specific resource or the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum