JakkeL's profile - activity

2014-02-17 15:22:41 -0600 received badge  Famous Question (source)
2014-01-29 09:01:04 -0600 commented answer swift stat commad doesn't give proper response

Would like to, but even if I have configred Swift to log events to syslog, can't find any events from the logs. Below is my logging configuration from proxy-server.conf.


set log_name = proxy-server 			#Label used when logging
set log_facility = LOG_LOCAL0			#Syslog log facility
set log_level = DEBUG			#Log level

2014-01-27 08:38:06 -0600 commented answer swift stat commad doesn't give proper response

DEBUG:iso8601.iso8601:Parsed 2014-01-28T14:27:31Z into {'tz_sign': None, 'second_fraction': None, 'hour': u'14', 'tz_hour': None, 'month': u'01', 'timezone': u'Z', 'second': u'31', 'tz_minute': None, 'year': u'2014', 'separator': u'T', 'day': u'28', 'minute': u'27'} with default timezone <iso8601.iso8601.utc object="" at="" 0xd87f90="">
DEBUG:iso8601.iso8601:Got u'2014' for 'year' with default None
DEBUG:iso8601.iso8601:Got u'01' for 'month' with default None
DEBUG:iso8601.iso8601:Got u'28' for 'day' with default None
DEBUG:iso8601.iso8601:Got u'14' for 'hour' with default None
DEBUG:iso8601.iso8601:Got u'27' for 'minute' with default None
DEBUG:iso8601.iso8601:Got u'31' for 'second' with default None

Command does aquire tokens from identity service just fine, that I can see from the output. But nothing happens after this time section. Please advice what is wrong?

2014-01-27 08:37:48 -0600 commented answer swift stat commad doesn't give proper response

Hi, fixed that service start error that i posted above, that was caused by value log_address = /var/log in the .conf files. As soon as i commented it out services start fine. So now I have all three .conf files in place at all storage nodes, I have rebuild rings and copied new .gz files to all storage nodes. All services are up and running and listening correct ports at all storage nodes. But still when I'm running swift --debug stat command at proxy node, execution of that command stops to this,

2014-01-27 08:37:48 -0600 received badge  Commentator
2014-01-26 17:59:21 -0600 commented answer swift stat commad doesn't give proper response

Here is link to my account-server.conf, container-server.conf and object-server.conf files files, http://pastebin.ubuntu.com/6823435/%3C/p%3E (http://pastebin.ubuntu.com/6823435/)

2014-01-26 17:52:40 -0600 commented answer swift stat commad doesn't give proper response

and this one,


Traceback (most recent call last):
  File "/usr/bin/swift-object-server", line 22, in <module>
    run_wsgi(conf_file, 'object-server', default_port=6000, **options)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 245, in run_wsgi
    _initrp(conf_path, app_section, *args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 337, in _initrp
    log_route='wsgi')
  File "/usr/lib64/python2.6/site-packages/swift/common/utils.py", line 930, in get_logger
    raise e
socket.error: [Errno 111] Connection refused

2014-01-26 17:52:24 -0600 commented answer swift stat commad doesn't give proper response

And this error,


Traceback (most recent call last):
  File "/usr/bin/swift-account-server", line 22, in <module>
    run_wsgi(conf_file, 'account-server', default_port=6002, **options)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 245, in run_wsgi
    _initrp(conf_path, app_section, *args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 337, in _initrp
    log_route='wsgi')
  File "/usr/lib64/python2.6/site-packages/swift/common/utils.py", line 930, in get_logger
    raise e
socket.error: [Errno 111] Connection refused

2014-01-26 17:39:15 -0600 commented answer swift stat commad doesn't give proper response

Added those misssing account-server.conf, container-server.conf and object-server.conf files, now when I'm starting swift-init main start,


Starting proxy-server...(/etc/swift/proxy-server.conf)
Starting container-server...(/etc/swift/container-server.conf)
Starting account-server...(/etc/swift/account-server.conf)
Starting object-server...(/etc/swift/object-server.conf)

I Get following errors;


Traceback (most recent call last):
  File "/usr/bin/swift-container-server", line 22, in <module>
    run_wsgi(conf_file, 'container-server', default_port=6001, **options)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 245, in run_wsgi
    _initrp(conf_path, app_section, *args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/swift/common/wsgi.py", line 337, in _initrp
    log_route='wsgi')
  File "/usr/lib64/python2.6/site-packages/swift/common/utils.py", line 930, in get_logger
    raise e
socket.error: [Errno 111]

2014-01-22 12:54:25 -0600 received badge  Famous Question (source)
2014-01-19 15:43:05 -0600 commented answer swift stat commad doesn't give proper response

Ok, so those misssing account-server.conf, container-server.conf and object-server.conf files may have something to do with the odd behavior of swift stat command. I'll configure those files (found some examples with google) and try to re-build rings.

2014-01-17 23:49:17 -0600 received badge  Popular Question (source)
2014-01-17 23:49:17 -0600 received badge  Notable Question (source)
2014-01-13 09:12:57 -0600 received badge  Editor (source)
2014-01-11 14:09:56 -0600 asked a question swift stat commad doesn't give proper response

Hi,

I have installed Swift to SLES 11 SP3 servers, now when I'm running command swift -V 2.0 -A $OS_AUTH_URL -U demo:admin -K $ADMINPASS stat to verify that Swift works properly, command stucks during execution. When used command with --debug found out that proxy server does reply with auth token, but then command stucks to following phase,

DEBUG:iso8601.iso8601:Parsed 2014-01-12T19:33:14Z into {'tz_sign': None, 'second_fraction': None, 'hour': u'19', 'tz_hour': None, 'month': u'01', 'timezone': u'Z', 'second': u'14', 'tz_minute': None, 'year': u'2014', 'separator': u'T', 'day': u'12', 'minute': u'33'} with default timezone <iso8601.iso8601.Utc object at 0xd87f90>
DEBUG:iso8601.iso8601:Got u'2014' for 'year' with default None
DEBUG:iso8601.iso8601:Got u'01' for 'month' with default None
DEBUG:iso8601.iso8601:Got u'12' for 'day' with default None
DEBUG:iso8601.iso8601:Got u'19' for 'hour' with default None
DEBUG:iso8601.iso8601:Got u'33' for 'minute' with default None
DEBUG:iso8601.iso8601:Got u'14' for 'second' with default None

Link to full output of the command ( http://pastebin.ubuntu.com/6734582/ )

Tried to see if either /var/logs/warnings or /var/logs/messages would containg any information, but it seems that Swift doesn't log any errors there-

Also few questions comes to my mind, first when ring creation is initiated, should it populate some kind of directory structure under /srv/node/<dev_name> ? And when storage nodes are set up, shoud one configure account-server.conf, container-server.conf and object-server.conf files? There wasn't any instructions for such action in deployment guide.</dev_name>

2014-01-11 13:56:45 -0600 answered a question Unable to authenticate to Swift using keystone

Problem solved. During the MySQL db creation, db was secured as was http://docs.openstack.org/trunk/install-guide/install/zypper/content/basics-database-controller.html (instructed) . This causes situation where installation script cannot communicate with db even when db is bind to servers ip. Following error "CRITICAL keystone [-] (OperationalError) (2003, "Can't connect to MySQL server on 'HOSTNAME' (111)") None None" was logged when command openstack-db --init --service keystone --password KEYSTONE_DBPASS was given. At this time, after securing db, manually edited MySQL db to approve root connection also from other then localhost and everything works.

2014-01-11 10:11:27 -0600 received badge  Enthusiast
2014-01-08 15:57:18 -0600 commented question Unable to authenticate to Swift using keystone

And I'm not able to connect keystone db with credentials used at the time of when db was created. Next re-install db with instructions from https://ask.openstack.org/en/question/332/keystone-unable-to-connect-to-mysql-durring-grizzy-setup/ and then create keystone db.

2014-01-08 15:49:41 -0600 commented question Unable to authenticate to Swift using keystone

Looks that there is an issue with the mysql db that keystone is using. Went through the logs, and found out some errors like "CRITICAL keystone [-] (OperationalError) (2003, "Can't connect to MySQL server on 'authserv' (111)") None None" at the time of db creation. Firewall is down at both sides.

2014-01-07 15:09:58 -0600 received badge  Notable Question (source)
2014-01-07 08:03:14 -0600 received badge  Popular Question (source)
2014-01-06 13:20:41 -0600 commented question Unable to authenticate to Swift using keystone

Later one doesn't have backslash after AUTH_. Which one is the correct format?

2014-01-06 13:20:07 -0600 commented question Unable to authenticate to Swift using keystone

Found that answer and checked and did all things (users, tenants, service endpoints) mentioned in it before posting this. Regarding to service endpoint creation, I have found two types of syntax that should be used, "http://IP:8080/v1/AUTH_\$(tenant_id)s" and "http://IP:8080/v1/AUTH_$(tenant_id)s"

2014-01-04 18:53:35 -0600 asked a question Unable to authenticate to Swift using keystone

Hi,

I have deployed Swift and Keystone to my SLES 11 SP3 servers for testing purposes following these http://docs.openstack.org/trunk/install-guide/install/zypper/content/ch_swift.html (Swift) and http://docs.openstack.org/trunk/install-guide/install/zypper/content/ch_keystone.html (Keystone) instruction for SLES -Havanna. Got all services on all servers running nicely, but now when I tried to verify the Swift setup from Swift proxy server, using command swift -V 2.0 -A $OS_AUTH_URL -U service:swift -K $OS_PASSWORD stat, I'm getting error [Errno 111] Connection refused.

Before issuing that command, I did setup those variables export OS_PASSWORD=[PASSWORD DEFINED AT proxy-server.conf TO admin_password AND AT IDENTITY SERVICE TO swift USER] and export OS_AUTH_URL=http://[IDENTITYSERV_HOSTNAME]:5000/v2.0 at Swift proxy server.

Also tried to get the Swift stat at proxy serv with command swift --os-auth-url http://[IDENTITYSERV_HOSTNAME]:5000/v2.0 --os-tenant-name service --os-username swift --os-password [PASSWORD DEFINED FOR USER swift AT IDENTITY SERVER] stat, got same error as before. Also tried command swift --os-auth-url http://[PROXYSERV_HOSTNAME]:8080/auth/v1.0 --os-tenant-name service --os-username swift --os-password [PASSWORD DEFINED FOR USER swift AT IDENTITY SERVER] stat, that just got stuck doing nothing.

I have set up tenant for swift at identity server keystone tenant-create --name=service --description="Service Tenant" and user keystone user-create --name=swift --pass=[PASSWORD], created admin role and mapped those together keystone user-role-add --user=swift --tenant=service --role=admin as instructed in the Keystone guide.

I have tried to google a solution to this error and verified that my http://pastebin.ubuntu.com/6694115/ (proxy-server.conf) contains same field and information that other users have used. From the identity server, he's my keystone.conf http://pastebin.ubuntu.com/6694179/ (keystone.conf) file.

As per my understanding, servers are listening correct ports so that should't be an issue.

At Swift Proxy server, netstat -ant:

tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN

and at the Keystone Identity server, netstat -ant:

tcp 0 0 0.0.0.0:35357 0.0.0.0:* LISTEN

tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN

So now I'm quite lost what is the issue in this case. Everything should be just like instructed, but still no-go. Thanks in advance for any help.