Ask Your Question
0

util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [timed out]

asked 2013-02-08 17:54:54 -0500

srikanth1239 gravatar image

Hello Everyone,

I have done with the dual node installation of openstack on centos 6.3 with Openstack FOLSOM. I am able to launch the instance from the dashboard, able to ping the instance using private ip and public is well.. But not able to SSH to the instance after checking the logs i came to know that there are some metadata errors in logs. Kindly check the below logs of the instances which are launched.


util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [timed out]

2013-02-08 17:30:02,466 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds

no instance data found in start

Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

  • Stopping Handle applying cloud-config[74G[ OK ]

  • Starting AppArmor profiles [80G [74G[ OK ]

landscape-client is not configured, please run landscape-config.

  • Stopping System V initialisation compatibility[74G[ OK ]

  • Starting System V runlevel compatibility[74G[ OK ]

  • Starting save kernel messages[74G[ OK ]

  • Stopping save kernel messages[74G[ OK ]

  • Starting ACPI daemon[74G[ OK ]

  • Starting regular background program processing daemon[74G[ OK ]

  • Starting deferred execution scheduler[74G[ OK ]

  • Starting automatic crash report generation[74G[ OK ]

  • Starting CPU interrupts balancing daemon[74G[ OK ]

  • Starting crash report submission daemon[74G[ OK ]

  • Stopping System V runlevel compatibility[74G[ OK ]

  • Starting execute cloud user/final scripts[74G[ OK ]


My controller nodes nova.conf looks like All services running except nova-compute & nova-metadata-api


[DEFAULT]

LOGS/STATE

debug = True

verbose = True

#[trusted_computing] server = <computenode ip="">

AUTHENTICATION

auth_strategy = keystone

SCHEDULER

compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler

scheduler_driver=nova.scheduler.simple.SimpleScheduler

VOLUMES

volume_group = nova-volumes

volume_name_template = volume-%08x

iscsi_helper = tgtadm root_helper = sudo

DATABASE

sql_connection = mysql://nova:<password>@<controllernode ip="">/nova

COMPUTE

compute_driver = libvirt.LibvirtDriver libvirt_type = kvm connection_type = libvirt instance_name_template = instance-%08x api_paste_config = /etc/nova/api-paste.ini allow_resize_to_same_host = True

APIS

osapi_compute_extension = nova.api.openstack.compute.contrib.standard_extensions ec2_dmz_host = <controllernode ip=""> s3_host = <controllernode ip="">

RABBITMQ

rabbit_host = <controllernode ip="">

GLANCE

image_service = nova.image.glance.GlanceImageService glance_api_servers = <controllernode ip="">:9292

logdir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp volumes_dir = /etc/nova/volumes dhcpbridge = /usr/bin/nova-dhcpbridge injected_network_template = /usr/share/nova/interfaces.template #libvirt_nonblocking = True #libvirt_inject_partition = -1 iscsi_helper = tgtadm

compute_driver = libvirt.LibvirtDriver

rpc_backend = nova.openstack.common.rpc.impl_qpid

rootwrap_config = /etc/nova/rootwrap.conf

NETWORK

network_manager = nova.network.manager.FlatDHCPManager force_dhcp_release = True dhcpbridge_flagfile = /etc/nova/nova.conf dhcpbridge = /usr/bin/nova-dhcpbridge firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver state_path = /var/lib/nova my_ip = <controllernode ip=""> public_interface = eth1 vlan_interface = eth0 flat_network_bridge = br100 flat_interface = eth0

routing_source_ip = 192.168.1.1

fixed_range = 192.168.100.0/24 multi_host = True enabled_apis = ec2,osapi_compute,osapi_volume,metadata send_arp_for_ha = True

[keystone_authtoken] admin_tenant_name = service admin_user = nova admin_password = <password> auth_host = <controllernode ip=""> auth_port = 35357 auth_protocol = http signing_dir = /tmp/keystone-signing-nova


my compute nodes nova.conf looks like Runs nova-compute & nova-network


[DEFAULT]

LOGS/STATE

debug = True

verbose = True

AUTHENTICATION

auth_strategy = keystone

SCHEDULER

compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler

scheduler_driver=nova.scheduler.simple.SimpleScheduler

VOLUMES

volume_group = nova-volumes

volume_name_template = volume-%08x

iscsi_helper = tgtadm root_helper = sudo

DATABASE

sql_connection = mysql://nova:<password>@<controllernode ip="">/nova

COMPUTE

compute_driver ...

(more)
edit retag flag offensive close merge delete

6 answers

Sort by ยป oldest newest most voted
0

answered 2013-02-09 02:08:04 -0500

zzs gravatar image

Since you can ping the instance, not so sure if it is the problem of the meta data. Can you upload the log of the instance booting from dashboard and the ssh log. Can you log in to the instance by VNC from dashboard.

Regarding the meta data, please check http://docs.openstack.org/folsom/openstack-compute/admin/content/metadata-service.html (http://docs.openstack.org/folsom/open...)

edit flag offensive delete link more
0

answered 2013-02-12 13:36:24 -0500

srikanth1239 gravatar image

Hi Jason Zhang (zzs),

Thanks for your interest on helping me with this.

  1. Yes, i can ping my instance after launching from dashboard.

  2. Kindly check the log of the instance which launching.


[ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.2.0-37-virtual (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #58-Ubuntu SMP Thu Jan 24 15:48:03 UTC 2013 (Ubuntu 3.2.0-37.58-virtual 3.2.35) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-virtual root=LABEL=cloudimg-rootfs ro console=ttyS0 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] Disabled fast string operations [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009dc00 (usable) [ 0.000000] BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 000000003fffd000 (usable) [ 0.000000] BIOS-e820: 000000003fffd000 - 0000000040000000 (reserved) [ 0.000000] BIOS-e820: 00000000fffbc000 - 0000000100000000 (reserved) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.4 present. [ 0.000000] No AGP bridge found [ 0.000000] last_pfn = 0x3fffd max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x70106, new 0x7010600070106 [ 0.000000] found SMP MP-table at [ffff8800000fda70] fda70 [ 0.000000] init_memory_mapping: 0000000000000000-000000003fffd000 [ 0.000000] RAMDISK: 3776c000 - 37bae000 [ 0.000000] ACPI: RSDP 00000000000fda20 00014 (v00 BOCHS ) [ 0.000000] ACPI: RSDT 000000003fffd740 00030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) [ 0.000000] ACPI: FACP 000000003ffffe40 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) [ 0.000000] ACPI: DSDT 000000003fffd900 024FD (v01 BXPC BXDSDT 00000001 INTL 20090123) [ 0.000000] ACPI: FACS 000000003ffffe00 00040 [ 0.000000] ACPI: SSDT 000000003fffd860 0009E (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) [ 0.000000] ACPI: APIC 000000003fffd770 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-000000003fffd000 [ 0.000000] Initmem setup node 0 0000000000000000-000000003fffd000 [ 0.000000] NODE_DATA [000000003fff8000 - 000000003fffcfff] [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000000] kvm-clock: cpu 0, msr 0:1cf7681, boot clock [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal empty [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0x00000010 -> 0x0000009d [ 0.000000] 0: 0x00000100 -> 0x0003fffd [ 0.000000] ACPI: PM-Timer IO Port: 0xb008 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 000000000009d000 - 000000000009e000 [ 0.000000 ...

(more)
edit flag offensive delete link more
0

answered 2013-02-14 00:07:21 -0500

zzs gravatar image

Did you create the key pair before launching VM, what did you mean ' i was trying to attach while launching'

edit flag offensive delete link more
0

answered 2013-02-14 00:08:23 -0500

zzs gravatar image

What is the log output of the ssh to VM.

edit flag offensive delete link more
0

answered 2013-02-14 18:45:23 -0500

zzs gravatar image

please check the process of ssh. http://docs.openstack.org/trunk/openstack-compute/admin/content/booting-a-test-image.html (http://docs.openstack.org/trunk/opens...)

edit flag offensive delete link more
0

answered 2013-02-15 08:39:11 -0500

srikanth1239 gravatar image

Hi,

I have created a Keypair, LOG: when i try to SSH for the instance with the key attached it simply rejects and asks for the password.

I launched the instance from command line, it is launched but not able to ssh with the key.

Regards Srikanth. M

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

1 follower

Stats

Asked: 2013-02-08 17:54:54 -0500

Seen: 424 times

Last updated: Feb 15 '13