Ask Your Question
0

Getting wget: server returned error: HTTP/1.1 500 Internal Server Error

asked 2013-04-24 17:04:54 -0500

mrCloud gravatar image

Hi I have a 2 node Openstack setup,

Node1: Running controller Ubuntu 12.04 Node2: Running Nova Computer and Quantum Ubuntu 12.04 with KVM

I followed this guide: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst (https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVSMultiNode/OpenStackGrizzlyInstallGuide.rst)

I am running grizzly release

I got everything working except when I power on VM, I am getting the following error: Starting dropbear sshd: OK ===== cloudfinal: system completely up in 40.16 seconds ==== wget: server returned error: HTTP/1.1 500 Internal Server Error wget: server returned error: HTTP/1.1 500 Internal Server Error wget: server returned error: HTTP/1.1 500 Internal Server Error instanceid: publicipv4: localipv4 : wget: server returned error: HTTP/1.1 500 Internal Server Error clouduserdata: failed to read instance id WARN: /etc/rc3.d/S99clouduserdata failed

Can any of you please ponnt me to a place where I can investigate this further? Thanks

edit retag flag offensive close merge delete

Comments

If it helps the VM is getting IP from DHCP Server fine just having issue getting metadata from metadata server: Lease of 50.50.1.4 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 50.50.1.2 cloudsetup: checking http://169.254.169.254/20090404/metadata/instanceid

mrCloud gravatar imagemrCloud ( 2013-04-24 17:07:34 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2013-05-15 04:45:52 -0500

fifieldt gravatar image

updated 2013-05-15 04:46:13 -0500

Hi,

It looks OpenStack is working correctly here to boot the VM, except getting through to the metadata server.

Can you share your /etc/quantum/metadata_agent.ini, ensure the metadata service is running, and make sure your firewall appears setup to allow access to the metadata server on the 169.254.169.254 IP address?

edit flag offensive delete link more
0

answered 2013-05-20 16:18:57 -0500

updated 2013-05-20 16:21:46 -0500

I'm guessing the issue is because on the nova-api side you are missing the following setting in your nova.conf

service_quantum_metadata_proxy = True

The log message from the metadata agent would give more insight though.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2013-04-24 17:04:54 -0500

Seen: 2,364 times

Last updated: May 20 '13