-
Notifications
You must be signed in to change notification settings - Fork 51
Puma not creating PID or Socket #25
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
Comments
Closed by #33 |
I'm not sure this is fixed by #33 @andreychernih? The pid and sockets base directory is /tmp is which is wiped on every restart of Ubuntu. So unless you provision every startup, puma is not going to be able to create the pid or sockets files. At least that's what I'm seeing. |
You're right, there's a problem with the |
Thanks @kraft001 - I'm happy to provide a PR. My thinking is we keep these files out /tmp and maybe something like /var/tmp/{project}/sockets/ etc.? |
Configuration at https://railsbox.io/boxes/0e2a475a6b52
Running this on an Ubuntu 12 host.
When the box boots, everything starts up but puma doesn't actually create the socket file or the pid file. The vagrant user has permissions on the tmp directory so I'm not sure what's going on. Nothing crazy showing up in syslog either.
Any ideas? I'm not sure where else to investigate at this point.
The text was updated successfully, but these errors were encountered: