Ask Your Question
0

saio error, swift instructions, don't work!!!

asked 2013-07-24 12:24:44 -0500

acatto gravatar image

Tried the latest instructions as they are like, countless times, used the same ubuntu version server 12.04.02 lts from scratch, and I ALWAYS get an error during 'unit tests' and startmain.

~/swift/.unittests 1>1.out 2>2.out reports errors, here's the log: https://docs.google.com/file/d/0BwZ6oWiCB_x9eW5mdjFBZ21hU28/edit?usp=sharing

startmain's errors: https://docs.google.com/file/d/0BwZ6oWiCB_x9R205YjdJMk0wMVk/edit?usp=sharing something like ( Error trying to load config from /etc/swift/proxy-server.conf: root)

you can see the WHOLE VIDEO here: https://docs.google.com/file/d/0BwZ6oWiCB_x9SXcwYnNWSF9kWU0/edit?usp=sharing

edit retag flag offensive close merge delete
add a comment

3 answers

Sort by ยป oldest newest most voted
0

answered 2013-07-25 10:42:02 -0500

clayg gravatar image

I'm really sorry you're having trouble, thanks for the detailed description.

Here's the relevant section of the SAIO guide to your dilemma[1]:

Much of the configuration described in this guide requires escalated root privileges; however, we assume that administrator logs in an unprivileged user. Swift processes also run under a separate user and group, set by configuration option, and refered as <your-user-name>:<your-group-name>. The default user is swift, which may not exist on your system.

It seems like you setup a swift user ~18:50

But I noted in the screen shot that you configured and started services as root.

You can either

a) always use root:root when it says <your-user-name>:<your-group-name>

b) switch to the swift user starting in the "Getting the code"[2] section

More people use option b, so I'd recommend that.

Good Luck!

  1. http://docs.openstack.org/developer/swift/development_saio.html#what-s-in-a-your-user-name
  2. http://docs.openstack.org/developer/swift/development_saio.html#getting-the-code
edit flag offensive delete link more

Comments

First of all, thank you very much for spending time, helping out and getting me further. I have opted for the easy route, all root:root, I know it might be insecure but it's just for me to develop a client against it. I'm still getting another new error now. look at this please: https://docs.google.com/file/d/0BwZ6oWiCB_x9azVYemJ5cjNxblU/edit?usp=sharing also in text format: 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.c

acatto gravatar imageacatto ( 2013-07-25 18:55:52 -0500 )edit
add a comment
0

answered 2013-11-11 04:25:15 -0500

koolhead17 gravatar image

@acatto Are you still facing the issue with the Swift install?

edit flag offensive delete link more
add a comment
0

answered 2013-07-25 18:57:41 -0500

acatto gravatar image

First of all, thank you for the time spend and help, here's the new error though: (I decided to REINSTALL ALL from scratch each time including the iso image because I want to have a FRESH test), I chose root:root, I don't care of security for my client tests , and it seems easier. Here's the image: https://docs.google.com/file/d/0BwZ6oWiCB_x9azVYemJ5cjNxblU/edit?usp=sharing Here's the actual text, if you want:

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> execfile(__file__) 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/wsgi.py", line 244, in run_wsgi sock = get_socket(conf, default_port=kwargs.get('default_port', 8080)) File "/root/swift/swift/common/wsgi.py", line 161, in get_socket bind_addr[0], bind_addr[1], bind_timeout)) Exception: Could not bind to 0.0.0.0:6010 after trying for 30 seconds

root@saio:~# ^C root@saio:~#

edit flag offensive delete link more

Comments

that's a separate question, and a duplicate of https://ask.openstack.org/en/question/3455/whats-this-startmain-exception-could-not-bind-to-00006010-after-trying-for-30-seconds/

clayg gravatar imageclayg ( 2013-08-07 17:18:28 -0500 )edit
add a comment

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

subscribe to rss feed

Stats

Asked: 2013-07-24 12:24:44 -0500

Seen: 645 times

Last updated: Nov 11 '13

Related questions

swift unit testin error centos 6.5

starting rcopenstack-swift-proxy errno 1?

SAIO testing: could not bind to 127.0...6010

Unable to get swift service info on horizon after login

running gnocchi-api with swift all-in-one install fails

Error in deleting IP on Openstack

Swift authentification probelm

object-replicator error with rsync

Rally throwing errors for heat testing.

401 Unauthorized