Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

If the connections is been refused, probably means your rsyncd is not properly configured.

Is rsyncd running? Paste rsyncd configs and check if ports and IP are correct set.

If the connections is been refused, probably means your rsyncd is not properly configured.

Is rsyncd running? Paste rsyncd configs rsyncd.conf and check if ports and IP are correct set.

Which ports are open? Run netstat -lvpn and check it out.

There is any firewall running? Is it blocking ports 873, 6000, 6001, 6002?

If the connections is been refused, probably means your rsyncd is not properly configured.

Is rsyncd running? Paste rsyncd.conf and check if ports and IP are correct set.

Which ports are open? Run netstat -lvpn and check it out.

There is any firewall running? Is it blocking ports 873, 6000, 6001, 6002?

========

Ive just realize your problem it's happening also on proxy-node.

What endpoints are set on keystone? Also run swift --debug stat and paste for us

If the connections is been refused, probably means your rsyncd is not properly configured.

Is rsyncd running? Paste rsyncd.conf and check if ports and IP are correct set.

Which ports are open? Run netstat -lvpn and check it out.

There is any firewall running? Is it blocking ports 873, 6000, 6001, 6002?

========

Ive just realize your problem it's happening also on proxy-node.

What endpoints are set on keystone? Also run swift --debug stat and paste for us

=========

By the netstat all services are listen in any ip address 0.0.0.0:port so when you send zeus at endpoint it listen and respond to service. But only for swift-proxy you're binding the service to 192.168.20.2:8080.

When keystone give you back swift-proxy endpoint the IP address of zeusis resolv to another IP, not 192.168.20.2, then the swift-proxy refuses the connection since the IP it's binding is different from the IP resolved by the name zeus.

You can change bind of swift-proxy to 0.0.0.0 or change the endpoint on keystone.

If the connections is been refused, probably means your You can change bind_address of swift-proxy to rsyncd0.0.0.0 is not properly configured.

Is rsyncd running? Paste rsyncd.conf and check if ports and IP are correct set.

Which ports are open? Run netstat -lvpn and check it out.

There is any firewall running? Is it blocking ports 873, 6000, 6001, 6002?

========

Ive just realize your problem it's happening also or change the endpoint on proxy-node.

What endpoints are set on keystone? Also run swift --debug stat and paste for us

=========keystone.

By the netstat all services are listen in any ip address 0.0.0.0:port so when you send zeus at endpoint it listen and respond to service. But only for swift-proxy you're binding the service to 192.168.20.2:8080.

When keystone give you back swift-proxy endpoint the IP address of zeusis resolv to another IP, not 192.168.20.2, then the swift-proxy refuses the connection since the IP it's binding is different from the IP resolved by the name zeus.

You can change bind of swift-proxy to 0.0.0.0 or change the endpoint on keystone.