"Error: connect ECONNRESET ::1:13557" while running 'sst dev'
I am seeing this error while running sst dev. It happens during the first deploy when starting sst dev. There are usually a lot of these at the same time (5-10). If I trigger a new incremental deploy it is a success, but I have not checked if the lambdas are actually running 'live' after that success or if they are offline.
I seems to be the connection to the "live" server running the lambdas locally.
I have around 270 functions running live. Maybe the server gets overwhelmed with amount of connections/traffic it receives during the start of the sst dev command?
It did not happen in the beginning but after I added more functions it happens almost every time I start sst dev.
Error: connect ECONNRESET ::1:13557
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:671:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:128:17) {
errno: -54,
code: 'ECONNRESET',
syscall: 'connect',
address: '::1',
port: 13557
}
I see entries like these in my sst.log. Not sure if that is related.
time=2024-09-24T21:31:08.478+02:00 level=INFO msg="lambda disconnected" workerID=400ca50d66c1470ab5c0a5718401f9a9
time=2024-09-24T21:31:08.478+02:00 level=ERROR msg="error writing to the connection" error="io: read/write on closed pipe"
time=2024-09-24T21:31:08.478+02:00 level=INFO msg="lambda sent response" workerID=400ca50d66c1470ab5c0a5718401f9a9
time=2024-09-24T21:31:08.490+02:00 level=INFO msg="lambda request" path="[ lambda 400ca50d66c1470ab5c0a5718401f9a9 runtime init error]"
time=2024-09-24T21:31:08.490+02:00 level=INFO msg="writing to topic" topic=ion/---/400ca50d66c1470ab5c0a5718401f9a9/request/cdbrmeea data=508
time=2024-09-24T21:31:08.733+02:00 level=INFO msg="closed iot writer" topic=ion/---/400ca50d66c1470ab5c0a5718401f9a9/request/cdbrmeea count=1
time=2024-09-24T21:31:08.733+02:00 level=INFO msg="lambda waiting for response" workerID=400ca50d66c1470ab5c0a5718401f9a9