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

docker stop times out and kill rabbitmq #10

Open
xeor opened this issue Dec 12, 2014 · 5 comments
Open

docker stop times out and kill rabbitmq #10

xeor opened this issue Dec 12, 2014 · 5 comments

Comments

@xeor
Copy link

xeor commented Dec 12, 2014

In rabbitmq-start, we starts rabbitmq-server with exec, which is correct if the command we starts handles SIGTERM. rabbitmq-server is another shell script, that does some logic and then starts rabbitmq itself. However, this time, it is not using exec, hence, Dockers signals wont ever reach the rabbitmq server itself.

xeor added a commit to xeor/rabbitmq that referenced this issue Dec 12, 2014
@jleskovar
Copy link

LGTM. Might be an idea to trap both SIGTERM and SIGINT, so you can ^c from within the container

@xeor
Copy link
Author

xeor commented Jan 6, 2015

@jleskovar updated pull-request so we will trap SIGINT to.

@pikeas
Copy link

pikeas commented Jan 8, 2015

Might be better to add the rabbitmq-start logic to the rabbitmq-server script directly?

@pikeas
Copy link

pikeas commented Jan 9, 2015

Just opened an issue upstream with RabbitMQ at rabbitmq/rabbitmq-server#47.

@pikeas
Copy link

pikeas commented Jan 20, 2015

Fix will be in the next RabbitMQ release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants