You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On CIS benchmarked servers (and possibly other benchmarks), the umask settings are pretty strict with all new files getting created with permissions of 600. Since plugins get downloaded as root and end up with these permissions, the rabbitmq service cannot read the plugin and fails to start.
Possible fixes are to add the following to the remote_file section of community_plugins.rb to set ownership to rabbitmq, preserving permissions:
owner 'rabbitmq'
group 'rabbitmq'
or change the permissions with the following (edit: thinking about it more, I think this would be consistent with other plugins and probably preferable):
mode 0644
The text was updated successfully, but these errors were encountered:
On CIS benchmarked servers (and possibly other benchmarks), the umask settings are pretty strict with all new files getting created with permissions of 600. Since plugins get downloaded as root and end up with these permissions, the rabbitmq service cannot read the plugin and fails to start.
Possible fixes are to add the following to the remote_file section of community_plugins.rb to set ownership to rabbitmq, preserving permissions:
or change the permissions with the following (edit: thinking about it more, I think this would be consistent with other plugins and probably preferable):
The text was updated successfully, but these errors were encountered: