8000 Vagrant reboot deletes puma pids and sockets folder from /tmp directory · Issue #55 · a-chernykh/railsbox · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Vagrant reboot deletes puma pids and sockets folder from /tmp directory #55

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.

Sign up for GitHub

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

Jump to bottom
Open
ghost opened this issue Jul 13, 2016 · 1 comment
Open

Vagrant reboot deletes puma pids and sockets folder from /tmp directory #55

ghost opened this issue Jul 13, 2016 · 1 comment

Comments

@ghost
Copy link
ghost commented Jul 13, 2016

While using the setup works perfectly fine on first provisioning, as soon as I do vagrant halt and start the machine again by doing vagrant up, I can't seem to get puma working. I've looked into the log files and the issue is that the pids and sockets directory from /tmp/project-name folder are missing. Actually, the whole /tmp/project-name folder is missing on subsequent boots.

Is this something that I can solve on my own?
@noefroidevaux
Copy link
noefroidevaux commented Jul 20, 2016 •
edited
Loading

@aniljaiswal I have the same problem. I seems related to #25 and as @arifb proposes, I use

app_temp_path: "/var/tmp{{ app_path }}"

instead of

app_temp_path: "/tmp{{ app_path }}"

in railsbox/ansible/roles/nginx/templates/nginx.conf.j2 (you need a vagrant provision after that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@noefroidevaux
0