Openstack/Devstack: console "Error code explanation: 404 = Nothing matches the given URI"

czezz · 05-10-2019, 11:05 AM

I have just started new test instance.
I am trying to access this VM via console from Horizon but surprisingly it gives me an error:

Code:

Error response

Error code 404.

Message: File not found.

Error code explanation: 404 = Nothing matches the given URI.

I checked the console log (fill output attached) and VM seems to be started OK.
openstack console log show testvm1

Code:

=== datasource: ec2 net ===
instance-id: i-00000003
name: N/A
availability-zone: nova
local-hostname: testvm1.novalocal
launch-index: 0
=== cirros: current=0.4.0 uptime=38.61 ===
  ____               ____  ____
 / __/ __ ____ ____ / __ \/ __/
/ /__ / // __// __// /_/ /\ \
\___//_//_/  /_/   \____/___/
   http://cirros-cloud.net


login as 'cirros' user. default password: 'gocubsgo'. use 'sudo' for root.
testvm1 login:

Any clue what might be wrong?

EDIT:
Added prefix to the topis "Openstack/Devstack"

berndbausch · 05-10-2019, 10:38 PM

Not everybody at Linuxquestions understands that you are talking about OpenStack. My recommendation: Add a little more context.

You should find details about the failure in the Apache and/or Horizon logs. You can also generate a console URL on the command line:

Code:

openstack console url show testvm1

then enter this URL in your browser.

If this error occurs for all instances, I guess the cloud is misconfigured.

James Baldwin · 10-12-2019, 02:40 AM

Hi,bro.
Do you resolve this problem.I meet the same problem.Maybe you can help me .

berndbausch · 10-12-2019, 04:13 AM

Quote:

Originally Posted by James Baldwin

Hi,bro.
Do you resolve this problem.I meet the same problem.Maybe you can help me .

What do you find in the Apache and/or Horizon logs?
Have you tried to generate a URL manually and enter it in the browser?

James Baldwin · 10-12-2019, 04:34 AM

Quote:

Originally Posted by berndbausch

What do you find in the Apache and/or Horizon logs?
Have you tried to generate a URL manually and enter it in the browser?

I'm so sorry that i'm a new one in openstack.Can you tell me more detials .Thanks.

berndbausch · 10-12-2019, 07:26 AM

The log files' location depends on the distro and the OpenStack deployment method. I believe that the Apche and Horizon logs are under /var/log/httpd or /var/log/apache2 in most cases. Look for error messages around the time the problem occurs.

As to generating the URL, use the command in https://www.linuxquestions.org/quest...7/#post5993860. It will issue a URL that you can paste into the browser's address bar to obtain a console.

Does you error occur once, occasionally or always?

James Baldwin · 10-12-2019, 10:04 PM

It's my first time to run instance.I am consideringabout whether it is my network configuration problem.When i see the network (dashboard) ,i see the 172.244.xxx(but i set eth0 192.168.99.2.xx ) error.txt thanks.

berndbausch · 10-13-2019, 12:13 AM

The last line from the log file

Code:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message

indicates that your configuration contains 127.0.0.1 somewhere. I don't think that is a good thing. It should be 192.168.99.2 instead.

I don't know which network you see in the console, but as a general rule, virtual networks have different IP address ranges than the infrastructure on which the cloud runs.

James Baldwin · 10-13-2019, 12:28 AM

Quote:

Originally Posted by berndbausch

The last line from the log file

Code:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message

indicates that your configuration contains 127.0.0.1 somewhere. I don't think that is a good thing. It should be 192.168.99.2 instead.

I don't know which network you see in the console, but as a general rule, virtual networks have different IP address ranges than the infrastructure on which the cloud runs.

1) network
127.0.0.1is lo.But i don't know where it is defined.
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 24828552 bytes 12131467440 (12.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 24828552 bytes 12131467440 (12.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

the complet network is there:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.99.208 netmask 255.255.0.0 broadcast 192.168.255.255
inet6 fe80::46a8:42ff:fe49:8ed0 prefixlen 64 scopeid 0x20<link>
ether 44:a8:42:49:8e:d0 txqueuelen 1000 (Ethernet)
RX packets 3695664 bytes 1346943148 (1.3 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3408612 bytes 1048432405 (1.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 36

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 77.77.77.208 netmask 255.255.255.0 broadcast 77.77.77.255
inet6 fe80::46a8:42ff:fe49:8ed1 prefixlen 64 scopeid 0x20<link>
ether 44:a8:42:49:8e:d1 txqueuelen 1000 (Ethernet)
RX packets 394408 bytes 115708055 (115.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 122 bytes 9164 (9.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 39

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 24870041 bytes 12150367068 (12.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 24870041 bytes 12150367068 (12.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tape9dd03c1-5f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc16:3eff:fe10:c71f prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:10:c7:1f txqueuelen 1000 (Ethernet)
RX packets 95305 bytes 9200186 (9.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 164941 bytes 14723026 (14.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vxlan_sys_4789: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 65000
inet6 fe80::e075:7cff:fe54:4c8f prefixlen 64 scopeid 0x20<link>
ether e2:75:7c:54:4c:8f txqueuelen 1000 (Ethernet)
RX packets 123 bytes 7706 (7.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 34997 bytes 3575978 (3.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

2)local.conf

i modify the control-local.txt.control-local.txt
i don't modify the other thing and run FORCE=yes ./stack.sh in 192.168.99.208
i use the the compute-local.txt.compute-local.txt
i don't modify the other thing and run FORCE=yes ./stack.sh in 192.168.99.203
3) the version of ubuntu
ubuntu server is 18.04 .

berndbausch · 10-13-2019, 02:58 AM

Why do you use non-standard Git repos? Try again after removing the lines containing trystack.cn.

Also, I would have expected a bridge somewhere in your network interface list. Perhaps ifconfig is unable to list it? Don't use ifconfig; use ip address instead.

James Baldwin · 10-13-2019, 11:17 AM

Quote:

Originally Posted by berndbausch

Why do you use non-standard Git repos? Try again after removing the lines containing trystack.cn.

Also, I would have expected a bridge somewhere in your network interface list. Perhaps ifconfig is unable to list it? Don't use ifconfig; use ip address instead.

If I delete the lines containing trystack.cn , then what should I use instead of it?

berndbausch · 10-13-2019, 07:13 PM

I understand now that you set up a cloud with two hosts, one controller and one compute node. There is a guide for this: https://docs.openstack.org/devstack/...inode-lab.html.

To avoid problems with incompatible software left behind, please reinstall both hosts before applying the guide. Don't replace the trystack.cn lines in the local.conf files; just delete them.

One more suggestion: When you clone Devstack, you get the absolutely newest, leading-edge version of all it components. You may be better off cloning a stable version like Stein:

Code:

git clone https://opendev.org/openstack/devstack -b stable/stein

If you still have problems after using the official repos, at least we know that it has nothing to do with incorrect software.

James Baldwin · 10-14-2019, 02:43 AM

Quote:

Originally Posted by berndbausch

I understand now that you set up a cloud with two hosts, one controller and one compute node. There is a guide for this: https://docs.openstack.org/devstack/...inode-lab.html.

To avoid problems with incompatible software left behind, please reinstall both hosts before applying the guide. Don't replace the trystack.cn lines in the local.conf files; just delete them.

One more suggestion: When you clone Devstack, you get the absolutely newest, leading-edge version of all it components. You may be better off cloning a stable version like Stein:

Code:

git clone https://opendev.org/openstack/devstack -b stable/stein

If you still have problems after using the official repos, at least we know that it has nothing to do with incorrect software.

Thank you, I will follow your suggestions for installation.
1) Is it the problem that I installed the compute node at the control node? It is also the same compute-local.conf
2) If I follow the tutorial on the official website to install and debug, how to set up the network to calculate the node, whether to set an internal communication address or how to set it.

berndbausch · 10-14-2019, 03:23 AM

Quote:

Originally Posted by James Baldwin

1) Is it the problem that I installed the compute node at the control node? It is also the same compute-local.conf

You mean you have a single node and ran stack.sh twice with different local.conf files? Yes, that's a problem. The result is pretty much unpredictable.

Quote:

2) If I follow the tutorial on the official website to install and debug, how to set up the network to calculate the node, whether to set an internal communication address or how to set it.

First, the instructions I gave you are for a multi-node setup. If you want a single-node setup, they are not for you. Just follow the default instructions on http://docs.openstack.org/devstack.

However I don't understand what you are trying to achieve. You seem to have a question about network setup.
What do you mean by "calculate the node"?

James Baldwin · 10-14-2019, 04:07 AM

Quote:

Originally Posted by berndbausch

You mean you have a single node and ran stack.sh twice with different local.conf files? Yes, that's a problem. The result is pretty much unpredictable.

First, the instructions I gave you are for a multi-node setup. If you want a single-node setup, they are not for you. Just follow the default instructions on http://docs.openstack.org/devstack.

However I don't understand what you are trying to achieve. You seem to have a question about network setup.
What do you mean by "calculate the node"?

Sorry.maybe i don't make it clean."caculate the node"means the compute node.
Now,i will make an introduce.
I have three server.I want to use one (A)of them to make a control node.The left two (B、C)are the compute node.
after i use the control-local.txt to install the control node on A.I also use the compute-local.txt to install the compute node on the same server(A).
The left two (B、C）use the compute-local.txt to install the compute node.
But when i open the control-node's dashboard.I can only launch the instance on node A.The instances on node B and C show:Error code 404.