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

Force-kill on /etc/init.d/consul stop. Fixes #128 #129

Merged
merged 1 commit into from Feb 26, 2015

Conversation

Projects
None yet
4 participants
@jhmartin
Copy link
Contributor

jhmartin commented Feb 9, 2015

In some conditions (I'm seeing it on a new node bootstrap when chef wants to start and then restart consul), consul does not come down in time for the init script. This change kill -9's the process if it hasn't come down within the 10s window.

@coveralls

This comment has been minimized.

Copy link

coveralls commented Feb 9, 2015

Coverage Status

Coverage remained the same at 100.0% when pulling 2ea1ae2 on jhmartin:128-kill_on_shutdown into 57b4105 on johnbellone:master.

johnbellone added a commit that referenced this pull request Feb 26, 2015

Merge pull request #129 from jhmartin/128-kill_on_shutdown
Force-kill on /etc/init.d/consul stop. Fixes #128

@johnbellone johnbellone merged commit 60e3072 into sous-chefs:master Feb 26, 2015

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
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.