Open howcrazy opened 10 months ago
The socket should instead be cleaned up at shutdown.
It creates the sock file but does not delete it after Ctrl + C or stop by supervisord. defer os.Remove(file)
not executed.
Maybe I should handle this situation manually?
+1
The socket should instead be cleaned up at shutdown.
It creates the sock file but does not delete it after Ctrl + C or stop by supervisord.
defer os.Remove(file)
not executed.Maybe I should handle this situation manually?
I don't think you should have to, if the service is not running anymore, the socket should disappear imo.
The socket should instead be cleaned up at shutdown.
It creates the sock file but does not delete it after Ctrl + C or stop by supervisord.
defer os.Remove(file)
not executed. Maybe I should handle this situation manually?I don't think you should have to, if the service is not running anymore, the socket should disappear imo.
But it still there 😂
Description
When listen to unix socket, socket file are not removed when stopping gin process (use
Ctrl + C
). The next time it is executed, the process will report an error:[GIN-debug] [ERROR] listen unix /tmp/testgin.sock: bind: address already in use
How to reproduce
Environment