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

Sensitivity to HUP during launch #125

Closed
jhmartin opened this issue Feb 7, 2015 · 3 comments · Fixed by #127
Closed

Sensitivity to HUP during launch #125

jhmartin opened this issue Feb 7, 2015 · 3 comments · Fixed by #127
Assignees
Milestone

Comments

@jhmartin
Copy link
Contributor

jhmartin commented Feb 7, 2015

The consul agent is sensitive to a HUP during its initialization process, such as when invoked via 'knife ssh'. Adding a nohup to the invocation or adding a sleep after it seems to clear up the issue.

I've opened an issue against consul itself as well.

@johnbellone
Copy link
Contributor

I'm not sure if this is a recipe bug or something due to underlying service. It sounds like we should wait to hear back from the project. Do you have a link to the issue?

@jhmartin
Copy link
Contributor Author

jhmartin commented Feb 9, 2015

Heard back from HashiCorp: hashicorp/consul#677 . They say the HUP is coming in before the signal handler is installed, and the init script should add a delay.

jhmartin pushed a commit to jhmartin/consul-cookbook that referenced this issue Feb 9, 2015
@johnbellone johnbellone added bug and removed question labels Feb 9, 2015
@johnbellone johnbellone added this to the Road to 1.0.0 milestone Feb 9, 2015
@johnbellone johnbellone self-assigned this Jun 16, 2015
jhmartin added a commit to jhmartin/consul-cookbook that referenced this issue Jul 13, 2015
… shutdown when invoked via knife ssh (or any short-lived pty), fixes sous-chefs#125.
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants