Description of problem: Executed openstack-demo-install Version-Release number of selected component: openstack-swift-object-1.7.4-2.fc19 Additional info: cmdline: /usr/bin/python /usr/bin/swift-object-server /etc/swift/object-server.conf dso_list: openstack-swift-1.7.4-2.fc19.noarch executable: /usr/bin/swift-object-server kernel: 3.7.9-201.fc18.x86_64 uid: 160 Truncated backtrace: wsgi.py:89:get_socket:Exception: Could not bind to 127.0.0.1:6000 after trying for 30 seconds Traceback (most recent call last): File "/usr/bin/swift-object-server", line 22, in <module> run_wsgi(conf_file, 'object-server', default_port=6000, **options) File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 133, 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 89, in get_socket bind_addr) Exception: Could not bind to 127.0.0.1:6000 after trying for 30 seconds Local variables in innermost frame: bind_addr: ('127.0.0.1', 6000) address_family: 2 err: error(98, 'Address already in use') sock: None retry_until: 1364991862.200813 warn_ssl: False conf: {'bind_port': '6000', '__file__': '/etc/swift/object-server.conf', 'bind_ip': '127.0.0.1', 'workers': '3', 'here': '/etc/swift'} default_port: 6000 addr: (2, 1, 6, '', ('127.0.0.1', 6000))
Created attachment 731136 [details] File: backtrace
Created attachment 731137 [details] File: core_backtrace
Created attachment 731138 [details] File: environ
object-server should not use by default bind_port = 6000 which is reserved for X11 server
Let's not jump to conclusions. Fedora didn't enable port 6000 in ages, even for localhost. Only UNIX domain sockets are used for X. Reporter, please attach the output of this command: netstat -atpn | grep 6000
[root@dhcp193-51 ~]# netstat -atpn | grep 6000 tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 2049/X tcp6 0 0 :::6000 :::* LISTEN 2049/X [root@dhcp193-51 ~]#
So, Alan guessed right. Now we need to decide if this is worth addressing. Meanwhile this can be worked around by changing the port of object server. This is done in 2 places: 1. Ring definition (hopefully there's a saved ring that can be rebuilt) 2. /etc/swift/object-server/*.conf (for SAIO) or /etc/swift/object-server.conf
*** Bug 977792 has been marked as a duplicate of this bug. ***
*** Bug 1018019 has been marked as a duplicate of this bug. ***
Well, it only took a year, but upstream moves ahead with Phase I, making bind_port mandatory: https://review.openstack.org/118200 At the next step, we'll change the ports without breaking existing clusters.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.