Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Some things to look at:

  1. Something is already bound to that port, run netstat -plnt to find out what.

  2. Some swift process has been orphaned and is still running on that port (but not showing up with netstat? doesn't seem likely)

  3. You have multiple conf files in your swift directory all using the same bind address.

My vote is on option 3 because you said netstat doesn't show the ports in use, but clearly a swift process cannot bind them. Thus leading me to think one gets bound, the other fails, then everything terminates on error.