Bug 1200041
| Summary: | [abrt] python-gunicorn: arbiter.py:459:reap_workers:HaltServer: <HaltServer 'Worker failed to boot.' 3> | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | redhat | ||||||
| Component: | python-gunicorn | Assignee: | Dan Callaghan <dcallagh> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 23 | CC: | dcallagh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/bee348ff2b9b0f7fe515758b5aae3d78440365d0 | ||||||||
| Whiteboard: | abrt_hash:fb652b19a97dc270b57b52daffea2473cea8d329 | ||||||||
| Fixed In Version: | python-gunicorn-19.3.0-3.fc23 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1592152 (view as bug list) | Environment: | |||||||
| Last Closed: | 2016-08-16 00:50:52 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 999590 [details]
File: backtrace
Created attachment 999591 [details]
File: environ
This is quite possibly just a bug in your application where it crashes on startup. Do you have the full stderr from invoking gunicorn and/or a reproducer? The real bug here is probably just that abrt should not be picking up this condition as an unhandled exception at all... Submitted an upstream PR to make gunicorn halt cleanly in this case, instead of dying with an unhandled exception. https://github.com/benoitc/gunicorn/pull/1095 This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. No new gunicorn version yet so this is still an issue. My upstream PR has got lost by the wayside, I should probably apply the patch in Fedora to clean up these abrt reports... python-gunicorn-19.3.0-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-90b539e46d python-gunicorn-19.3.0-3.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update python-gunicorn' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-65d7705cd0 python-gunicorn-19.3.0-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update python-gunicorn' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-90b539e46d python-gunicorn-19.3.0-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: tried to start pyramid wsgi app with gunicorn cd /path/to/project gunicorn .:main Version-Release number of selected component: python-gunicorn-19.1.1-2.fc21 Additional info: reporter: libreport-2.3.0 cmdline: /usr/bin/python /usr/bin/gunicorn .:main executable: /usr/bin/gunicorn kernel: 3.18.7-200.fc21.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: arbiter.py:459:reap_workers:HaltServer: <HaltServer 'Worker failed to boot.' 3> Traceback (most recent call last): File "/usr/bin/gunicorn", line 9, in <module> load_entry_point('gunicorn==19.1.1', 'console_scripts', 'gunicorn')() File "/usr/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 74, in run WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() File "/usr/lib/python2.7/site-packages/gunicorn/app/base.py", line 185, in run super(Application, self).run() File "/usr/lib/python2.7/site-packages/gunicorn/app/base.py", line 71, in run Arbiter(self).run() File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 169, in run self.manage_workers() File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 477, in manage_workers self.spawn_workers() File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 542, in spawn_workers time.sleep(0.1 * random.random()) File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 209, in handle_chld self.reap_workers() File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 459, in reap_workers raise HaltServer(reason, self.WORKER_BOOT_ERROR) HaltServer: <HaltServer 'Worker failed to boot.' 3> Local variables in innermost frame: status: 768 reason: 'Worker failed to boot.' wpid: 21690 self: <gunicorn.arbiter.Arbiter object at 0x7ffba0249490> exitcode: 3