No, but you can use a monitoring service like nagios to do that.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patricio A. Bruna
Sent: Thursday, October 16, 2008 11:03 PM
To: linux-cluster@redhat.com
Subject: [Linux-cluster] Email alert
Its possible to configure Cluster Sui
11:03:57 -0500
From: "Mark Chaney" <[EMAIL PROTECTED]>
Subject: RE: [Linux-cluster] Can't create LV in 2-node cluster
To: "'linux clustering'"
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;charset="us-ascii"
What are yo
What are you using for shared storage? Also, 2 node clusters are highly
discouraged from my experience and recommendations of others.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, October 06, 2008 10:28 AM
To: linux-cluste
AM
To: linux clustering
Subject: Re: [Linux-cluster] error messages explained
Mark Chaney wrote:
> When you say, need to join with the services running. What services do I
> need to start in order to do this manual join? Just cman? If a node
crashes
> and cant rejoin. I have to hurry u
I have a 3 node cluster. When I fence a single server (skydive.local) from
wheeljack.local, I get the following results (2 servers clustered). I can
duplicate this with any of my 3 servers. Why is the second server being
fenced?
##
[EMAIL PROTECTED] ~]#
a
design perspective.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christine Caulfield
Sent: Friday, October 03, 2008 2:39 AM
To: linux clustering
Subject: Re: [Linux-cluster] error messages explained
Mark Chaney wrote:
> Cam someone explain to me these e
I have a 3 node cluster running gfs. They have a private gigabit network
that's used for cluster communication and backups. Can you recommend what
type of settings I should have here? My nodes don't seem to rejoin the
cluster to well after being fenced.
Thanks,
Mark
--
Linux-cluster mailing l
Cam someone explain to me these errors and tell me how I should attempt to
resolve them? They both aren't happening at the same time exactly, its just
to errors that I don't truly understand.
ccsd[3192]: Attempt to close an unopened CCS descriptor (13590).
ccsd[3192]: Error w
the reverse order. Don't forget to chkconfig
on after you have the cluster working again.
On Mon, Sep 29, 2008 at 3:06 AM, Mark Chaney <[EMAIL PROTECTED]> wrote:
I have a 3 node cluster that has shared storage using iscsi san, hence I am
using GFS. Anyway, I had it crash for whatever
Here is my cluster.conf
#
:[EMAIL PROTECTED] On Behalf Of Mark Chaney
Sent: Monday, September 29, 2008 3:16 AM
To: 'linux clustering'
Subject: RE: [Linux-cluster] proper cluster crash procedures?
Here is my cl
PROTECTED] On Behalf Of Mark Chaney
Sent: Monday, September 29, 2008 3:07 AM
To: linux-cluster@redhat.com
Subject: [Linux-cluster] proper cluster crash procedures?
I have a 3 node cluster that has shared storage using iscsi san, hence I am
using GFS. Anyway, I had it crash for whatever reason, not sure if
I have a 3 node cluster that has shared storage using iscsi san, hence I am
using GFS. Anyway, I had it crash for whatever reason, not sure if something
was rebooted incorrectly or what, but now I have been spending the past 2
hours trying to get the cluster back up. I would think that sampling
reb
My cluster nodes are getting fenced when I simply just restart the network
service. What can I do to prevent that happening so quick? Can I even
prevent it since im using GFS?
I have a 3 node cluster running CentOS 5.2. They all are connected to my
iscsi SAN, so CLVMD is being used and GFS as well
AM
To: Mark Chaney
Cc: Linux-cluster@redhat.com
Subject: Re: [Linux-cluster] dlm: no local IP address has been set
On Wed, Sep 03, 2008 at 05:05:02AM -0500, Mark Chaney wrote:
> grr, I am still getting this error every so often:
>
> dlm: no local IP address has been set
> dlm: cannot s
grr, I am still getting this error every so often:
dlm: no local IP address has been set
dlm: cannot start dlm lowcomms -107
but my hosts files are fine and actually all servers are members of the
clutser
error is only showing on 1 of 3 servers and its always right after they come
back up after b
Are you using shared storage? Is far as I know, the current cluster suite
wont do an automatic live migration to another server during a reboot, but
it will do the live migration back after the reboot. Does that make sense?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paras pr
17 matches
Mail list logo
