--log-to-socket invalid socket protocol

Bug #1367513 reported by John-William Trenholm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gunicorn (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Description: Ubuntu 14.04.1 LTS
Release: 14.04
Python 2.7.6

Hello,
I'm using gunicorn's --log-to-socket feature and on trusty I get an error which prevents gunicorn from starting. The error bails with Socket error 91: Invalid protocol. This is due to a change in Python's 2.7.6 sockets.py.

It appears that upstream has already patched this bug with the following commit. Would it be possible to patch this for the community?

https://github.com/benoitc/gunicorn/commit/24bfae8508b7d55898e8a421268856b38ed29fbc#diff-3f0ccdab4e1ca658f432ac7feb652cca

The expected behavior is that I can specify the unix socket protocol type at startup.

/usr/bin/gunicorn --bind=unix:/var/run/nginx/thing.sock --backlog=64 --workers=8 --max-requests=2000 --timeout=60 --user www-data --group www-data --umask 0022 --log-syslog --log-syslog-to "unix:///dev/log#dgram" --log-syslog-facility local0 --log-syslog-prefix thing thing.wsgi:application

I've already resolved this in my own ppa, however I was hoping we could get this patched rolled out for everyone.

Thank you,
John-William Trenholm

Revision history for this message
Chuck Short (zulcss) wrote :

This patch was applied already and fixed in xenial I dont think its a good candiate for an SRU.

Changed in gunicorn (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.