Closed
Bug 1040396
Opened 10 years ago
Closed 10 years ago
Somehow silence StopIteration errors during gunicorn shutdown
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Cloud Services Graveyard
Server: Token
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Unassigned)
Details
(Whiteboard: [qa+])
Per Bug 1039803 Comment 7: """ Seen the StopIteration exception before. It is a gunicorn thing when nginx closes the TCP socket without sending any data. see: https://github.com/benoitc/gunicorn/issues/65 Here's the actual gunicorn code: https://github.com/benoitc/gunicorn/blob/master/gunicorn/workers/async.py#L116 Not entirely sure how to silence it but it sounds like it can safely be ignored. """
Updated•10 years ago
|
Whiteboard: [qa+]
Reporter | ||
Comment 1•10 years ago
|
||
Bob, has this been fixed with the updated gunicorn version? IIRC this is one of the things mentioned in the changelog for that release. (The socket errors still occur, specifically I'm interested in the StopIteration tracebacks)
Flags: needinfo?(bobm)
Comment 2•10 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #1) > Bob, has this been fixed with the updated gunicorn version? IIRC this is > one of the things mentioned in the changelog for that release. > > (The socket errors still occur, specifically I'm interested in the > StopIteration tracebacks) There is no occurrence of StopIteration in any of the Sync application logs on any of the Sync nodes!
Flags: needinfo?(bobm)
Reporter | ||
Comment 3•10 years ago
|
||
Awesome, I'm closing this out.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•