-
Notifications
You must be signed in to change notification settings - Fork 660
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
Server fails to start if there is a .pid file left over #658
Comments
Yes; it is expected that you run |
This is for the container use case. It's not possible to do that. Could we make If there is a server running already, the second one will fail to start due to port conflicts. |
This should be fixed in |
I'm still seeing this when using After the After stopping the nodes with
|
The code to check if the Blockstack version in question is running will This behavior may be a consequence of running Blockstack in Docker. Within the Docker container, it could be the case that Blockstack always runs as PID 1. If this is the case, then checking the PID file wouldn't tell us anything, since the PID is the same across invocations. Can you confirm if this is the case? |
The process that is being run with the |
So, the PID file always has |
Yup! |
This is possibly fixed in |
Merged to |
I'm running into this when running in docker. If I stop the container and then restart it sometimes the
blockstack-server.pid
file was not cleaned up. The reason I run into this on docker is because the data that needs to be persisted is in the same directory as the.pid
file. Moving it out of the$HOME/.blockstack-server
directory would fix this issue.The text was updated successfully, but these errors were encountered: