-
Notifications
You must be signed in to change notification settings - Fork 329
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
lorawan-server doesn't properly shutdown in docker container #843
Comments
The lorawan-server script doesn't forward TERM signal to underlying process. Normally the underlying process must be started from the starting script with "exec", but only if it is a binary executable (which "erl" is not; from tests carried out it works, but two "zombie" processes remain active). In this modification, a trap is activated that forwards the term signal. In solution to gotthardp#843 issue
Hi @lcse66. |
Hi Hugo (@hugosantosbessa) |
Hi everyone.
The server running in the docker environment does not respond correctly to the shutdown request, but it is killed at the end of the timeout. A longer timeout produces no advantages.
This behavior also causes side problems, including permanent errors in connectors when the connected service (e.g. mqtt broker) is running on the same server, and the server is being stopped. See also #771 #772.
The issue can be verified by stopping the Lorawan container and measuring the shutdown time, which will be approximately 10 seconds (corresponding to the timeout for stopping the containers).
I know that this project is no longer being maintained for now, and I hope that it will be maintained again in the future. Best regards to @gotthardp for the excellent project.
The text was updated successfully, but these errors were encountered: