Ask Your Question
1

[solved] Problem verifying installation of Swift. [Errno 111] Connection refused

asked 2014-09-23 13:42:39 -0600

Iván Sixto gravatar image

updated 2014-09-25 08:37:07 -0600

Hi, I just installed Swift on a fresh installation of OpenStack.

I've got a problem when doing swift stat:

Account HEAD failed: http://zeus:8080/v1/AUTH_37d8b1fb62374ef9a5642f992f624eec 503 Internal Server Error

I think is about proxy server not being able to authenticate with Storage nodes, but I'm not pretty sure...

I've been reviewing my proxy-server.conf and I don't see any error...

Do you have any idea guys?

My proxy-server.conf: [DEFAULT] bind_port = 8080 user = swift

[pipeline:main]
pipeline = healthcheck cache authtoken keystoneauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:keystoneauth]
use = egg:swift#keystoneauth
operator_roles = Member,admin,swiftoperator

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = true
# cache directory for signing certificate
#   signing_dir = /opt/swift/keystone-signing
# auth_* settings refer to the Keystone server
auth_protocol = http
auth_host = zeus
auth_port = 35357
# the service tenant and swift username and password created in Keystone
admin_tenant_name = service
admin_user = swift
admin_password = passswift


[filter:cache]
use = egg:swift#memcache

[filter:catch_errors]
use = egg:swift#catch_errors

[filter:healthcheck]
use = egg:swift#healthcheck

Just say that zeus is controller node (where keystone is installed).

Thanks

PD: All devices on Storage nodes are mounted.

EDITED:

From rsyslog: /var/log/messages

Sep 23 22:34:23 zeus proxy-server: Auth Token confirmed use of v2.0 apis
Sep 23 22:34:23 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:23 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:23 zeus proxy-server: Account GET returning 503 for [] (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: Account GET returning 503 for [] (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: Account GET returning 503 for [] (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:30 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET ...
(more)
edit retag flag offensive close merge delete

Comments

Kindly check the ports are opened on both the proxy and storage nodes.Check the syslog. Make sure memcache is configured.

ebyenjoys gravatar imageebyenjoys ( 2014-09-23 14:00:43 -0600 )edit

Did you resolve metadata issue https://ask.openstack.org/en/question... before installing swift ?

dbaxps gravatar imagedbaxps ( 2014-09-23 14:20:22 -0600 )edit

dbaxps, answared on that topic ;)

ebyenjoys, i uploaded rsyslog on first post. I'll check ports tomorrow (roaming data is getting over ;S)

Iván Sixto gravatar imageIván Sixto ( 2014-09-23 15:42:54 -0600 )edit

Ok, fixed error on /var/log/messages by adding and changing bind_ip with storage network IP in proxy-server.conf (on controller) and container, account and object conf files on Storage nodes.

But, still same issue when swift stat (connecion refused).

Iván Sixto gravatar imageIván Sixto ( 2014-09-24 15:47:12 -0600 )edit

Ok, I have definitely no idea about what's going on.

If I look on keystone log I'm able to see how Swift user is authenticated. Please, have you got any idea?

Iván Sixto gravatar imageIván Sixto ( 2014-09-24 16:25:04 -0600 )edit

1 answer

Sort by » oldest newest most voted
1

answered 2014-09-25 06:38:35 -0600

guimaluf gravatar image

updated 2014-09-25 08:21:54 -0600

You can change bind_address of swift-proxy to 0.0.0.0 or change the endpoint on 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.

edit flag offensive delete link more

Comments

hi! thanks for replying.

I updated first post with all info.

;)

Iván Sixto gravatar imageIván Sixto ( 2014-09-25 07:41:37 -0600 )edit

I've also noticed that there is no content on

/etc/swift/object-server /etc/swift/container-server /etc/swift/account-server

...

Iván Sixto gravatar imageIván Sixto ( 2014-09-25 08:04:24 -0600 )edit

one more thing: which ip points to zeus? Cause your proxy-node is listen on 8080 in your mgnt IP. Maybe the name zeus is resolving to another IP.

tcp 0 0 192.168.20.2:8080 0.0.0.0:* LISTEN 4936/python

guimaluf gravatar imageguimaluf ( 2014-09-25 08:05:58 -0600 )edit

oh... Ehm,

zeus is pointed to management network 192.168.10.2

but proxy node is listening on 192.168.20.2 (storage network).. is that bad config?

Iván Sixto gravatar imageIván Sixto ( 2014-09-25 08:08:09 -0600 )edit

Ok, I understand that actually it is a bad config...

The enpoint is pointing to ZEUS -> 192.168.10.2...

Then I have to change bind_ip on proxy-config to 192.168.10.2 instead 192.168.20.2.

I'll check it our in a sec.

Iván Sixto gravatar imageIván Sixto ( 2014-09-25 08:14:24 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-09-23 13:42:39 -0600

Seen: 2,270 times

Last updated: Sep 25 '14