-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
NPM as spawned child process does not work #81
Comments
Hello. I have the same problem. I have an app in Nodejs that running with pm2 sends the error 'Access is denied'. How can I make PM2 run as administrator privileges. Or do they have a good execution practice? Please support me, I have been struggling with this for several days and the only way to solve it was to not use PM2 and create a Windows Task Scheduler. @Choppel Did you find any solution?
|
Description
Running on Windows Server 2022, Node 14.21.3, Npm 6.14.18
This is more a question regarding the necessity of running pm2 as "Local Service" rather than a bug report.
An app spawned by pm2 runs properly. Pm2 says it runs as Administrator and everything works as expected. But then this app spawns npm via NodeJS child_process, npm does not work properly. The output is seen below. The culprit seems to be the fact that pm2 is started as "Local Service". When I change it to "Administrator" npm is spawned correctly by the app.
Maybe, on Windows, a child_process is spawned by the user that pm2 runs as and not the user my app runs as. On Linux this is not a problem.
Steps to Reproduce
If it helps I could provide a precise example.
Environment
Running on: 26.4.2023, pm2-installer 3.4.3 with node v14.21.3 and npm 6.14.18 on win32-10.0.20348.
The text was updated successfully, but these errors were encountered: