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

RE: [Linux-cluster] Cluster Suite 4 failover problem

> -----Original Message-----
> Scenario: Running services running in node1, then i shutdown 
> the eth0 of
> node1
> Result: Services not failover to node2, and the clustat in 
> node1 shows that:
> Member Status: Quorate
>   Member Name                      Status
>   ------ ----                              ------
>   node1                                    Offline
>   node2                                    Online, Local, rgmanager
>   Service Name     Owner (Last)                   State
>   ------- ----         ----- ------                       -----
>   ftp                       unkonwn                          started
>   www                   unkonwn                          started
>        <ip address="" monitor_link="0"/>
>        <ip address="" monitor_link="0"/>

Some things to be aware of:

- cluster checks the status of "ftp" and "www" services using the
scripts. If the scripts say the service is running, cluster considers
the service as available. Most service scripts simply look for the
process name or PID to determine if a service is running.

- you have monitor_link turned off on your IP addresses - this means
when you down your eth0 interface, cluster manager isn't going to notice
that those IP addresses aren't working.

With manual fencing, the cluster is going to sit there and wait until
you manually reboot that failed node.

OpSource Inc.

PGP Key ID 0x6CB364CA 

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