-
Notifications
You must be signed in to change notification settings - Fork 2.6k
PM2_GRACEFUL_LISTEN_TIMEOUT/listen_timeout not working correctly #2956
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
Labels
Comments
Bug reproduced, seems like there is something missing |
Unitech
added a commit
that referenced
this issue
Jun 26, 2017
Fixed, you can try the fix: $ npm install Unitech/pm2#development -g
$ pm2 update |
Thanks @Unitech, any idea when the next release will go out? |
Published on PM2 2.6.0: $ npm install pm2@latest -g
$ pm2 update |
inerc
pushed a commit
to inerc/pm2
that referenced
this issue
Feb 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
So I'm attempting to use
wait_ready
withlisten_timeout
in my app but it appears as if thelisten_timeout
is not actually working as expected.When attempting to see if it works as expected using the example (https://github.com/Unitech/pm2/tree/master/examples/wait-ready), it doesn't appear to be the case either.
The specific behavior that appears to be broken is even after the listen_timeout expires, pm2 still waits.
Steps to reproduce:
listen_timeout
to be1000
I've also tested this using
fork
mode as well. Is my understanding of this feature correct in that it should stop waiting and report an error status oncelisten_timeout
is exceeded?The text was updated successfully, but these errors were encountered: