openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #21385
Re: metadata server not responding
Hi Sylvain
Thanks a lot for your quick response. I checked tcpdump and there is no
trace of request
tcpdump -nn -i br100 2>&1 |tee br100
tcpdump -nn -i em2 2>&1 |tee em2
I tried curl from different session during tcpdump.
ip add
lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet 169.254.169.254/32 scope link lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:22:19:6a:bc:09 brd ff:ff:ff:ff:ff:ff
inet 163.1.5.40/24 brd 163.1.5.255 scope global em1
inet6 fe80::222:19ff:fe6a:bc09/64 scope link
valid_lft forever preferred_lft forever
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:22:19:6a:bc:0b brd ff:ff:ff:ff:ff:ff
inet6 fe80::222:19ff:fe6a:bc0b/64 scope link
valid_lft forever preferred_lft forever
4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:22:19:6a:bc:0d brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:22:19:6a:bc:0f brd ff:ff:ff:ff:ff:ff
6: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 52:54:00:80:b8:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
link/ether 52:54:00:80:b8:51 brd ff:ff:ff:ff:ff:ff
9: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 00:22:19:6a:bc:0b brd ff:ff:ff:ff:ff:ff
inet 192.168.9.3/24 brd 192.168.9.255 scope global br100
inet6 fe80::9c69:63ff:fef2:698a/64 scope link
valid_lft forever preferred_lft forever
14: vnet4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 500
link/ether fe:16:3e:5f:20:d1 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe5f:20d1/64 scope link
valid_lft forever preferred_lft forever
One vm is running on compute node and I can ssh into it.
Thanks
Kashif
On Thu, Feb 28, 2013 at 4:36 PM, Sylvain Bauza
<sylvain.bauza@xxxxxxxxxxxx>wrote:
> Metadata can be fetched from http://169.254.169.254:80/latest/metadata
> Could you please tcpdump -nn -i <your bridge intf.> on your node running
> nova-network and check if you see request coming in ?
>
> -Sylvain
>
>
>
> Le 28/02/2013 17:29, mohammad kashif a écrit :
>
> Hi
>
> I have installed openstack on two node setup with rhel6.4. I am using
> nova-network with multi_host=True. Everything is running on controller node
> and second node is running nova-compute, nova-network and
> nova-api-metadata. I can create vm's and it is getting ip address but metadata
> server is not responding. I can see that it is running
>
> lsof -i:8775
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> nova-api- 8009 nova 4u IPv4 28815 0t0 TCP *:8775 (LISTEN)
>
> curl http://169.254.169.254:8775
>
> <html>
> <head>
> <title>404 Not Found</title>
> </head>
> <body>
> <h1>404 Not Found</h1>
> The resource could not be found.<br /><br />
> </body>
>
> in metadata log file
>
> 8009 ERROR nova.api.metadata.handler [-] Failed to get metadata for ip:
> 169.254.169.254
>
> iptable looking ok to me (I dont have much experience with iptable)
>
> DNAT tcp -- anywhere 169.254.169.254 tcp dpt:http
> to:192.168.9.3:8775
>
> 192.168.9.3 is the address of compute node.
>
> Can some one suggest something please.
>
> Thanks
>
> Kashif
>
>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
References
