-
Notifications
You must be signed in to change notification settings - Fork 65
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
Wait should be implemented in start/stop functions in RHEL6 init script #26
Comments
Reading https://consul.io/docs/commands/leave.html & https://consul.io/docs/agent/basics.html I see 2 different ways of shutting it down, but with the same outcome: The node leaves the cluster. The only disadvantage I see by using The other question is if we really wanna wait 60s by default or maybe just 10? I have no idea what a reasonable timeout might be, but 60s sounds quite long. Otherwise it looks fine to me, though I think the problem might be different or non-existent on EL7, as systemd might take care of it. |
@duritong: |
Souns fine, let's update the branch then. |
OK, done. I tested it and it seems to work fine. |
thanks a lot, I merged the PR, if you find any problems on EL7 let's open another ticket. |
OK, let's do so then |
Hi,
I've came across a problem that is likely related to startup/shutdown of
consul
in RHEL 6. Following are the details:Version:
Details:
8400
is fired up afterconsul
has been started bydaemon
function.consul
shuts down when killed bykillproc
.This leads to following errors:
8400
when fired right after the startup.Steps to reproduce:
Refusal of connection to agent port
8400
:The service fails to start upon restart action because some ports are still bound.
Unfortunately I haven't investigated this in RHEL 7, nor I've tried different consul versions yet, however I implemented wait in RHEL 6 init script in PR #25.
@duritong, @tomhillable: Would you please review and eventually merge?
Thanks.
The text was updated successfully, but these errors were encountered: