Well that was fast as I had a quick back and forth on that bug I linked
above. Feel free to add any more details if you want.
The heart of the issue comes down to the fact that the rabbitmq-server
runs as a non-root user who will not have permissions to create a
directory in /var/log. The result is not being able to create the log
directory and failure to start. To be fair, rabbitmq-server does try to
create the directory as noted in the Github issue above.
One solution to avoid this, the rabbitmq-server packaging would need to
be changed to run the service as a root user or log to somewhere it
would have permissions to going forward. I do not believe we would want
to change this, so I am going to mark this bug as "wont fix". If you
have any further details, questions, or notes feel free to add them here
or to the Github bug above.
** Changed in: rabbitmq-server (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: rabbitmq-server (Ubuntu)
Assignee: Joshua Powers (powersj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585043
Title:
rabbitmq-server fails to start when /var/log/rabbitmq does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/rabbitmq/+bug/1585043/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
