-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
node processes get killed after session sign out #78
Comments
I'm having the same issue. The @jessety/pm2-logrotate module is running, but the app.js is not. I can use the command pm2 resurrect and it starts the app. I have also tried going to services and making sure that pm2 is running on the Local System account. |
I'm using nvm to upgrade the Node.js version from v14 to v18.16.0 and then the mentioned issue occurred. After some trial and error, I solved the issue with the following steps:
|
Thanks a lot @itm-platform. The pm2 service was shutting down almost as soon as it started. Just rebooted the server (for the sake of testing) and my three node apps are running as expected. Server environment:
Last thing, I upgraded the dependencies in package.json before running: npm run configure
npm run configure-policy
npm run setup "dependencies": {
"@jessety/pm2-logrotate": "^2.7.4",
"node-windows": "1.0.0-beta.8",
"pm2": "5.3.0"
}, |
Whenever I sign out, my pm2 / node processes get killed. When signing in back again, the only one visible is the module
@jessety/pm2-logrotate
Installation
I installed pm2-installer following the steps as Admin:
npm run configure
,npm run configure-policy
,npm run setup
.What I've tried
npm configure
andsetup
several timesinfo:
Running on: 21/03/2023, pm2-installer 3.4.3 with node v14.15.3 and npm 6.14.9 on win32-10.0.17763.
Thanks for any help!
The text was updated successfully, but these errors were encountered: