Ask Your Question
0

after configuring swift service, getting (Account HEAD failed: http://controller02:8080/v1/AUTH_805e0875107440b9b852254ef2559f4e 500 Internal Error)

asked 2018-12-30 06:10:58 -0600

Malik Shehroz gravatar image

kindly check and help me out with this.

root@controller02:~# . admin-openrc root@controller02:~# swift stat Account HEAD failed: http://controller02:8080/v1/AUTH_805e0875107440b9b852254ef2559f4e (http://controller02:8080/v1/AUTH_805e...) 500 Internal Error Failed Transaction ID: tx69ebf7b0536d474d81933-005c28b4a0 root@controller02:~#

below are the logs:

Dec 30 16:49:18 controller02 proxy-server: Starting Keystone auth_token middleware Dec 30 16:49:18 controller02 proxy-server: Starting Keystone auth_token middleware Dec 30 16:49:18 controller02 proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. Dec 30 16:49:18 controller02 proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. Dec 30 16:49:18 controller02 proxy-server: Starting Keystone auth_token middleware Dec 30 16:49:18 controller02 proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. Dec 30 16:49:21 controller02 swift-proxy[4745]: Starting proxy-server...(/etc/swift/proxy-server.conf) Dec 30 16:49:21 controller02 swift-proxy[4745]: No handlers could be found for logger "keystonemiddleware._common.config" Dec 30 16:49:21 controller02 swift-proxy[4745]: ...done. Dec 30 16:49:21 controller02 systemd[1]: Started LSB: Swift proxy server. Dec 30 16:49:38 controller02 proxy-server: - - 30/Dec/2018/11/49/38 HEAD /v1/AUTH_805e0875107440b9b852254ef2559f4e%3Fformat%3Djson HTTP/1.0 200 - Swift - - - - tx6774e8d3ddcc466388d9f-005c28b0d2 - 0.0081 RL - 1546170578.119056940 1546170578.127141953 - Dec 30 16:49:38 controller02 keystoneauth.identity.generic.base: Failed to discover available identity versions when contacting http://controller02:35357. Attempting to parse version from URL. Dec 30 16:49:38 controller02 proxy-server: 192.168.100.3 192.168.100.3 30/Dec/2018/11/49/38 HEAD /v1/AUTH_805e0875107440b9b852254ef2559f4e%3Fformat%3Djson HTTP/1.0 500 - python-swiftclient-3.5.0 gAAAAABcKLDSpmWX... - - - tx6774e8d3ddcc466388d9f-005c28b0d2 - 0.0204 - - 1546170578.116504908 1546170578.136944056 - Dec 30 16:49:38 controller02 proxy-server: Error: An error occurred: #012Traceback (most recent call last):#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/catch_errors.py", line 41, in handle_request#012 resp = self._app_call(env)#012 File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 1074, in _app_call#012 resp = self.app(env, self._start_response)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/gatekeeper.py", line 123, in __call__#012 return self.app(env, gatekeeper_response)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/healthcheck.py", line 52, in __call__#012 return self.app(env, start_response)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/proxy_logging.py", line 346, in __call__#012 six.reraise(exc_type, exc_value, exc_traceback)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/proxy_logging.py", line 338, in __call__#012 iterable = self.app(env, my_start_response)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/memcache.py", line 109, in __call__#012 return self.app(env, start_response)#012 File "/usr/lib/python2.7/dist-packages/swift/common/middleware/listing_formats.py", line 137, in __call__#012 ... (more)

edit retag flag offensive close merge delete

Comments

From your log:

Failed to discover available identity versions when contacting http://controller02:35357

Is that server name and port the correct Keystone endpoint? If yes, is Keystone running? Can you reach it at this address/port?

Bernd Bausch gravatar imageBernd Bausch ( 2018-12-30 09:51:30 -0600 )edit

yes server and port is correct. i haven't change any thing on keystone and yet it is showing inactive.

root@controller02:~# systemctl status keystone.service ● keystone.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) root@controller02:~#

Malik Shehroz gravatar imageMalik Shehroz ( 2018-12-30 22:28:29 -0600 )edit

You don't seem to have a service named "keystone.service". It's probably called something else.

Does systemctl list-units | grep -i keystone reveal something?

Bernd Bausch gravatar imageBernd Bausch ( 2018-12-30 22:34:55 -0600 )edit

thanks bernd issue seems to resolve now after changing port# in authtoken section of proxy-server.conf.

[filter:authtoken] www_authenticate_uri = http://controller02:5000 auth_url = http://controller02:5000

Malik Shehroz gravatar imageMalik Shehroz ( 2018-12-30 23:44:49 -0600 )edit

I guessed something like that. Great that you have a solution!

Bernd Bausch gravatar imageBernd Bausch ( 2018-12-31 00:19:54 -0600 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2018-12-31 05:49:42 -0600

Malik Shehroz gravatar image

issue seems to resolve now after changing port# in authtoken section of proxy-server.conf.

[filter:authtoken] www_authenticate_uri = http://controller02:5000 auth_url = http://controller02:5000

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: 2018-12-30 06:10:58 -0600

Seen: 86 times

Last updated: Dec 30 '18