On Wed, 2009-08-05 at 20:42 -0400, Bernie Wu wrote:
> Hi Listers,
> How can I remove nodes that currently appear in my Linux HA Management Client
> ?
If it's heartbeat based cluster, first you should run hb_delnode to
delete the nodes.
And then delete them from cib:
If you are using the latest c
Hi Listers,
How can I remove nodes that currently appear in my Linux HA Management Client ?
These nodes belong to another cluster and they appear as stopped.
TIA
Bernie
The information contained in this e-mail message is intended only for the
personal and confi
I actually found exactly what you said 5 minutes after I sent the
email. Would have been
great for backing up the filesystem.
I have heartbeat up and running for a 3rd IP and found a bit to mount it:
grandpa IPaddr::192.168.0.243/24/eth0
Filesystem::/dev/drbd0::/data::xfs::defaults
Is that
There is no way to mount a secondary device without first promoting it
to primary.
If what you're looking to do is have one server primary with a read-only
secondary, it is not possible.
Your secondary servers 'cat /proc/drbd' should look similar with the
exception of Primary/Secondary are reverse
I have remade the system using single primary since that's all that
is needed in reality.
At current I have this on the primary:
r...@grandpa:~# cat /proc/drbd
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by
iv...@ubuntu, 2009-01-17 07:49:56
I am not using crm, because I find that it does not work reliably, so I am
using the 2.0.8 in v1 mode essentially.
I use monit to detect status of my services and issue restart or hb_standby if
needed.
Is 2.0.8 not a good version? It was the latest version I saw available in rpm
for my redhat
On Wednesday 05 August 2009 15:46:26 Lars Ellenberg wrote:
> On Wed, Aug 05, 2009 at 01:51:03PM +0200, Marc Cousin wrote:
> > Hi,
> >
> > I know this is a very old thread.
> >
> > But I'm now trying heartbeat 2.99.2 (from the provided rpm packages) and
> > I still have these 'local's in the drbd sc
Alain.Moulle wrote:
> Thanks Andrew,
>
> 1. So my understanding is that in a "more than 2 nodes cluster" , if
> two nodes are failed, the have_quorum is set to 0 by the cluster soft
> and the behavior is choosen by the administrator with the no-quorum-policy
> parameter. So the question is now : w
On Wed, Aug 05, 2009 at 01:51:03PM +0200, Marc Cousin wrote:
> Hi,
>
> I know this is a very old thread.
>
> But I'm now trying heartbeat 2.99.2 (from the provided rpm packages) and I
> still have these 'local's in the drbd script.
Please use DRBD 8.3.2 (or newer, in case someone digs up this t
Thanks Andrew,
1. So my understanding is that in a "more than 2 nodes cluster" , if
two nodes are failed, the have_quorum is set to 0 by the cluster soft
and the behavior is choosen by the administrator with the no-quorum-policy
parameter. So the question is now : what is the best choice for
no-q
I didn´t know/read about any restrictions on alias-interfaces yet.
> eth0:0 isn't a real device, you may find that's the problem.
>
> -Shane
>
> On 05/08/2009, at 8:46 PM, Testuser SST wrote:
>
> >
> >
> > yes it is, the drbd-device is working fine on that interface.
> >
> >
> >> This interface
eth0:0 isn't a real device, you may find that's the problem.
-Shane
On 05/08/2009, at 8:46 PM, Testuser SST wrote:
>
>
> yes it is, the drbd-device is working fine on that interface.
>
>
>> This interface eth0:0 its up?
>>
>> 2009/8/5 Testuser SST
>>
>>> Hi,
>>>
>>> is there a problem using ali
yes it is, the drbd-device is working fine on that interface.
> This interface eth0:0 its up?
>
> 2009/8/5 Testuser SST
>
> > Hi,
> >
> > is there a problem using alias-interfaces with heartbeat 2.1.3
> (CentOS-RPM)
> > ? I configured in the ha.cf something like:
> >
> > ucast eth0:0 192.168
This interface eth0:0 its up?
2009/8/5 Testuser SST
> Hi,
>
> is there a problem using alias-interfaces with heartbeat 2.1.3 (CentOS-RPM)
> ? I configured in the ha.cf something like:
>
> ucast eth0:0 192.168.95.13
>
> and got:
>
> debug: opening ucast eth0:0 (UDP/IP unicast)
> heartbeat[23629]:
Hi,
is there a problem using alias-interfaces with heartbeat 2.1.3 (CentOS-RPM) ? I
configured in the ha.cf something like:
ucast eth0:0 192.168.95.13
and got:
debug: opening ucast eth0:0 (UDP/IP unicast)
heartbeat[23629]: 2009/08/05_14:21:31 info: glib: ucast: write socket priority
set to IP
Hi,
I know this is a very old thread.
But I'm now trying heartbeat 2.99.2 (from the provided rpm packages) and I
still have these 'local's in the drbd script.
Is this normal ? Has the bug been corrected ?
On Monday 17 November 2008 12:35:20 Dejan Muhamedagic wrote:
> Hi,
>
> On Fri, Nov 14, 2
On Wed, Aug 5, 2009 at 10:22 AM, Alain.Moulle wrote:
> Hello,
>
> I'm a little bit confusing about quorum configuration :
> there is the have-quorum parameter which is normally
> managed by the cluster itself.
> On my configuration, its value is "0"
> But the Pacemaker documentation says :
>
On 08/05/2009 11:09 AM, Dominik Klein wrote:
> Tobias Appel wrote:
>> On 08/05/2009 10:30 AM, Dominik Klein wrote:
>>> Tobias Appel wrote:
So all I need is a command line tool to check wether a resource is
currently started or not. I tried to check the resources with the
failcount co
Tobias Appel wrote:
> On 08/05/2009 10:30 AM, Dominik Klein wrote:
>> Tobias Appel wrote:
>>> So all I need is a command line tool to check wether a resource is
>>> currently started or not. I tried to check the resources with the
>>> failcount command, but it's always 0. And the crm_resource comma
On 08/05/2009 10:30 AM, Dominik Klein wrote:
> Tobias Appel wrote:
>>
>> So all I need is a command line tool to check wether a resource is
>> currently started or not. I tried to check the resources with the
>> failcount command, but it's always 0. And the crm_resource command is
>> used to config
Tobias Appel wrote:
> Hi,
>
> I need a command to see if a resource is started or not. Somehow my IPMI
> resource does not always start, especially on one node (for example if I
> reboot the node, or have a failover). There is no error and nothing, it
> just does nothing at all.
> Usually I hav
Hi,
I need a command to see if a resource is started or not. Somehow my IPMI
resource does not always start, especially on one node (for example if I
reboot the node, or have a failover). There is no error and nothing, it
just does nothing at all.
Usually I have to clean up the resource and the
Hello,
I'm a little bit confusing about quorum configuration :
there is the have-quorum parameter which is normally
managed by the cluster itself.
On my configuration, its value is "0"
But the Pacemaker documentation says :
"have-quorum : If false, this may mean that the cluster cannot
Lars has asked me to announce that at long last, we have finalized the
new Linux-HA repository/project structure.
Effective immediately, Heartbeat 2.x has been split into the following
projects:
* cluster-glue 1.0
* resource-agents 1.0
* heartbeat 3.0-beta
### Cluster Glue 1.0 - http://hg.lin
24 matches
Mail list logo
