openstack-nova-network dead but pid file exists (Grizzly on centos 6.4) [closed]
Hi Friends
I am using Grizzly Version on CENTOS 6.3. When I am trying to start openstack-nova-network service on Cloud Controller Node but it gives me error "openstack-nova-network dead but pid file exists". In between, i had stop the iptables services and selinux to off. For more information email me vicky_3k2000@yahoo.com . Here I am paste my contents of nova.conf file and logs of /var/log/nova/network.log
nova.conf
[DEFAULT] verbose=True logdir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp rootwrap_config = /etc/nova/rootwrap.conf
#SCHEDULER compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
#VOLUMES volume_api_class=nova.volume.cinder.API volume_driver=nova.volume.driver.ISCSIDriver volume_group=cinder-volumes volume_name_template=volume-%s iscsi_helper=tgtadm volumes_dir = /etc/nova/volumes
DATABASE
sql_connection = mysql://nova:nova@192.168.1.130/nova
COMPUTE
compute_driver=libvirt.LibvirtDriver libvirt_type=kvm instance_name_template=instance-%08x api_paste_config=/etc/nova/api-paste.ini libvirt_nonblocking = True libvirt_inject_partition = -1 libvirt_cpu_mode=host-model
COMPUTE/APIS: i you have separate configs for separate services
this lag is required for both nova-api and nova-compute
allow_resize_to_same_host=True
APIS
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions ec2_dmz_host=192.168.1.130 s3_host=192.168.1.130 enabled_apis=ec2,osapi_compute,metadata
QPID
qpid_hostname=192.168.1.130 rpc_backend=nova.openstack.common.rpc.impl_qpid
GLANCE
image_service=nova.image.glance.GlanceImageService glance_api_servers=192.168.1.130:9292
NETWORK
network_manager = nova.network.manager.FlatDHCPManager force_dhcp_release = True dhcpbridge_flagfile = /etc/nova/nova.conf firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
Change my_ip to match each host
my_ip=192.168.1.130 public_interace=eth1 vlan_interace=eth1 flat_interface=eth1 flat_network_bridge=br100 fixed_range=192.168.100.0/24
NOVNC CONSOLE
novncproxy_base_url=http://192.168.1.130:6080/vnc_auto.html
Change vncserver_proxyclient_address and vncserver_listen to match each compute host
vncserver_proxyclient_address=192.168.1.130 vncserver_listen=192.168.1.130
AUTHENTICATION
auth_strategy=keystone
[keystone_authtoken] auth_host=127.0.0.1 auth_port=35357 auth_protocol=http admin_tenant_name=service admin_user=nova admin_password=nova signing_dirname=/tmp/keystone-signing-nova
dhcpbridge = /usr/bin/nova-dhcpbridge #injected_network_template = /usr/share/nova/interfaces.template
/var/log/nova/Network.log
2013-08-23 12:10:16 17230 TRACE nova Command: sudo nova-rootwrap /etc/nova/rootwrap.conf FLAGFILE=/etc/nova/nova.conf NETWORK_ID=1 dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=192.168.100.1 --except-interface=lo --dhcp-range=set:private,192.168.100.2,static,255.255.255.0,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/lib/python2.6/site-packages/bin/nova-dhcpbridge --leasefile-ro 2013-08-23 12:10:16 17230 TRACE nova Exit code: 11 2013-08-23 12:10:16 17230 TRACE nova Stdout: '' 2013-08-23 12:10:16 17230 TRACE nova Stderr: '2013-08-23 12:10:16 CRITICAL nova [req-213b0097-9e84-41fc-944e-0648567cfb47 None None] cannot import name BigInteger\n2013-08-23 12:10:16 17349 TRACE nova Traceback (most recent call last):\n2013-08-23 12:10:16 17349 TRACE nova File "/usr/lib/python2.6/site-packages/bin/nova-dhcpbridge", line 128, in <module>\n2013-08-23 12:10:16 17349 TRACE nova main()\n2013-08-23 12:10:16 17349 TRACE nova File "/usr/lib/python2.6/site-packages/bin/nova-dhcpbridge", line 122, in main ...