After running sls offline start I can't then stop the process by doing CTRL+C in terminal. I'm having to manually pick out the PID using netstat in order to kill the serverless process running on port 3000 to restart serverless.
Has anyone else come up against this? It's also blocking our build process as our integration tests spin up the serverless process in order to run requests against our endpoints..
Hi @ammarhaider7 is it still the case ? I'm willing to fix it if yes.
Hi @dherault , this is still the case. Confirming that we've had issues in build machines where the port is still in use even after exiting a previously running serverless-offline process.
What is your environment ?
Sorry for the delay !
if anyone is still experiencing this issue, feel free to re-open, ideally with some repro steps, or better, a repro repository. thanks!
This happens to me when I run sls offline start with npm scripts.
CTRL + C seems leave the child process instead of killing it.
I have same problem with npm run sls offline start
I also have the same issue and cannot find to resolve this issue.
Ctrl + C works for me, but for programmatic control I think it would be nice to have an sls offline stop command! 馃榿
I have no idea how to actually stop this...
It does not stop through Ctrl+C in PyCharm terminal. As of now I have to close the PyCharm IDE and restart it again. I am wondering if anyone has got any solution or not yet. It would be great if it supports both Ctrl+C and sls offline stop command to stop the instance.
Most helpful comment
Hi @dherault , this is still the case. Confirming that we've had issues in build machines where the port is still in use even after exiting a previously running serverless-offline process.