Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternate restarts fail on CentOS #264

dparne opened this issue May 5, 2015 · 0 comments


None yet
2 participants
Copy link

commented May 5, 2015

I noticed an issue with SELinux enforced CentOS.

Since the "rabbitmq.upstart.conf.erb" template has the PID_FILE hardcoded to "/var/run/rabbitmq/pid". The startup script "/etc/init.d/rabbitmq-server" is not able to create the directory "/var/run/rabbitmq" and I am getting an error when I run "service rabbitmq-server restart" every other time. It turned out to be that it could not find which process to kill.

This seems to be happening because of the security context of the "/var/run" folder restricting the startup script to be able to create that folder.

Ideally it would be nice if that value where we wanna store the PID_FILE is an attribute.

@jjasghar jjasghar closed this Feb 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.