AW: [Linux-cluster] Problems starting a VM Service

Rene Rosenberger r.rosenberger at netbiscuits.com
Wed Sep 30 13:25:08 UTC 2009


Hi,

rgmanager-2.0.52-1

[root at cluster-node02 ~]# cat /etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster alias="cluster01" config_version="16" name="cluster01">
        <fence_daemon clean_start="0" post_fail_delay="0"
post_join_delay="3"/>
        <clusternodes>
                <clusternode name="cluster-node01.netbiscuits.com"
nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="Fence_Device_01"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="cluster-node02.netbiscuits.com"
nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="Fence_Device_02"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_ipmilan" ipaddr="192.168.100.141"
login="root" name="Fence_Device_01" passwd="emoveo11wap"/>
                <fencedevice agent="fence_ipmilan" ipaddr="192.168.100.142"
login="root" name="Fence_Device_02" passwd="emoveo11wap"/>
        </fencedevices>
        <rm>
                <failoverdomains>
                        <failoverdomain name="Failover_Domain_01"
nofailback="0" ordered="0" restricted="0">
                                <failoverdomainnode
name="cluster-node01.netbiscuits.com" priority="1"/>
                                <failoverdomainnode
name="cluster-node02.netbiscuits.com" priority="1"/>
                        </failoverdomain>
                </failoverdomains>
                <resources/>
                <vm autostart="1" domain="Failover_Domain_01" exclusive="0"
migrate="live" name="Nagios" path="/rootfs/vm/" recovery="relocate"/>
                <vm autostart="1" domain="Failover_Domain_01" exclusive="0"
migrate="live" name="Log-Server" path="/rootfs/vm/" recovery="relocate"/>
        </rm>
</cluster>

Regards, rene

-----Ursprüngliche Nachricht-----
Von: Lon Hohberger [mailto:lhh at redhat.com] 
Gesendet: Mittwoch, 30. September 2009 15:21
An: r.rosenberger at netbiscuits.com; linux clustering
Betreff: Re: [Linux-cluster] Problems starting a VM Service

On Wed, 2009-09-30 at 14:14 +0200, Rene Rosenberger wrote:
> Hi,
> 
>  
> 
> i have Luci and Ricci installed. I have also created a Xen VM on
> cluster-node01. After that i copied the conf file fort hat vm to a
> place where both cluster-nodes can access it. When i now try to start
> a sopped vm service it starts. Nice J but in clustat and in luci it is
> shown as stopped! The thing is that luci really starts the vm service.

Need cluster.conf & rgmanager version

There were some weird (now fixed) problems with VMs which involved a
race between cluster.conf updates and status checks; it's possible you
hit one of them.

-- Lon






More information about the Linux-cluster mailing list