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

RE: [Linux-cluster] Event in one failover domain affecting anotherseparate failover domain

Ok, I've set the log level to debug so hopefully next time this happens
I can get more info. Of course this is a production cluster so there is
only so much I can do in terms of testing.. Here is the cluster.conf
(sanitized but otherwise accurate):

<?xml version="1.0"?>
<cluster alias="cluster_a" config_version="2" name="cluster_a">
        <quorumd device="/dev/mapper/mpath5p1" interval="3" tko="23"
        <cman deadnode_timeout="135" expected_votes="6">
                <multicast addr=""/>
        <fence_daemon post_fail_delay="0" post_join_delay="30"/>
                <clusternode name="server_a" votes="1">
                                <method name="1">
                                        <device name="server_a-ilo"/>
                        <multicast addr="" interface="bond0"/>
                <clusternode name="server_b" votes="1">
                                <method name="1">
                                        <device name="server_b-ilo"/>
                        <multicast addr="" interface="bond0"/>
                <clusternode name="server_c" votes="1">
                                <method name="1">
                                        <device name="server_c-ilo"/>
                        <multicast addr="" interface="bond0"/>
                <fencedevice agent="fence_ilo" hostname="server_a-ilo"
login="clu_user" name="server_a-ilo" passwd="..removed.."/>
                <fencedevice agent="fence_ilo" hostname="server_b-ilo"
login="clu_user" name="server_b-ilo" passwd="..removed.."/>
                <fencedevice agent="fence_ilo" hostname="server_c-ilo"
login="clu_user" name="server_c-ilo" passwd="..removed.."/>
        <rm log_level="7">
                        <failoverdomain name="DOMAIN_ONE" ordered="1"
                                <failoverdomainnode name="server_a"
                                <failoverdomainnode name="server_b"
                        <failoverdomain name="DOMAIN_TWO" ordered="1"
                                <failoverdomainnode name="server_c"
                                <failoverdomainnode name="server_b"
                <service autostart="1" domain="DOMAIN_ONE"
name="service_one" recovery="relocate">
                        <script file="/etc/init.d/service_one"
                        <lvm lv_name="lvapp1" name="app1-lvm"
                        <ip address="xxx.xxx.xxx.100" monitor_link="1"/>
                        <fs device="/dev/cluvg-app1/lvapp1"
force_fsck="1" force_unmount="1" fsid="64050" fstype="ext3"
mountpoint="/app1" name="app1-fs" options="" self_fence="0"/>
                <service autostart="1" domain="DOMAIN_TWO"
name="service_two" recovery="relocate">
                        <script file="/etc/init.d/service_two"
                        <lvm lv_name="lvapp2" name="app2-lvm"
                        <lvm lv_name="lvapp2_data" name="app2-data-lvm"
                        <ip address="xxx.xxx.xxx.200" monitor_link="1"/>
                        <fs device="/dev/cluvg-app2/lvapp2"
force_fsck="1" force_unmount="1" fsid="45751" fstype="ext3"
mountpoint="/app2" name="app2-fs" options="" self_fence="0"/>
                        <fs device="/dev/cluvg-app2-data/lvapp2_data"
force_fsck="1" force_unmount="1" fsid="985" fstype="ext3"
mountpoint="/app2/data" name="app2-data-fs" options="" self_fence="0"/>

-----Original Message-----
From: linux-cluster-bounces redhat com
[mailto:linux-cluster-bounces redhat com] On Behalf Of Lon Hohberger
Sent: Monday, April 21, 2008 2:02 PM
To: linux clustering
Subject: Re: [Linux-cluster] Event in one failover domain affecting
anotherseparate failover domain

On Mon, 2008-04-21 at 13:22 -0400, Kielek, Samuel wrote:

> The issue I have observed is that when server_c (DOMAIN_TWO) had an
> issue that led to it being fenced, the service running on server_a
> (service_one) immediately stopped and relocated to server_b (the
> recovery action is set to "relocate" for both services).

Your cluster.conf would be helpful.

Also, you can increase the log level to 'debug' which would tell you
more; see "Logging Configuration":


...for more information.

-- Lon

Linux-cluster mailing list
Linux-cluster redhat com

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