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

Lon Hohberger lhh at redhat.com
Wed Sep 30 15:08:08 UTC 2009


On Wed, 2009-09-30 at 15:25 +0200, Rene Rosenberger wrote:
> 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

Ok, so it's not the one fixed here:

http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=a9ac1e635c559b46512cf4251fe71c015bb6d70f

I don't recall if this will matter much, but get rid of the trailing
slash on /rootfs/vm/.

Also, ensure /rootfs/vm/Nagios and /root/fs/vm/Log-Server file names
match the names contained within the respective config files.

(e.g.  name = "Nagios" / name = "Log-Server" )

This is because rgmanager wants a vm "name" but xm wants a "config file"
- so they have to match.

-- Lon




More information about the Linux-cluster mailing list