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

Service doesn't come back after reboot because the default service directory is missing #55

Closed
Fitzsimmons opened this issue Apr 19, 2016 · 4 comments

Comments

@Fitzsimmons
Copy link

Fitzsimmons commented Apr 19, 2016

The default service directory is /var/run/vault, which is created by the cookbook - but on many systems, /var/run is mounted as tmpfs. This means that /var/run/vault is not present if the server reboots. The creation of /var/run/vault should be the responsibility of the init script, so that we don't run into this problem.

@johnbellone
Copy link
Contributor

What platform/version are you running?

@johnbellone johnbellone added the bug label May 3, 2016
@Fitzsimmons
Copy link
Author

I'm running Ubuntu 14.04. The issue is worse when using sysv, because it has nowhere to put the pidfile. When using upstart, a pidfile is not needed, but it will still attempt to chdir to /var/run/vault and crash when that directory doesn't exist; in this case, node['hashicorp-vault']['service']['directory'] can be overridden to anything persistent, like /etc/vault.

@legal90
Copy link
Contributor

legal90 commented May 6, 2016

For sysvinit it was fixed by #51

@lock
Copy link

lock bot commented May 19, 2019

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 May 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants