Ask Your Question
1

update failed: 503 service unavailable

asked 2011-03-22 07:59:04 -0500

zyh-at-bupt gravatar image

when I create openstack object storage admin account, this problem happens. after I input: swift-auth-add-user -K devauth -a system root testpass the terminal output: update failed: 503 service unavailable

the /var/log/syslog is as follow: Mar 22 15:40:17 swift-desktop auth-server validate_token('AUTH_tk9ca08031dd164712a25c36e05131aee0', _, _) = (86399.977941989899, '.super_admin', '.single_use', '.reseller_admin') [0.00] Mar 22 15:40:17 swift-desktop auth-server 127.0.0.1 - - [22/Mar/2011:07:40:17 +0000] "GET /token/AUTH_tk9ca08031dd164712a25c36e05131aee0 HTTP/1.0" 204 - "-" "-" - - - - - - - - - "-" "127.0.0.1" "-" 0.0038 Mar 22 15:40:17 swift-desktop proxy-server ERROR with Account server 192.168.1.125:6004/sda8 re: Trying to PUT to /v1/AUTH_20f431da534d444899e34f5d551d8498: Connection refused (txn: txc7ff39aa-bfc3-425e-b596-d0c75304e6e6) Mar 22 15:40:17 swift-desktop proxy-server ERROR with Account server 192.168.1.125:6003/sda7 re: Trying to PUT to /v1/AUTH_20f431da534d444899e34f5d551d8498: Connection refused (txn: txc7ff39aa-bfc3-425e-b596-d0c75304e6e6) Mar 22 15:40:17 swift-desktop proxy-server Account PUT returning 503 for [400, 201, 503] (txn: txc7ff39aa-bfc3-425e-b596-d0c75304e6e6) Mar 22 15:40:17 swift-desktop auth-server ERROR attempting to create account https://swift-desktop:8080/v1/AUTH_20f431da534d444899e34f5d551d8498 (https://swift-desktop:8080/v1/AUTH_20...) : 503 Internal Server Error Mar 22 15:40:17 swift-desktop auth-server FAILED create_user('system', 'root', _, True, False) [0.05] Mar 22 15:40:17 swift-desktop auth-server 127.0.0.1 - - [22/Mar/2011:07:40:17 +0000] "PUT /account/system/root HTTP/1.0" 503 - "-" "-" - - - - - - - - - "-" "127.0.0.1" "-" 0.0511 Mar 22 15:40:17 swift-desktop proxy-server - 127.0.1.1 22/Mar/2011/07/40/17 PUT /v1/AUTH_20f431da534d444899e34f5d551d8498 HTTP/1.0 503 - - .super_admin%3A.single_use%2CAUTH_tk9ca08031dd164712a25c36e05131aee0 - - - txc7ff39aa-bfc3-425e-b596-d0c75304e6e6 - 0.0281

edit retag flag offensive close merge delete

18 answers

Sort by ยป oldest newest most voted
0

answered 2011-04-29 16:49:57 -0500

david-goetz gravatar image

Looks like the devices aren't mounted properly:

Apr 27 03:53:51 ubuntu container-replicator Skipping sda1 as it is not mounted

Also memcached doesn't seem to be responding:

Apr 27 03:53:26 ubuntu proxy-server Error talking to memcached:

edit flag offensive delete link more
0

answered 2011-09-08 06:42:47 -0500

tonytkdk gravatar image

SO , I'm facing same problem with "dev/sdb1 is not mounted"

but , I do check it with mount ...

/dev/sdb1 is already mounted to /srv/node/sdb1

and the permission of /srv/node/sdb1 is

root@SwiftZ3:/srv/node# ll total 8 drwxr-xr-x 3 swift swift 4096 2011-09-07 14:15 ./ drwxr-xr-x 3 root root 4096 2011-09-07 14:15 ../ drwxr-xr-x 2 swift swift 6 2011-09-08 14:25 sdb1/ root@SwiftZ3:/srv/node#

edit flag offensive delete link more
0

answered 2011-04-28 09:06:36 -0500

moubarik-siham gravatar image

hi , I can't create the account

root@ubuntu:~# swauth-add-user -K sawthkey -a system root testpass Account creation failed: 403 Forbidden User creation failed: 403 Forbidden

can you help me please .?

edit flag offensive delete link more
0

answered 2011-04-28 19:07:27 -0500

david-goetz gravatar image

Can't really see what the problem is with just that. Could you copy/paste in the error logs?

edit flag offensive delete link more
0

answered 2013-05-23 07:51:26 -0500

I have the Swift Proxy server and 3 nodes as per the hastexo documentation site. I still get the error when I try to test The error is

Account GET failed: http://10.1.168.105:8080/v1/AUTH_76d66f46c50b42fc8f88574f2cddf08f?format=json (http://10.1.168.105:8080/v1/AUTH_76d6...) 503 Internal Server Error

Any help..!!

edit flag offensive delete link more
0

answered 2011-03-28 00:48:29 -0500

zyh-at-bupt gravatar image

clayg, thank you very much, I will try it. Then, I will tell you the result.

edit flag offensive delete link more
0

answered 2011-03-25 09:27:48 -0500

zyh-at-bupt gravatar image

clayg, thank you very much. I restart the memcached service, still this problem.

syslog on the proxy node: Mar 25 17:24:38 swift-desktop proxy-server Account PUT returning 503 for [503, 503, 503] (txn: txa9d5b4f6-2051-462f-8e8f-e1d1fa17c2d1) Mar 25 17:24:38 swift-desktop proxy-server - 192.168.1.130 25/Mar/2011/09/24/38 PUT /v1/AUTH_cadad33181144d32af4d0f6ceea9bdba HTTP/1.0 503 - - .super_admin%3A.single_use%2CAUTH_tk02e78a624ff943cea89cbddeab68c485 - - - txa9d5b4f6-2051-462f-8e8f-e1d1fa17c2d1 - 0.0146

edit flag offensive delete link more
0

answered 2011-03-22 18:35:45 -0500

clay-gerrard gravatar image

looks like maybe the account-servers aren't started? Or they aren't listening at 192.168.1.125:6004?

Is this a mutli-node setup? Are the account-servers running on a different machine than the proxy?

Can you check the log on 192.168.1.125 and see if the account-server is running and if there are any errors in the log?

edit flag offensive delete link more
0

answered 2011-03-24 09:27:30 -0500

zyh-at-bupt gravatar image

thank you, clayg , I had installed the swift again, and I met the problem again, I do not know how to solve it, please help me to solve it. thanks.

after I input: swift-auth-add-user -K devauth -a system root testpass the terminal output: update failed: 503 service unavailable

the information is as follow: I have 3 vms,:auth node, proxy node, storage node

openstack-proxy 192.168.1.127 openstack-auth 192.168.1.130 openstack-storage 192.168.1.125

storage node has 3 devices: sda5,sda6,sda7 /dev/sda5 4.7G 4.3M 4.7G 1% /srv/node/sda5 /dev/sda6 4.7G 4.3M 4.7G 1% /srv/node/sda6 /dev/sda7 5.6G 4.3M 5.6G 1% /srv/node/sda7 /dev/sr0 686M 686M 0 100% /media/Ubuntu 10.04.1 LTS i386

root@swift-desktop:/etc/swift# swift-ring-builder account.builder account.builder, build version 3 262144 partitions, 3 replicas, 3 zones, 3 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id zone ip address port name weight partitions balance meta 0 1 192.168.1.125 6002 sda5 100.00 262144 0.00 1 2 192.168.1.125 6002 sda6 100.00 262144 0.00 2 3 192.168.1.125 6002 sda7 100.00 262144 0.00 root@swift-desktop:/etc/swift# swift-ring-builder container.builder container.builder, build version 3 262144 partitions, 3 replicas, 3 zones, 3 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id zone ip address port name weight partitions balance meta 0 1 192.168.1.125 6001 sda5 100.00 262144 0.00 1 2 192.168.1.125 6001 sda6 100.00 262144 0.00 2 3 192.168.1.125 6001 sda7 100.00 262144 0.00 root@swift-desktop:/etc/swift# swift-ring-builder object.builder object.builder, build version 3 262144 partitions, 3 replicas, 3 zones, 3 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id zone ip address port name weight partitions balance meta 0 1 192.168.1.125 6000 sda5 100.00 262144 0.00 1 2 192.168.1.125 6000 sda6 100.00 262144 0.00 2 3 192.168.1.125 6000 sda7 100.00 262144 0.00

proxy-server.conf:

[DEFAULT] cert_file = /etc/swift/cert.crt key_file = /etc/swift/cert.key bind_port = 8080 workers = 8 user = swift

[pipeline:main] pipeline = healthcheck cache auth proxy-server

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

[filter:auth] use = egg:swift#auth ssl = true ip= 192.168.1.130

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

[filter:cache] use = egg:swift#memcache memcache_servers = 192.168.1.127:11211

auth-server.conf:

[DEFAULT] cert_file = /etc/swift/cert.crt key_file = /etc/swift/cert.key user = swift

[pipeline:main] pipeline = auth-server

[app:auth-server] use = egg:swift#auth default_cluster_url = https://192.168.1.127:8080/v1

Highly recommended to change this key to something else ...

(more)
edit flag offensive delete link more
0

answered 2011-03-24 15:02:56 -0500

clay-gerrard gravatar image

Hrm.. so you should probalby fix the memcached thing. Make sure memcached is installed (aptitude install memcached -y) and running (service memcached restart)

Then either retry the account create, or you should be able to verify memcache is working by connecting and issuing a command directly:

$ telnet 192.168.1.127 11211 Trying 192.168.1.127... Connected to 192.168.1.127. Escape character is '^]'. version VERSION 1.4.2 ^]

telnet> quit Connection closed.

But I don't think that's the whole problem. The proxy is reporting that all the account servers are returning 503 Server Error. What errors do you see in syslog on the storage node (192.168.1.125)?

edit flag offensive delete link more

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: 2011-03-22 07:59:04 -0500

Seen: 3,303 times

Last updated: Jun 12 '13