-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Cannot read property pm2_env of undefined #2870
Comments
PM2/NodeJS version ? |
Which Docker image are you using also? |
Node version 6.10.1 |
I just updated to pm2 version 2.4.6, and I am getting the same error.
|
I think this might have to do with having a |
Same error - totally killed a deploy for me today. Node 7.10.0 Going to try to revert back to diff version(s).. |
Published under PM2 |
@tnguyen14 I think it may have to do with if the log file specified is accessible/writeable. That's what appeared to have solve the issue for me. |
confirmed, it has been fixed. you can try the fix:
|
@andyfleming can you confirm what you did to fix this? I am using the latest docker container and it is still an issue. |
Same here |
To be honest, I can't remember what project I was working on where I ran into this, but I believe what solved the issue for me was reconfiguring the log settings (because the process didn't have permission to write logs where it was trying to). If you use a {
"apps" : [{
//...
"error_file": "/dev/stderr",
"out_file": "/dev/stdout",
//...
}]
} |
Could you share the exact error you have ? @ivoribeiro @zachariahtimothy |
@andyfleming thanks I tried that with the same error.
|
Hi @zachariahtimothy I had very similar error. Please make sure that you app.js file is in the expected location. |
I came across the same error - turns out I had a typo in the args for pm2-docker. |
Hi,
I'm trying to use pm2 inside a docker container (it works fine on the host machine), and I am getting this error:
I tried to look this up, and it seems that
data
ismsg.args
from the socket? I'm not sure what this is, or how to debug it further.Is there anything I could do to figure out this issue further?
The text was updated successfully, but these errors were encountered: