Red Hat Bugzilla – Bug 995765
[abrt] openstack-swift-proxy-1.8.0-2.fc19: socket.py:224:meth:error: [Errno 99] Cannot assign requested address
Last modified: 2015-02-18 09:04:55 EST
Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf
socket.py:224:meth:error: [Errno 99] Cannot assign requested address
Traceback (most recent call last):
File "/usr/bin/swift-proxy-server", line 22, in <module>
run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 125, in run_wsgi
sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))
File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 81, in get_socket
File "/usr/lib/python2.7/site-packages/eventlet/convenience.py", line 38, in listen
File "/usr/lib64/python2.7/socket.py", line 224, in meth
error: [Errno 99] Cannot assign requested address
Local variables in innermost frame:
self: <socket._socketobject object at 0x1a63520>
args: (('10.11.164.206', 8080),)
Potential duplicate: bug 977792
Created attachment 785283 [details]
Created attachment 785284 [details]
Created attachment 785285 [details]
Thom, did you use swift-init together with systemctl by any chance?
(In reply to Pete Zaitcev from comment #4)
> Thom, did you use swift-init together with systemctl by any chance?
I don't know how Thom is reproducing this, but I get this on reboot post RDO+packstack all in one install using openstack-havana.
That sounds right, I was following the instructions while at FLOCK. Unfortunately, the VM was removed a couple of hours ago.
Mark, could you please capture /etc/swift? The only thing that comes to
mind is that somehow you ended with /etc/swift/proxy-server/1.conf.
I would not put it past the Packstack.
Clearing NEEDINFO, N/A to me.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.