I ran into this bug that rears its ugly head once in a while, where the

yarn start

process just stops listening. it says “Listening for requests…” but when the front end makes requests, I can see that nothing happens, and the front end gets a 500 error. you guys want me to send any logs over?

And yarn start executes

sst start

?

yep

I see. It’s weird that you cannot kill the process. I suspect if the WebSocket that SST opens hangs

yeah, seems like an issue with the websocket connection.

pkill node

killed the process without issue

Hm did it die right when you started it

it did work for a while. this usually happens with long-running processes

Hey @Sam Hulick

this usually happens with long-running processes

Do you mean when sst start has been running for a while? Or the Lambda function is long-running (ie. runs for 10min then returns)?

the sst start process

I see. does it happen after leaving it on for a few hours? over night? couple of days?

A few hours

I see. Let me leave it on over night and test in the morning.

@Frank sure thing!