update EADDRINUSE warning (currently a red-herring) to explain what likely happened; closes #5

Author: brettstack

README.md

@@ -20,7 +20,7 @@ exports.handler = (event, context) => awsServerlessExpress.proxy(server, event,
 
 ## Quick Start/Example
 
-Want to get up and running quickly? [Check out our example](example/README.md) which includes:
+Want to get up and running quickly? [Check out our example](example) which includes:
 
  - Lambda function
  - Express server

example/scripts/local.js

@@ -24,4 +24,5 @@ function exitHandler(options, err) {
 
 process.on('exit', exitHandler.bind(null, { cleanup: true }))
 process.on('SIGINT', exitHandler.bind(null, { exit: true })) // ctrl+c event
+process.on('SIGTSTP', exitHandler.bind(null, { exit: true })) // ctrl+v event
 process.on('uncaughtException', exitHandler.bind(null, { exit: true }))

index.js

@@ -155,7 +155,7 @@ function createServer (requestListener, serverListenCallback, binaryTypes) {
     })
     .on('error', (error) => {
         if (error.code === 'EADDRINUSE') {
-            console.warn(`EADDRINUSE ${getSocketPath(server._socketPathSuffix)} incrementing socketPathSuffix.`)
+            console.warn(`WARNING: Attempting to listen on socket ${getSocketPath(server._socketPathSuffix)}, 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.`)
             ++server._socketPathSuffix
             return server.close(() => startServer(server))
         }