Why do I get "connection refused" when reaching OpenStack Dashboard

asked 2013-04-18 10:57:12 -0500

60 ●2 ●3 ●9

updated 2013-04-24 01:58:54 -0500

I just tried to install Openstack (grizzly) on Ubuntu 12.04 on a single node to try it out. Everything went perfectly until I tried to install Horizon, which, after 3 days of various attempts just doesn't want to work. I followed this tutorial from the beginning (except the object storage part).

It seems it is the apache and django configuration who would be faulty as I get some errors as soon as I try to connect to Horizon. I can get to the authentication page (127.0.0.1/horizon) and print my login and password (admin, or any other service user). But then I got this error :

http://paste.openstack.org/show/36310/

I can also find this on apache2 logs. When I tried to connect to OpenStack Block Storage service (cinder) I get:

#cinder list
ERROR: [Errno 111] Connection refused

So, in fact, the problem must be with cinder. From what I read in the tutorial, I don't use cinder but nova-volume. I have this conf in nova.conf :

volume_driver=nova.volume.driver.ISCIDriver
volume_group=nova-volumes
volume_name_template=volume-%s
isci_helper=tgtadm

I got this output from #cinder endpoints

This output from #keypoint service-list

This output from #keypoint endpoint-list

More details on my configuration:

So, do I absolutely have to use cinder instead of nova-volume to get Horizon working ?

edit retag flag offensive close merge delete

add a comment

4

answered 2013-04-18 16:08:53 -0500

jpichon

1796 ●4 ●16 ●36

updated 2013-06-07 17:10:59 -0500

smaffulli
6981 ●38 ●68 ●102 http://maffulli.net/

I don't believe this is a problem with your Horizon configuration. The "Connection refused" error appears to come from the Cinder Volume Service. Check that the volume (block storage) endpoints are correct in your keystone catalogue and that the cinder service is up and running. Does "cinder list" work from the command line?

Horizon assumes cinder is installed based on your Keystone service catalogue. If Cinder doesn't exist and is handled by nova, you should remove the cinder/volume endpoints from the catalogue, and Horizon will talk to nova-volume instead. If the tutorial doesn't go into installing Cinder then a bug should probably be filed against openstack-manuals to remove the Volume endpoint creation in the "Creating keystone services and service endpoints" section.

edit flag offensive delete link

Comments

Thanks for your answer, I (and smaffulli ;) ) updated the question. In the tutorial, it seems that we use nova_volume and not cinder. Should I switch to cinder to use Horizon, and then, how ?

epillet ( 2013-04-22 01:35:13 -0500 )edit

1

Hey. Horizon assumes cinder is installed based on your Keystone service catalogue. If Cinder doesn't exist and is handled by nova, you should remove the cinder/volume endpoints from the catalogue, and Horizon will talk to nova-volume instead. If the tutorial doesn't go into installing Cinder then...

jpichon ( 2013-04-25 06:18:38 -0500 )edit

1

...a bug should probably be filed against openstack-manuals to remove the Volume endpoint creation in the "Creating keystone services and service endpoints" section. If you can confirm there is nothing about installing Cinder in the tutorial, it would be great if you reported this doc issue. Thanks!

jpichon ( 2013-04-25 06:21:46 -0500 )edit

Sorry for the delay, yep, it did solve the problem on horizon with the django errors. Do i fill a bug [here]{http://docs.openstack.org/install/} or in some other place for a problem in the documentation ?

epillet ( 2013-05-03 09:52:44 -0500 )edit

You can file bugs about documentation issues at https://bugs.launchpad.net/openstack-manuals - thank you!

jpichon ( 2013-05-03 10:12:11 -0500 )edit

add a comment

1

answered 2013-05-03 16:05:55 -0500

annegentle
858 ●5 ●14 ●17

Thanks for logging a doc bug! It's fixed now, and you can find the instructions to install cinder on the cloud controller at http://docs.openstack.org/grizzly/openstack-compute/install/apt/content/cinder-install.html and http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/.

edit flag offensive delete link

add a comment

1

answered 2013-04-22 08:48:10 -0500

Ph4nToM
216 ●15 ●21 ●34

I had this problem before... You have a problem with you database. look at the line connection = mysql://keystone:keystone@localhost/keystone Verify that you have specified a good login et password in your mysql database

edit flag offensive delete link

Comments

I verified my password with a direct mysql connection. I set up my conf file like this : connection = mysql://keystone:keystonepwd@127.0.0.1/keystone The problem shouldn't come from keystone db connection as it work perfectly on a terminal to create, list and administrate instances with nova.

epillet ( 2013-04-22 09:03:24 -0500 )edit

Look at your iptables... Make a service iptables stop (just for a little moment...)

Ph4nToM ( 2013-04-22 09:05:15 -0500 )edit

In my keystone conf, I edit only mysql://keystone:keystone@127.0.0.1/keystone and I put the line token_format = UUID. And it's work.

Ph4nToM ( 2013-04-22 09:12:27 -0500 )edit

The password I registered is "keystonepwd" so I guess this line should be ok. In what field did you put token_format = UUID ?

epillet ( 2013-04-22 09:20:16 -0500 )edit

token_format = UUID is specified in [signing]

Ph4nToM ( 2013-04-22 09:31:43 -0500 )edit

see more comments

0

answered 2013-04-19 01:47:02 -0500

RomilGupta

834 ●7 ●17 ●29

check whether all openstack services are running . check the failed service log and try to fix it .

do service apache2 restart; service memcached restart; and check the logs.

edit flag offensive delete link

Comments

It seems like every services are running, except that I normally don't use cinder, and as @jpichon said, it seems to be a dependency of nova-django-horizon, so I wonder if we have to use it instead of nova-volumes.

epillet ( 2013-04-19 03:14:46 -0500 )edit

add a comment

0

answered 2013-04-21 06:43:57 -0500

RomilGupta

834 ●7 ●17 ●29

updated 2013-04-21 06:45:22 -0500

If you faced this " ERROR: [Errno 111] Connection refused " do ' unset httpproxy ' or ' unset httpsproxy '

edit flag offensive delete link

Comments

Thanks, but I don't have any variable that is called httpproxy or httpsproxy in my environnement.

epillet ( 2013-04-22 02:02:48 -0500 )edit

its the proxy that you have to :unset http_proxy

RomilGupta ( 2013-04-22 02:17:21 -0500 )edit

Yep, but I don't have such http<whatever> or <whatever>proxy variable to unset in my environment (listed them with "$env". Your command is a bash command right ?

All the same, I tried it and got no change.

epillet ( 2013-04-22 02:28:54 -0500 )edit

jst do cinder --debug list and post the log you got !

RomilGupta ( 2013-04-22 02:34:13 -0500 )edit

Here it is : pasteOpenstack

epillet ( 2013-04-22 02:51:34 -0500 )edit

see more comments

-1

answered 2013-04-24 01:05:37 -0500

fanchen
1

Follow the same steps, also skip the swift, and got the some problem. Also considering change volume to cinder.

edit flag offensive delete link

Comments

thanks it work!

pakito ( 2013-04-24 07:35:41 -0500 )edit

Could you give us some details of the problem you encountered and the solution that worked ;) ?

epillet ( 2013-04-24 08:24:25 -0500 )edit

add a comment

Why do I get "connection refused" when reaching OpenStack Dashboard

6 answers

Comments

Comments

Comments

Comments

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Why do I get "connection refused" when reaching OpenStack Dashboard edit

6 answers

Comments

Comments

Comments

Comments

Comments

Your Answer

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Why do I get "connection refused" when reaching OpenStack Dashboard