Keystone Unable to Establish Connection [closed]

asked 2015-02-17 16:01:52 -0500

ALU.RDC gravatar image

Hello everyone. I'd like to provide you with a very clear concise description of what I have set up, so there is no ambiuguity.

I have 1 single server, with 1 active network interface. I'm running OpenSuSE 13.1. I'm trying to install Openstack-keystone. I have the option of running through a proxy, but at the moment, I have it set to disabled in /etc/sysconfig/proxy. My export list has no proxy variables set. but I did have a no_proxy="localhost,, <myip" variable="" set="" at="" one="" time="" during="" testing.="" <="" p="">

Ok, so with that background, onto my problem. I have set up openstack-keystone, mysql-python (which uses mariadb)

My first issue is this when I start keystone I get this output:

Loaded: loaded (/etc/init.d/openstack-keystone) Active: active (exited) since Tue 2015-02-17 04:44:02 EST; 7min ago Process: 4262 ExecStop=/etc/init.d/openstack-keystone stop (code=exited, status=0/SUCCESS) Process: 4272 ExecStart=/etc/init.d/openstack-keystone start (code=exited, status=0/SUCCESS)

The status is Active (Exited). As opposed to other processes that have Active (running). I thought this may be normal, but in running netstat -atp or netstat -tulpen I see nothing that shows that the keystone process is listening for connections. My /etc/keystone/keystone.conf (which i'll post shortly) has it's bind address to and it listening on ports 35357 and 5000.

Yet when I go to run or start openstack-keystone, while it recieves a real process ID, it shows no listening port. I've grepped for it, and everything. There is nothing listening on 35357 or 5000. Now before this issue comes up, I have opened up the ports in SuSEfirewall. In fact, I actually disabled the entire firewall itself, unloaded all rules. Currently, the system is wide open, no firewall rules exist.

So this leads to the next issue. I'm not sure if they are related. After I even start openstack-keystone (when it is in active (exited)), I try to connect to the mysql database. From the terminal i can issue 'mysql -u root -p" and enter the database no problem. In fact, I ran a keystone-manage db_sync keystone, and it populated the keystone table with 18 entries. So I'm assuming that all is correct....

The problem is when I take it a step further. I use the command 'keystone tenant-create --name admin --description 'admin-tenant'

This is where things get really hairy. The error I'm getting is:

Unable to establish connection to

That's the error I receive if I set the OS_SERVICE_ENDPOINT equal to I've tried many options such as localhost, controller, and my own interface's IP address. The results are the same. It is unable to establish a connection. I can only assume this is linked to the fact that I see nothing listening on ports 35357 and 5000 ... (more)

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by PradeepNaik
close date 2015-02-18 02:46:01.983559