1

HTTPConnectionPool(host='192.168.1.12', port=8774): Max retries exceeded with url: /v2/70a04e8259b04717bf1bdd4faaedbc0c/extensions (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

asked 2014-01-05 10:33:38 -0600

www
68 ●8 ●11 ●16

updated 2014-01-22 15:12:43 -0600

Evgeny
1 ●2 ●4

I've got the following error while trying to connect to the dashboard: HTTPConnectionPool(host='192.168.1.12', port=8774): Max retries exceeded with url: /v2/70a04e8259b04717bf1bdd4faaedbc0c/extensions (Caused by <class 'socket.error'="">: [Errno 111] Connection refused) could anybody explain it to me please?</class>

edit retag flag offensive close merge delete

Comments

Can you check compute service is up ? Can you try telnet 192.168.1.12 8774. Does this work ?

dheeru ( 2014-01-05 11:08:05 -0600 )edit

no, it does not. knwing that I am using devstack.

www ( 2014-01-05 11:59:12 -0600 )edit

Compute should be up right ? If not up, it will surely give the above problem. Please restart all your services and try again.

dheeru ( 2014-01-05 21:34:38 -0600 )edit

I got same error. I see that in all openstack based service include /etc/"service"/"service.conf". in which one line "connection = ..." In section [database]. if you forgot to update it to correct. you will get same error. so always first check it.

hk ( 2016-06-26 15:29:10 -0600 )edit

4 answers

Sort by » oldest newest most voted

3

answered 2014-01-08 13:28:00 -0600

www
68 ●8 ●11 ●16

actually I discovered that the problem was due to the size of the RAM of the VM. In fact, when I increased it everything worked ordinarly. Thank you.

edit flag offensive delete link

Comments

How much memory, I give controller node 1.2G memory, or report this error.just running keystone,glance and nova

Livenux Chou ( 2014-04-26 04:46:40 -0600 )edit

I used to use 1GB. But after getting into trouble with MySQL and this. I safely give my VM 1.5GB of memory.

Kashyap Kopparam ( 2014-06-06 05:57:56 -0600 )edit

thank you it's work to me i use 4GB for ram before that it's 3GB

RezaER ( 2015-01-25 05:18:34 -0600 )edit

0

answered 2014-01-06 05:07:08 -0600

unmesh-gurjar
1141 ●2 ●8 ●23

Ensure that your nova-api service is running on host having IP 192.168.1.12 and is listening on port 8774.

edit flag offensive delete link

Comments

if it is not the case, what should I do?

www ( 2014-01-06 16:16:18 -0600 )edit

You need to check for the nova-api service logs (devstack defaults to /var/log/nova/api.log) to determine the cause of service start up failure. Paste the logs onto paste.openstack.org and provide the link here if you need help in tracking down the issue.

unmesh-gurjar ( 2014-01-06 23:30:47 -0600 )edit

Hi! I have the same problem as yours. I use my laptop as host platform to install OpenStack via devstack and meet the same problem as yours. Did you mean if you increase the size of your host machine memory, then the problem will be solved? Thanks!

gavingo15 ( 2014-01-08 20:42:39 -0600 )edit

Yes @gavingo

www ( 2014-01-09 15:27:32 -0600 )edit

0

answered 2014-12-12 07:21:22 -0600

Venu Murthy
121 ●8 ●4

Ok, in my case, while I am trying this on Ubuntu 14.04 and Juno on the below command I would get the status as below and the logs were frozen.

service nova-api start

nova-api stop/waiting

For some strange reason nova-api had gone missing, reinstalling it fixed the problem.

edit flag offensive delete link

0

answered 2015-01-05 03:29:22 -0600

frippe75
1 ●1 ●3 ●4

updated 2015-01-05 03:30:44 -0600

It most likely due to having to little memory, check requirements on devstack dot org

I guess it all boils down to the OOM implementation of Linux. It's Linux handling out-of-memory situations. nova-api process is being killed. See console or grep messages for "killed process"

The behaviour can be altered. Read up by googling "OOM killer"

edit flag offensive delete link

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-01-05 10:33:38 -0600

Seen: 19,338 times

Last updated: Jan 05 '15

Related questions