https://serverless-stack.com/ logo
#help
Title
# help
s

Sam Hulick

10/26/2021, 9:16 PM
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?
hmm, the debug log isn’t even logging anything when I make API calls
I hit ^C to kill the process and it’s stuck.. won’t even quit
ö

Ömer Toraman

10/26/2021, 9:22 PM
And yarn start executes
sst start
?
s

Sam Hulick

10/26/2021, 9:22 PM
yep
ö

Ömer Toraman

10/26/2021, 9:23 PM
I see. It’s weird that you cannot kill the process. I suspect if the WebSocket that SST opens hangs
s

Sam Hulick

10/26/2021, 9:24 PM
yeah, seems like an issue with the websocket connection.
pkill node
killed the process without issue
t

thdxr

10/27/2021, 1:21 AM
Hm did it die right when you started it
or did it work for a while
s

Sam Hulick

10/27/2021, 1:23 AM
it did work for a while. this usually happens with long-running processes
f

Frank

10/27/2021, 1:30 AM
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)?
s

Sam Hulick

10/27/2021, 1:31 AM
the sst start process
f

Frank

10/27/2021, 1:32 AM
I see. does it happen after leaving it on for a few hours? over night? couple of days?
s

Sam Hulick

10/27/2021, 2:28 AM
A few hours
f

Frank

10/27/2021, 7:27 AM
I see. Let me leave it on over night and test in the morning.
When
yarn start
gets stuck again, can you look up the CW logs for the lambda that got the 500 error, and paste it here. That should provide more context.
s

Sam Hulick

10/27/2021, 3:58 PM
@Frank sure thing!
2 Views