Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Socket does not exit - Attempt to listen on socket, aws-serverless-express will restart the Node.js server
See original GitHub issueI am getting a warning when I make requests against my aws-serverless-express server. I run the server using the serverless offline plugin as well. The warning reads as follows:
WARNING: Attempting to listen on socket /tmp/server0.sock, but it is already in use. This is likely as a result of a previous invocation error or timeout. Check the logs for the invocation(s) immediately prior to this for root cause, and consider increasing the timeout and/or cpu/memory allocation if this is purely as a result of a timeout. aws-serverless-express will restart the Node.js server listening on a new port and continue with this request.
Any ideas what’s happening here? Each further request I make, the socket error increments, so if I’ve made two requests I get two warnings, if I make three requests I have three warnings and so on…
Issue Analytics
- State:
- Created 6 years ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fixed in v3.1.1
@jeremygiberson thanks for this.
@munkyjunky I have temporarily adopted
serverless-httpand it works well withserverless-offline.If I have some time I will look into how they work with closing sockets and see if there is something that can be inspired to work with this package.