Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nodejs server kills itself #320

Open
argenx-pmason opened this issue Nov 17, 2022 · 3 comments
Open

nodejs server kills itself #320

argenx-pmason opened this issue Nov 17, 2022 · 3 comments

Comments

@argenx-pmason
Copy link

When using the extension I find that every so often, usually if I havent run something for a while, the server has stopped running and I have to restart it. There doesnt seem to be any reason. No message or warning. Please fix.

@allanbowe allanbowe transferred this issue from sasjs/vscode-extension Nov 17, 2022
@allanbowe
Copy link
Member

Hi Phil - are you able to attempt persistence using the pm2 npm tool?

https://github.com/sasjs/server#persisting-the-session

There is nothing in the server itself that forces a stoppage, rather it is a system issue. Hence the need for a 'wrapper' facility to keep the session alive.

@argenx-pmason
Copy link
Author

Thanks - I will try that.

@jbodart-argenx
Copy link

For me, using pm2 on windows solved the problem of the server being stopped and not restarted.
Now it restarts automatically, so there is always a server ready to process my programs.

However pm2 does not prevent the server stopping while waiting for a long running program to complete.
In such a case the submitted program seems to terminate prematurely, and the log file retrieved only contains:

read ECONNRESET

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants