[Openstack] Trouble launching my first OpenStack image

Kiran Kumar kirankumarkuvvarapu at gmail.com
Fri May 30 18:04:39 UTC 2014


All services should be run, and u will get the output like this

root at openstackdemo:/home/cloudenabler/Downloads# nova service-list
+------------------+---------------+----------+---------+-------+----------------------------+-----------------+
| Binary           | Host          | Zone     | Status  | State |
Updated_at                 | Disabled Reason |
+------------------+---------------+----------+---------+-------+----------------------------+-----------------+
| nova-consoleauth | openstackdemo | internal | enabled | up    |
2014-05-30T18:02:44.000000 | None            |
| nova-conductor   | openstackdemo | internal | enabled | up    |
2014-05-30T18:02:40.000000 | None            |
| nova-compute     | openstackdemo | nova     | enabled | up    |
2014-05-30T18:02:40.000000 | None            |
| nova-cert        | openstackdemo | internal | enabled | up    |
2014-05-30T18:02:44.000000 | None            |
| nova-scheduler   | openstackdemo | internal | enabled | up    |
2014-05-30T18:02:44.000000 | None            |
+------------------+---------------+----------+---------+-------+----------------------------+-----------------+

Check all the nova services(conductor,compute,scheduler) log


On Fri, May 30, 2014 at 11:20 PM, Ben Tomasini <ben.tomasini at gmail.com>
wrote:

> agent-list (redacted)
>
> stack at cmsdev01:~/git/devstack$ nova --os-username nova --os-tenant-name
> service --os-auth-url http://10.220.159.182:35357/v2.0/ --os-password
> ******** agent-list
> +----------+------------+----+--------------+---------+---------+-----+
> | Agent_id | Hypervisor | OS | Architecture | Version | Md5hash | Url |
> +----------+------------+----+--------------+---------+---------+-----+
> +----------+------------+----+--------------+---------+---------+-----+
>
>
> nova.conf (redacted):
>
> [DEFAULT]
> flat_interface = em0
> flat_network_bridge = br100
> vlan_interface = eth0
> public_interface = br100
> network_manager = nova.network.manager.FlatDHCPManager
> firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
> compute_driver = libvirt.LibvirtDriver
> default_ephemeral_format = ext4
> glance_api_servers = 10.220.159.182:9292
> rabbit_password = ********
> rabbit_hosts = 10.220.159.182
> rpc_backend = nova.openstack.common.rpc.impl_kombu
> ec2_dmz_host = 10.220.159.182
> vncserver_proxyclient_address = 127.0.0.1
> vncserver_listen = 127.0.0.1
> vnc_enabled = true
> xvpvncproxy_base_url = http://10.220.159.182:6081/console
> novncproxy_base_url = http://10.220.159.182:6080/vnc_auto.html
> logging_exception_prefix = %(color)s%(asctime)s.%(msecs)03d TRACE %(name)s
> %(instance)s
> logging_debug_format_suffix = from (pid=%(process)d) %(funcName)s
> %(pathname)s:%(lineno)d
> logging_default_format_string = %(asctime)s.%(msecs)03d
> %(color)s%(levelname)s %(name)s [-%(color)s]
> %(instance)s%(color)s%(message)s
> logging_context_format_string = %(asctime)s.%(msecs)03d
> %(color)s%(levelname)s %(name)s [%(request_id)s %(user_name)s
> %(project_name)s%(color)s] %(instance)s%(color)s%(message)s
> force_config_drive = always
> instances_path = /opt/stack/data/nova/instances
> lock_path = /opt/stack/data/nova
> state_path = /opt/stack/data/nova
> enabled_apis = ec2,osapi_compute,metadata
> instance_name_template = instance-%08x
> sql_connection = mysql://root:********@127.0.0.1/nova?charset=utf8
> metadata_workers = 4
> ec2_workers = 4
> osapi_compute_workers = 4
> my_ip = 10.220.159.182
> s3_port = 3333
> s3_host = 10.220.159.182
> default_floating_pool = public
> fixed_range =
> force_dhcp_release = True
> dhcpbridge_flagfile = /etc/nova/nova.conf
> scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
> rootwrap_config = /etc/nova/rootwrap.conf
> api_paste_config = /etc/nova/api-paste.ini
> allow_resize_to_same_host = True
> auth_strategy = keystone
> debug = True
> verbose = True
>
> [conductor]
> workers = 4
>
> [osapi_v3]
> enabled = True
>
> [keystone_authtoken]
> signing_dir = /var/cache/nova
> admin_password = ********
> admin_user = nova
> cafile =
> admin_tenant_name = service
> auth_protocol = http
> auth_port = 35357
> auth_host = 10.220.159.182
>
> [spice]
> enabled = false
> html5proxy_base_url = http://10.220.159.182:6082/spice_auto.html
>
> [libvirt]
> inject_partition = -2
> use_usb_tablet = False
> cpu_mode = none
> virt_type = kvm
>
> [keymgr]
> fixed_key = ******
>
>
>
> On Fri, May 30, 2014 at 10:29 AM, Kiran Kumar <
> kirankumarkuvvarapu at gmail.com> wrote:
>
>> output of "#nova agent-list" and also "nova.conf" file to debug.
>>
>>
>> On Fri, May 30, 2014 at 10:53 PM, Ben Tomasini <ben.tomasini at gmail.com>
>> wrote:
>>
>>> Here is the output of /var/log/nova/nova-scheduler.log.  It doesn't look
>>> like there are any entries from today.  This is the entire content of the
>>> file:
>>>
>>> 2014-05-29 06:51:02.618 10956 INFO nova.openstack.common.periodic_task
>>> [-] Skipping periodic task _periodic_update_dns because its interval is
>>> negative
>>> 2014-05-29 06:51:02.657 10956 AUDIT nova.service [-] Starting scheduler
>>> node (version 2014.1)
>>> 2014-05-29 06:51:03.091 10956 INFO oslo.messaging._drivers.impl_rabbit
>>> [-] Connected to AMQP server on localhost:5672
>>> 2014-05-29 14:00:55.438 10956 INFO nova.openstack.common.service [-]
>>> Caught SIGTERM, exiting
>>>
>>> The nova-scheduler appears to be running:
>>>
>>> stack     2940  0.2  0.1 267080 77788 pts/12   S+   09:09   0:09  |
>>>   \_ /usr/bin/python /usr/local/bin/nova-scheduler --config-file
>>> /etc/nova/nova.conf
>>>
>>> Ben
>>>
>>>
>>> On Fri, May 30, 2014 at 10:04 AM, Kiran Kumar <
>>> kirankumarkuvvarapu at gmail.com> wrote:
>>>
>>>> Hi Ben,
>>>> check (or) post the output of  "# tail /var/log/nova/nova-scheduler.log
>>>> ".
>>>>
>>>> Kiran
>>>>
>>>>
>>>> On Fri, May 30, 2014 at 10:17 PM, Ben Tomasini <ben.tomasini at gmail.com>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I just finished installing OpenStack on Ubuntu 14.04 using the
>>>>> Devstack script and tried to launch my first instance using a Centos 6.4
>>>>> image which I uploaded from here:
>>>>>
>>>>>
>>>>> http://dev.centos.org/centos/hvm/CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2
>>>>>
>>>>> The status of the instance alternated between scheduled(or ing) and
>>>>> spawning.  In addition, the list of internal IP addresses assigned to the
>>>>> instance started at 6 and grew to over 40.  The instance never started.
>>>>>  When I tried to terminate it, I was unable as it was in an "error" state.
>>>>>
>>>>> What steps should I take to troubleshoot this?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Ben
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list:
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>> Post to     : openstack at lists.openstack.org
>>>>> Unsubscribe :
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140530/0c9aacc7/attachment.html>


More information about the Openstack mailing list