Bug 1592152

Summary: [abrt] python-gunicorn: arbiter.py:459:reap_workers:HaltServer: <HaltServer 'Worker failed to boot.' 3>
Product: Red Hat Enterprise Linux 7 Reporter: Dan Callaghan <dcallagh>
Component: python-gunicornAssignee: John Keck <jkeck>
Status: CLOSED WONTFIX QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: extras-qa, redhat
Target Milestone: rcKeywords: Extras, Patch
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1200041 Environment:
Last Closed: 2021-02-15 07:39:38 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:
Description Flags
0001-handle-HaltServer-in-manage_workers.patch none

Description Dan Callaghan 2018-06-17 22:41:21 UTC 
RHEL7 python-gunicorn is also affected by this bug which I encountered (and fixed) in the Fedora package. See cloned text below.

This is triggering abrt reports against CentOS 7.


+++ This bug was initially created as a clone of Bug #1200041 +++

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
Comment 2 Dan Callaghan 2018-06-17 22:42:28 UTC 
Created attachment 1452469 [details]
0001-handle-HaltServer-in-manage_workers.patch

The patch landed in gunicorn 19.4.2 but it also applies (with some tweaks) against 18.0. Attached.
Comment 5 RHEL Program Management 2021-02-15 07:39:38 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.