Re: [openstack-dev] Juno Multinode installation error
Hi,
recently I faced this issue.
upgrade amqp lib on all nodes and it should work.
Regards,
Yatin
On Tue, May 5, 2015 at 5:37 PM, Ajaya Agrawal ajku@gmail.com wrote:
Hi,
A better place to ask this question would be ask.openstack.org .
Cheers,
Ajaya
On Tue, May 5, 2015 at 4:56 PM, Abhishek Talwar abhishek.tal...@tcs.com
wrote:
Hi Folks,
I am trying to setup a multinode OpenStack. When I boot an instance it is
successfully created but it is going in ERROR state. I have checked the
logs in /var/log/nova/nova-scheduler.log and it gives an Operational error
“database is locked”. Moreover when I check the database there are no
tables getting created in the Nova database, while Neutron and others have
there tables.
The logs are following :
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
OperationalError: (OperationalError) database is locked u'UPDATE
reservations SET deleted_at=?, deleted=id, updated_at=updated_at WHERE
reservations.deleted = ? AND reservations.expire ?' ('2015-05-05
09:05:13.150105', 0, '2015-05-05 09:05:13.138314')
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
2015-05-05 14:37:47.972 18551 INFO oslo.messaging._drivers.impl_rabbit
[-] Connecting to AMQP server on controller:5672
2015-05-05 14:37:47.991 18551 INFO oslo.messaging._drivers.impl_rabbit
[-] Connected to AMQP server on controller:5672
2015-05-05 15:10:59.535 18551 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:11:01.506 19260 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:11:03.691 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:11:03.747 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connected to AMQP server on
controller:5672
2015-05-05 15:21:55.601 19260 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:21:56.568 19542 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:21:57.504 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:21:57.514 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connected to AMQP server on
controller:5672
2015-05-05 15:32:39.316 19542 INFO oslo.messaging._drivers.impl_rabbit
[-] Connecting to AMQP server on controller:5672
2015-05-05 15:32:39.343 19542 INFO oslo.messaging._drivers.impl_rabbit
[-] Connected to AMQP server on controller:5672
2015-05-05 15:38:21.280 19542 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:38:22.434 19954 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:38:23.173 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:38:23.248 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connected to AMQP server on
controller:5672
2015-05-05 15:39:46.468 19954 INFO oslo.messaging._drivers.impl_rabbit
[-] Connecting to AMQP server on controller:5672
2015-05-05 15:39:46.484 19954 INFO oslo.messaging._drivers.impl_rabbit
[-] Connected to AMQP server on controller:5672
The configuration for nova.conf is :
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
scheduler_default_filters=AllHostsFilter
verbose = True
connection = mysql://nova:NOVA_DBPASS@controller/nova
rpc_backend = rabbit
rabbit_host = controller
rabbit_password = RABBIT_PASS
auth_strategy = keystone
my_ip = 10.10.10.10
vncserver_listen = 10.10.10.10
vncserver_proxyclient_address = 10.10.10.10
network_api_class = nova.network.neutronv2.api.API
security_group_api = neutron
linuxnet_interface_driver =
nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver = nova.virt.firewall.NoopFirewallDriver
[keystone_authtoken]
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS
[glance]
host = controller
[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = NEUTRON_PASS
The configuration for neutron is:
[DEFAULT]
verbose = True
lock_path = $state_path/lock
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True
auth_strategy =
Re: [openstack-dev] Juno Multinode installation error
Hi,
A better place to ask this question would be ask.openstack.org .
Cheers,
Ajaya
On Tue, May 5, 2015 at 4:56 PM, Abhishek Talwar abhishek.tal...@tcs.com
wrote:
Hi Folks,
I am trying to setup a multinode OpenStack. When I boot an instance it is
successfully created but it is going in ERROR state. I have checked the
logs in /var/log/nova/nova-scheduler.log and it gives an Operational error
“database is locked”. Moreover when I check the database there are no
tables getting created in the Nova database, while Neutron and others have
there tables.
The logs are following :
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
OperationalError: (OperationalError) database is locked u'UPDATE
reservations SET deleted_at=?, deleted=id, updated_at=updated_at WHERE
reservations.deleted = ? AND reservations.expire ?' ('2015-05-05
09:05:13.150105', 0, '2015-05-05 09:05:13.138314')
2015-05-05 14:35:13.158 18551 TRACE nova.openstack.common.periodic_task
2015-05-05 14:37:47.972 18551 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 14:37:47.991 18551 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
2015-05-05 15:10:59.535 18551 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:11:01.506 19260 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:11:03.691 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:11:03.747 19260 INFO oslo.messaging._drivers.impl_rabbit
[req-7b53c22a-2161-4f9f-9942-c39ad5b35ca0 ] Connected to AMQP server on
controller:5672
2015-05-05 15:21:55.601 19260 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:21:56.568 19542 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:21:57.504 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:21:57.514 19542 INFO oslo.messaging._drivers.impl_rabbit
[req-ee9a2d39-678d-48c2-b490-2894cb6370b5 ] Connected to AMQP server on
controller:5672
2015-05-05 15:32:39.316 19542 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 15:32:39.343 19542 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
2015-05-05 15:38:21.280 19542 INFO nova.openstack.common.service [-]
Caught SIGTERM, exiting
2015-05-05 15:38:22.434 19954 AUDIT nova.service [-] Starting scheduler
node (version 2014.2.2)
2015-05-05 15:38:23.173 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connecting to AMQP server on
controller:5672
2015-05-05 15:38:23.248 19954 INFO oslo.messaging._drivers.impl_rabbit
[req-b65ec7c6-6bbd-4e13-9694-da927c9cf337 ] Connected to AMQP server on
controller:5672
2015-05-05 15:39:46.468 19954 INFO oslo.messaging._drivers.impl_rabbit [-]
Connecting to AMQP server on controller:5672
2015-05-05 15:39:46.484 19954 INFO oslo.messaging._drivers.impl_rabbit [-]
Connected to AMQP server on controller:5672
The configuration for nova.conf is :
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
scheduler_default_filters=AllHostsFilter
verbose = True
connection = mysql://nova:NOVA_DBPASS@controller/nova
rpc_backend = rabbit
rabbit_host = controller
rabbit_password = RABBIT_PASS
auth_strategy = keystone
my_ip = 10.10.10.10
vncserver_listen = 10.10.10.10
vncserver_proxyclient_address = 10.10.10.10
network_api_class = nova.network.neutronv2.api.API
security_group_api = neutron
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver = nova.virt.firewall.NoopFirewallDriver
[keystone_authtoken]
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS
[glance]
host = controller
[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = NEUTRON_PASS
The configuration for neutron is:
[DEFAULT]
verbose = True
lock_path = $state_path/lock
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True
auth_strategy = keystone
# Driver to use for scheduling a loadbalancer pool to an lbaas agent
# loadbalancer_pool_scheduler_driver =
neutron.services.loadbalancer.agent_scheduler.ChanceScheduler
