Ask Your Question

what's this (startmain): Exception: Could not bind to after trying for 30 seconds?

asked 2013-07-26 11:00:34 -0500

acatto gravatar image

updated 2013-08-06 11:45:57 -0500

Jobin gravatar image

Hello community, I finally got something moving forward with the installation, I chose root:root for the user:group in the saio instructions because I have no time to fine tune or take the chance that I'll have to reinstall again, I just need SAIO to work and develop a cloud protocol against it, done.

My issue now, when I run the startmain I get the following: (link to screen shot: )

root@saio:~# startmain
Starting proxy-server...(/etc/swift/proxy-server.conf)
Starting container-server...(/etc/swift/container-server/1.conf)
Starting container-server...(/etc/swift/container-server/2.conf)
Starting container-server...(/etc/swift/container-server/3.conf)
Starting container-server...(/etc/swift/container-server/4.conf)
Starting account-server...(/etc/swift/account-server/1.conf)
Starting account-server...(/etc/swift/account-server/2.conf)
Starting account-server...(/etc/swift/account-server/3.conf)
Starting account-server...(/etc/swift/account-server/4.conf)
Starting object-server...(/etc/swift/object-server/1.conf)
Starting object-server...(/etc/swift/object-server/2.conf)
Starting object-server...(/etc/swift/object-server/3.conf)
Starting object-server...(/etc/swift/object-server/4.conf)
Traceback (most recent call last):
  File "/usr/local/bin/swift-object-server", line 7, in <module>
  File "/root/swift/bin/swift-object-server", line 22, in <module>
    run_wsgi(conf_file, 'object-server', default_port=6000, **options)
  File "/root/swift/swift/common/", line 244, in run_wsgi
    sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))
  File "/root/swift/swift/common/", line 161, in get_socket
    bind_addr[0], bind_addr[1], bind_timeout))
Exception: **Could not bind to** after trying for 30 seconds

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-08-06 10:46:24 -0500

acatto gravatar image

thank you, ssh is the fault,

I was using ssh which uses that port (somehow), why I don't know, I'll research. I work easier with it.

edit flag offensive delete link more

answered 2013-07-27 23:50:22 -0500

clayg gravatar image

updated 2013-07-28 10:57:19 -0500

It means another process is already bound to that port - probably X.

If it's a swift process, swift-orphans should help you find it.

Otherwise maybe netstat -plnt

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-07-26 11:00:34 -0500

Seen: 1,056 times

Last updated: Aug 06 '13