Can't access controller node

asked 2014-05-11 16:42:43 -0600

danoreilly gravatar image

Controller & network nodes running RHEL 6.5. Compute node running CentOS 6.5. Neutron & Nova installed on compute node just fine, but I can't access the controller node. For example:

keystone --debug user-list

DEBUG:keystoneclient.session:REQ: curl -i -X POST http://tm1cldctll01:35357/v2.0/tokens -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-keystoneclient" -d '{"auth": {"te nantName": "admin", "passwordCredentials": {"username": "admin", "password": "pass-admin"}}}' INFO:urllib3.connectionpool:Starting new HTTP connection (1): 8080 Authorization Failed: Unable to establish connection to http://tm1cldctll01:35357/v2.0/tokens [NEW:note: root@tm1cldcmpl03 on parent: /root] #

This looks very suspicious. I have another controller node running RHEL 6.5, and it works OK. The HTTP connection info, though, looks different:

DEBUG:keystoneclient.session:REQ: curl -i -X POST http://xxxctlxxx:35357/v2.0/tokens -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-keystoneclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "pass-admin"}}}' INFO:urllib3.connectionpool:Starting new HTTP connection (1): xxxctlxxx DEBUG:urllib3.connectionpool:"POST /v2.0/tokens HTTP/1.1" 200 7939 DEBUG:keystoneclient.session:RESP: [200] {'date': 'Sat, 10 May 2014 00:42:20 GMT', 'content-type': 'application/json', 'content-length': '7939', 'vary': 'X-Auth-Token'}

Any idea why the differences?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-05-11 17:41:00 -0600

blazesurfer gravatar image

if you have access to the tm1cldctl01 node, i would personally start a tail -f /var/log/messages and try again the other two logs i normally check when looking at these issues

/var/log/warn /var/log/apache2/error_log

note i am running SLES 11sp3 though similar logs im sure.

once tailing on the log i normaly then try the request again.

other thing is that your connection response in tm1cldctl01 request is saying 8080 authorization failed.. in my tests so far that is normally the hand off to the proxy server failing.. maybe check your endpoint configuration as well. I could be way off the mark with this last bit but the logs should help highlight more direction.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2014-05-11 16:42:43 -0600

Seen: 265 times

Last updated: May 11 '14