Hi,
The default dnsmasq lease time of 2 mins flood my /var/log/messages file
with dhcp requests and acks, do you guys think that there is a good
reason for the default lease time to be so low? do you think we better
change the default to be a higher value?
--
Thanks,
Rami Vaknin, QE @ Red
You could just turn off notifications in glance but that isn't causing an
issue. So it seems pretty clear that your compute and network nodes are
listening properly on 05, 07, 08. Is it possible that your network got
configured as multi_host=False somehow? Or that you have multiple rabbits
runn
2012/12/10 Vishvananda Ishaya
> Check rabbitmqctl list_queues and see if there are queues that have
> nonzero entries. That means messages are being sent but not picked up by
> the nodes.
>
Here is the output of the command -- there some non zero values for glance
info. Is there any way to clear
Check rabbitmqctl list_queues and see if there are queues that have nonzero
entries. That means messages are being sent but not picked up by the nodes. If
the nova-networks are hanging they are probably stuck waiting on a lock files.
I believe the lock files are in /var/lock/nova by default. You
I don't see any errors in your network log. are nova-network and nova-compute
running on the same host with the same config file? It looks like it isn't
recieving a message. Are you running another nova-network that is picking up
the message on another host?
Vish
On Dec 10, 2012, at 12:18 PM,
Hey there, which version of dnsmasq are your running. This bug has been reported and fixed in the version 2.59-1 of dnsmasqRazique
Razique Mahroua - Nuage & Corazique.mahr...@gmail.com
Le 27 nov. 2012 à 08:25, "唐宏伟" <31438837@qq.com> a écrit :
Hi all,
I have setup an "all-in-one" op
Hi all,
I have setup an "all-in-one" openstack folsom on my server from source code. I use quantum as the network manager. When I start the quantum-dhcp-agent, the dnsmasq starts failed, and output the error message "dnsmasq: failed to bind listening socket for fe80::f816:
Hi all,
I have setup an "all-in-one" openstack folsom on my server from source code. I use quantum as the network manager. When I start the quantum-dhcp-agent, the dnsmasq starts failed, and output the error message "dnsmasq: failed to bind listening socket for fe80::f816:
On Mon, Oct 22, 2012 at 01:54:11PM +0200, Gary Kotton wrote:
> Can you please explain the problems that you had with qpid?
OpenStack components were periodically losing touch with each other.
Requests to boot/delete an instance, for example, would never make it
as far the compute hosts. They woul
On Fri, Oct 19, 2012 at 10:24:20AM -0400, Lars Kellogg-Stedman wrote:
> It happened again last night -- which means we were without networking
> on our instances for about seven hours -- and restarting nova-network
> doesn't resolve the problem. It is necessary to first kill dnsmasq
> (and allow n
On 10/18/2012 05:42 PM, Lars Kellogg-Stedman wrote:
The good news is that since replacing qpid with rabbitmq our
environment seems to have stabilized to the point that it's *almost*
useful.
Can you please explain the problems that you had with qpid?
The last remaining issue is that dnsmasq w
Hi Lars,
There are no errors being logged by dnsmasq; started just after 2AM,
> all of the "DHCPREQUEST ..." traffic just stops, and the logs after
> that point look like this:
>
We ran into similar issues that turned out to be a qemu bug:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/
I've noticed similar behavior where dnsmasq stops working if nova-network
is restarted without first killing all the dnsmasq processes.
On Oct 19, 2012 10:24 AM, "Lars Kellogg-Stedman"
wrote:
> On Thu, Oct 18, 2012 at 06:16:07PM +0100, Ronivon Costa wrote:
> >I have noticed a similar behaviou
On Thu, Oct 18, 2012 at 06:16:07PM +0100, Ronivon Costa wrote:
>I have noticed a similar behaviour, for example when the switch/router is
>rebooted. I am able to recover the communications with the VMs restarting
>nova network (no need to kill dnsmasq).
There are no network devices be
The good news is that since replacing qpid with rabbitmq our
environment seems to have stabilized to the point that it's *almost*
useful.
The last remaining issue is that dnsmasq will occasionally stop
responding to instances. Killing dnsmasq and restarting
openstack-nova-network makes things wor
This is correct.
Vish
On May 24, 2012, at 9:45 PM, William Herry wrote:
> Hi
>
> sorry for too much silly questions
>
> I am interested in the dnsmasq of nova when use FlatDHCP network mode
>
> I am guess it works like this:
> nova write MAC -> IP info to /var/lib/nova/networks/nova-br1.conf
Hi
sorry for too much silly questions
I am interested in the dnsmasq of nova when use FlatDHCP network mode
I am guess it works like this:
nova write MAC -> IP info to /var/lib/nova/networks/nova-br1.conf when boot
a instance
nova tell dnsmasq to reread /var/lib/nova/networks/nova-br1.conf
ins
On 03/17/2012 06:08 PM, Ghe Rivero wrote:
> Hi Thomas,
> you can use the flag:
> dhcpbridge=/usr/bin/nova-dhcpbridge
> in nova.conf.
>
> Ghe Rivero
Ok, I'll do that, thanks!
However, I really think that by default this should be corrected. I
feels really weird that nova is trying to search a
Hi Thomas,
you can use the flag:
dhcpbridge=/usr/bin/nova-dhcpbridge
in nova.conf.
Ghe Rivero
On 3/16/12, Thomas Goirand wrote:
> Hi,
>
> When running with the following nova.conf:
>
> --sql_connection=mysql://nova:admin@127.0.0.1/nova
> --novncproxy_base_url=http://:6080/vnc_auto.html
> --ra
Hi,
When running with the following nova.conf:
--sql_connection=mysql://nova:admin@127.0.0.1/nova
--novncproxy_base_url=http://:6080/vnc_auto.html
--rabbit_host=
--glance_api_servers=:9292
--network_manager=nova.network.manager.VlanManager
--connection_type=xenapi
--xenapi_connection_url=https://
20 matches
Mail list logo
