nova boot error

Asked by Cornel on 2012-12-18

I'm trying to boot an image with nova but i obtain an error

+--------------------------------------+------+--------+----------+
| ID | Name | Status | Networks |
+--------------------------------------+------+--------+----------+
| 2d4b8122-5bfd-43b2-9f23-dd286390fd42 | vm1 | ERROR | |
+--------------------------------------+------+--------+----------+

Seems something with network is not well... Why and what i have to do?
Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
2012-12-18
Last reply:
2012-12-20
Tom Fifield (fifieldt) said : #1

Hi,

Can you please provide your nova.conf and the interesting parts of the log files in /var/log/nova ?

Cornel (cornel-punga) said : #2

[DEFAULT]
verbose=True
auth_strategy=keystone
allow_resize_to_same_host=True
api_paste_config=/etc/nova/api-paste.ini
rootwrap_config=/etc/nova/rootwrap.conf
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
dhcpbridge_flagfile=/etc/nova/nova.conf
force_dhcp_release=True
fixed_range=10.0.0.0/24
s3_host=192.168.1.xxx
s3_port=3333
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
my_ip=192.168.1.xxx
sql_connection=mysql://root:mypassword@localhost/nova?charset=utf8
libvirt_type=qemu
libvirt_cpu_mode=none
instance_name_template=instance-%08x
enabled_apis=ec2,osapi_compute,metadata
volume_api_class=nova.volume.cinder.API
state_path=/opt/stack/data/nova
lock_path=/opt/stack/data/nova
instances_path=/opt/stack/data/nova/instances
logging_context_format_string=%(asctime)s %(color)s%(levelname)s %(name)s [^[[0$
logging_default_format_string=%(asctime)s %(color)s%(levelname)s %(name)s [^[[0$
logging_debug_format_suffix=^[[00;33mfrom (pid=%(process)d) %(funcName)s %(path$
logging_exception_prefix=%(color)s%(asctime)s TRACE %(name)s ^[[01;35m%(instanc$
network_manager=nova.network.manager.FlatDHCPManager
public_interface=br100
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0
novncproxy_base_url=http://192.168.1.xxx:6080/vnc_auto.html
xvpvncproxy_base_url=http://192.168.1.xxx:6081/console
vncserver_listen=127.0.0.1
vncserver_proxyclient_address=127.0.0.1
ec2_dmz_host=192.168.1.xxx
rabbit_host=localhost
rabbit_password=mypassword
glance_api_servers=192.168.1.xxx:9292
compute_driver=libvirt.LibvirtDriver
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver

ZhiQiang Fan (aji-zqfan) said : #3

shell>nova-manage service list
if nova-network's status is xxx instead of :)
shell>service nova-network status
if nova-network is stop/waiting, then follow the order:
1. check /var/log/nova/nova-scheduler.log to see any error or critical
2. check /var/log/nova/nova-network.log
3. check /var/log/nova/nova-compute.log
note that, since you're long time without any action, information will roll to log.1 .2 .3 etc
you can try to lunch a new instance, when it fail, check the log immidiately, and paste any error or critical info to us

thanks

Can you help with this problem?

Provide an answer of your own, or ask Cornel for more information if necessary.

To post a message you must log in.