You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the app starts, sometimes the last process has not remove its server.pid file. This causes startup to fail. This is an issue in production because it requires manual intervention if the app or server restarts for any reason.
Reproduce:
Start rails app with docker-compose.
Force-close app with ctl-c
Restart app with docker-compose
See error message in console/logs: app_1 | A server is already running. Check /app/tmp/pids/server.pid. app_1 | Exiting ghgvc-1_app_1 exited with code 1
The text was updated successfully, but these errors were encountered:
I think I can add a command to the docker-compose file that clears this each time it starts. It's not a huge problem, but I figured I should log an issue for it. I will try to include this in the next PR.
When the app starts, sometimes the last process has not remove its server.pid file. This causes startup to fail. This is an issue in production because it requires manual intervention if the app or server restarts for any reason.
Reproduce:
app_1 | A server is already running. Check /app/tmp/pids/server.pid. app_1 | Exiting ghgvc-1_app_1 exited with code 1
The text was updated successfully, but these errors were encountered: