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 using "overseer," I assign state.Listener to ss.Ln and then call ss.Engine.RunListener(ss.Ln) to start the service.
Problem: Currently, graceful restart is working fine. However, when I send a TERM signal to the program for a normal shutdown, it gets blocked and doesn't terminate.
---
How can I resolve the above issues?
The text was updated successfully, but these errors were encountered:
Also, I did an experiment and without any wrapping, with the default gin framework, when I call
kill -SIGUSR2 ${master_pid}
I get an error as follows
accept tcp [::]:5001: use of closed network connection
Is this error normal and do I need to deal with it?
======
Does this error report have the same effect as the http.ErrServerClosed ?
// ErrServerClosed is returned by the Server's Serve, ServeTLS, ListenAndServe,
// and ListenAndServeTLS methods after a call to Shutdown or Close.
var ErrServerClosed = errors.New("http: Server closed")
Context: I am using the Gin framework and have made some customizations to the framework. Here are some of the encapsulated structures.
After completing all the initialization, the service is started using the following code:
When using "overseer," I assign state.Listener to ss.Ln and then call ss.Engine.RunListener(ss.Ln) to start the service.
Problem: Currently, graceful restart is working fine. However, when I send a TERM signal to the program for a normal shutdown, it gets blocked and doesn't terminate.
---How can I resolve the above issues?
The text was updated successfully, but these errors were encountered: