quantum net-list Connection refused
hi, it becomes puzzling: instaulując werję grizzly step by step, I can not do with network options noda quantum net-list or anything else but associated with Quantum, is the answer
"[Errno 111] Connection refused".
also trying to do this query on the controller node connection is refused.
Is anyone able to identify it?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- neutron Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Assuming quantum-server has not crashed, probably keystone is returning a wrong endpoint for it.
With admin credentials, check that keystone endpoint-list returns the correct quantum endpoint.
If keystone endpoint-list fail with errno 111 too, then probably your problem is that keystone is not running.
Hope this helps,
Salvatore
Revision history for this message
|
#2 |
Thank you for your answear!! You said that maybe keystone returning a wrong endpoint for it... well..
i trying do:
keystone tenant-list
and I get
+------
| id | name | enabled |
+------
| a76e7598cf49449
| 717d7110950e49d
| 836ec35d7939411
+------
mmm... but keystone endpoint-list
returns me an answer but how can I recognize wheather it is correct endpoint? I get :
root@grizzly-
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+------
| id | region | publicurl | internalurl | adminurl | service_id |
+------
| 5e89addbd9ed44d
| 7aaf057998b04ab
| 86476822f9fb429
| 96f4decb603442e
| cabd14c7b3ae450
| ef8d851797da4a7
+------
so I thnik keystone is runnig... Am i right?
Do you have (or someone else) any other sugegstion?
Thank you :)
Revision history for this message
|
#3 |
use quantum net-list -v to see which http request is blocking u and then fix the related URL problem.
Revision history for this message
|
#4 |
mmm.... Ok, thanks. :)
I get some answer, this:
root@grizzly-
DEBUG: quantumclient.
DEBUG: quantumclient.
REQ: curl -i http://
DEBUG: quantumclient.
DEBUG: quantumclient.
DEBUG: quantumclient.
REQ: curl -i http://
DEBUG: quantumclient.
DEBUG: quantumclient.
ERROR: quantumclient.shell [Errno 111] Connection refused
DEBUG: quantumclient.shell clean_up ListNetwork
DEBUG: quantumclient.shell got an error: [Errno 111] Connection refused
Can I expect a hint what to do?
after:
curl -v -H "X-Auth-Token: password" -H "Content-type: application/json" http://
I get normaal json answer so keyston is running ( I think)
Revision history for this message
|
#6 |
Are you sure that your quantum-server is running? You'd see that error if it's not:
# quantum net-list
+------
| id | name | subnets |
+------
| c09f9856-
+------
# service quantum-server stop
quantum-server stop/waiting
# quantum net-list
[Errno 111] Connection refused
Revision history for this message
|
#7 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
Revision history for this message
|
#8 |
yes, I'm sure that quantum-server is running! I'm sure for 100% .
quantum-server is running on Controller node. I can add networks and do every command connected with quantum via quantum-server on Controller node.
But... quantum on Network Node is not running, i get
root@network:~# quantum net-list
[Errno 111] Connection refused
, doing quantum net-list -v , i get:
DEBUG: quantumclient.
DEBUG: quantumclient.
REQ: curl -i http://
DEBUG: quantumclient.
DEBUG: quantumclient.
DEBUG: quantumclient.
REQ: curl -i http://
DEBUG: quantumclient.
DEBUG: quantumclient.
ERROR: quantumclient.shell [Errno 111] Connection refused
DEBUG: quantumclient.shell clean_up ListNetwork
DEBUG: quantumclient.shell got an error: [Errno 111] Connection refused
ANY SUGGESTION?
Revision history for this message
|
#9 |
Klaudia,
I think that the problem is because you have all your services running on: 127.0.0.1
When you run commands from controller, everything is working because all calls are local but when running from a different node is still trying to reach:
REQ: curl -i http://
When you set up your controller, use the IP address that is reachable between your nodes.
Revision history for this message
|
#10 |
Edgar,
Thank you for your reply. It can be this problem , as you noticed.
I'm trying to find the files that contain the phrase '127 .0.0.1 ' , and can be conneted with quantum problems. well...
there are many files containing 127.0.0.1 (grep 127.0.0.1 -r /) , but which one could be this, where I have to do exnage 127.0.0.1 on controller addres?
I tryided to find this in quantum catalog: grep 127.0.0.1 -r /etc/quantum/ ,
but there are not '127.0.0.1' phrase there.
I find for example that in patch: /usr/lib/
def metadata_
rules = []
return rules
But I do not know if I change the code in this place or elsewhere, and how to restart it later. I could ask for help from a file where I find the files where you need to replace the phrase 127.0.0.1 to another address, the address of the Controller?
Revision history for this message
|
#11 |
Klaudia,
when you set up your controller with whatever method(s) you are using, you need to make sure the
keystone endpoints are using the reachable ip address. If this was an automated setup, then search
through the config files for that automation. If it was manual, then you probably actually typed 127.0.0.1
for the address to "keystone endpoint-create ..."
my first setup was manual according to this guide:
https:/
that guide provided me with a script that created the endpoints:
https:/
you can manually delete and remake your endpoints
"keystone endpoint-delete ..." then "keystone endpoint-create ..."
good luck.
JamO
Revision history for this message
|
#12 |
Kaludia,
James already gave you some details about the keystone configuration. For all the services nova.conf should be also pointing to the right IP address:
/etc/nova/
Look for all the config files under:
/etc/nova
/etc/quantum
/etc/ ..
Good Luck!
Edgar
Revision history for this message
|
#13 |
I see this was asked a month ago. Did you resolve the problem?
What do you see for
$ cat /etc/quantum/
$ tail /var/log/
Can you help with this problem?
Provide an answer of your own, or ask Klaudia for more information if necessary.