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

RE: [Linux-cluster] Problem with fenced on 2 node cluster



Lon,
 
Thanks for your response. I didn't realize that /sbin/fenced should be running at all times. During an actual fence action, I do see fence_apc show up so this all sounds normal, right? 
 
Brad Filipek


________________________________

From: linux-cluster-bounces redhat com on behalf of Lon Hohberger
Sent: Tue 1/29/2008 1:06 PM
To: linux clustering
Subject: Re: [Linux-cluster] Problem with fenced on 2 node cluster



On Tue, 2008-01-29 at 12:05 -0600, Brad Filipek wrote:
> I have a 2 node cluster setup fairly basic right now (mounts an ext3
> filesystem, and activates a virtual IP). When both boxes are powered
> off, I can start up node1 just fine. It starts the services and runs
> great. Then I power up node2 and it joins fine. However, if I run "ps
> aux | grep fenced" on node1 I see that /sbin/fenced is running and it
> never goes away. Is there anyway to check and see what it is doing? I
> know that the fenced service works because it will reboot the other
> node if I disconnect the network cable. I am using an APC master
> switch for power.

fenced should stay running at all times... did you mean it's stuck in an
infinite loop?

fenced spawns agents - such as 'fence_apc' - which should only be
present during a fencing operation.  If those stay around for a long
time, there's a problem.

-- Lon


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



Confidentiality Notice: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. 

If you have received this communication in error, please notify us immediately by email reply or by telephone and immediately delete this message and any attachments.

<<winmail.dat>>


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