Well, it might help if I point out the background of trouble and confusion.
I tried to configure rabbitmq automatically with puppet, using the officially recommended plugin, see https://forge.puppet.com/puppetlabs/rabbitmq https://github.com/voxpupuli/puppet-rabbitmq Two problems came together then: Problem 1: The plugin is not really compatible with ubuntu/debian, and was obviously written for some other distribution (red hat I guess), and enforces the ownership the plugin authors believed to be correct, i.e. changes /etc/rabbitmq and it's contents to be owned by root. Problem 2: The system I was testing this on has for security reasons an umask of 027 (instead of the usual 022) for root, and both puppet and this plugin forgot to set a proper umask. The result was that rabbitmq did not work anymore, since /etc/rabbitmq was owned by root and lost public read access. My problem then was: How to repair? I didn't find a hint about what it was supposed to be. Making it all readable did not help: Running rabbitmq-plugins as root renders rabbitmq dead probably because of the umask 027, file becomes undreadable. running rabbitmq-plugins as su -c "rabbitmq-plugins ..." -s /bin/sh rabbitmq doesn't work either if /etc/rabbitmq is owned by root, because rabbitmq- plugins wants to write a temporary /etc/rabbitmq/enabled_plugins.tmp So the central problem is that it is not obvious how things are supposed to be used and to work. Just having a umask different from 022 seems to break everything. Under what uid is rabbitmq-plugins supposed to be used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842408 Title: rabbitmq-server writes to /etc/rabbitmq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1842408/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
