In the dnsmasq.conf file I have
listen-address=127.0.0.1
listen-address=192.168.1.250
Where 192.168.1.250 is the virtual IP.
Otherwise, I think it will listen on all interfaces.
On 3/24/2012 7:22 PM, Alan Robertson wrote:
Or if there's a way to get your dnsmasq server to bind to a specific
IP
Or if there's a way to get your dnsmasq server to bind to a specific IP
address, that's an even better solution.
On 3/23/2012 8:27 PM, Trevor Hemsley wrote:
I'd guess that your replies are going back with the wrong source IP
address on them and the Windows clients are being picky about accepti
Hello
I think this constrains it's wrong
==
colocation c_drbd_libvirt_vm inf: ms_drbd_vmstore:Master
ms_drbd_mount1:Master ms_drbd_mount2:Master g_vm
==
it must be like this
==
colocation
Thank you for the responses.
It turned out to be pilot error. I had a virtual machine that was
running dnsmasq on the same IP address that was not part of the cluster.
I had entered poweroff at the command line and then started bringing up
the new DNS server. It turns out that the old server w
Shutdown pacemaker and fix your drbd disk first. Get them both
uptodate/uptodate and make sure you can manually switch them to primary
on each node.
Node2 can't become primary when it's not connected to something with an
uptodate disk.
On 3/24/12 3:15 PM, Andrew Martin wrote:
Hi Andreas,
M
Hello,
I have configured a KVM virtual machine primitive using Pacemaker 1.1.6 and
Heartbeat 3.0.5 on Ubuntu 10.04 Server using DRBD as the storage device (so
there is no shared storage, no live-migration):
primitive p_vm ocf:heartbeat:VirtualDomain \
params config="/vmstore/config/vm.xml"
Hi Andreas,
My complete cluster configuration is as follows:
Last updated: Sat Mar 24 13:51:55 2012
Last change: Sat Mar 24 13:41:55 2012
Stack: Heartbeat
Current DC: node2 (9100538b-7a1f-41fd-9c1a-c6b4b1c32b18) - partition with
quorum
Version: 1.1.6-9971ebba4494012a93c03b40
> Hi everyone,
>
> for those interested in contributing to a community documentation
> project focusing on performance optimization in high availability
> clusters, please take a look at the following URLs:
>
> https://github.com/fghaas/hp-ha-guide (GitHub repo)
> http://www.hastexo.com/node/173
