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
Exit status of master should be non-zero in case of error #1183
Comments
👍 |
1 similar comment
👍 |
Actually it is expected to return with exit status [2016-05-02 15:50:57 +0200] [58904] [INFO] Worker exiting (pid: 58904)
[2016-05-02 15:50:57 +0200] [58901] [INFO] Shutting down: Master
[2016-05-02 15:50:57 +0200] [58901] [INFO] Reason: Worker failed to boot.
(gunicorn_py3)[examples] echo $? 15:50:57 ☁ master ☂ ⚡ ✭
3 what shell are you using? |
Hey, using bash. But both of our shells should be working fine :-) (let's assume that for now, wouldn't it be horrible if my shell didn't properly expose the exit code of the process that last terminated?) I think for making progress, we probably need to find the difference between our cases of making the worker fail. I unfortunately do not remember how I made it fail at the time of reporting. One thing I also cannot exclude: maybe I had gunicorn running in a wrapper (shell script, for instance)? I doubt that, but as I have unfortunately not explicitly written that above, we shouldn't exclude this. So, next time I can hopefully provide a more complete report. |
bump |
no answer since awhile. closing the issue since I was not able to reproduce it myself. |
Of course I am not 100 % sure about how this has been decided, but I would expect to see a non-zero exit code after master shutdown when a worker failed to boot. That is, this was highly surprising to me:
The text was updated successfully, but these errors were encountered: