Re: Some problems with fence_virt.conf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Is "prodif" really the interface name?
I'd have expected something like "virbr0"

On Sat, Nov 3, 2012 at 10:49 PM, C. L. Martinez <carlopmart@xxxxxxxxx> wrote:
> Hi all,
>
>  I am trying to setup a virtual kvm guest cluster under a centos 6.3
> x86_64 (guests are CentOS 6.3, too). When  I have setup
> fence_virt.conf (I will use fence_xvm/fence_virt to fence guests),
> these errors appears:
>
> [root@kvmhost etc]# fence_virtd -F -d99
> Background mode disabled
> Debugging threshold is now 99
> fence_virtd {
>         debug = "99";
>         listener = "multicast";
>         backend = "libvirt";
>         module_path = "/usr/lib64/fence-virt";
> }
>
> listeners {
>         multicast {
>                 key_file = "/etc/cluster/fence_xvm.key";
>                 address = "255.0.0.15";
>                 family = "ipv4";
>                 port = "1229";
>                 interface = "prodif";
>         }
>
> }
>
> backends {
>         libvirt {
>                 uri = "qemu:///system";
>         }
>
> }
>
> Backend plugin: libvirt
> Listener plugin: multicast
> Searching /usr/lib64/fence-virt for plugins...
> Searching for plugins in /usr/lib64/fence-virt
> Loading plugin from /usr/lib64/fence-virt/libvirt.so
> Registered backend plugin libvirt 0.1
> Loading plugin from /usr/lib64/fence-virt/multicast.so
> Failed to map backend_plugin_version
> Registered listener plugin multicast 1.1
> 2 plugins found
> Available backends:
>     libvirt 0.1
> Available listeners:
>     multicast 1.1
> Debugging threshold is now 99
> Using qemu:///system
> Debugging threshold is now 99
> Got /etc/cluster/fence_xvm.key for key_file
> Got ipv4 for family
> Got 255.0.0.15 for address
> Got 1229 for port
> Got prodif for interface
> Reading in key file /etc/cluster/fence_xvm.key into 0x13bb070 (4096 max size)
> Actual key length = 4096 bytes
> Setting up ipv4 multicast receive (255.0.0.15:1229)
> Joining multicast group
> Failed to bind multicast receive socket to 255.0.0.15: Invalid argument
> Check network configuration.
> Could not set up multicast listen socket
>
> Why is not possible to bind multicast socket?? In kvm host I have
> installed these packages:
>
> [root@kvmhost etc]# rpm -qa | grep fence | sort
> fence-virt-0.2.3-9.el6.x86_64
> fence-virtd-0.2.3-9.el6.x86_64
> fence-virtd-libvirt-0.2.3-9.el6.x86_64
> fence-virtd-multicast-0.2.3-9.el6.x86_64
>
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux