Hello. I am trying to get a GFS2 drive to synchronize between 2 servers
using DRBD and Pacemaker but am encountering some errors.
The following link contains all my configuration and the errors I am
getting. Please have a look. All help is greatly appreciated.
Please see --> http://aladdin.jobspa
You didn't have to do 'yum makecache'
Sometimes ago Andrew accidentally replaced some rpms without bumping up
revision number.
This made yum to complain.
'yum clean all' should have cured all that.
On Tue, May 11, 2010 at 2:09 PM, Simon Lavigne-Giroux wrote:
> I found the solution to my probl
I found the solution to my problem, I had to do a 'yum clean all' and 'yum
makecache' before doing the 'yum update'
I'm just getting used to yum.
Simon
On Mon, May 10, 2010 at 12:55 PM, Simon Lavigne-Giroux
wrote:
> Hi,
>
> I'm trying to install pacemaker from your epel-5 repository from your g
The is no "default" unless it's set, that's why crm complains
On Tue, May 11, 2010 at 12:41 PM, Gianluca Cecchi wrote:
> On Tue, May 11, 2010 at 5:47 PM, Vadym Chepkov wrote:
>
>> pingd is a daemon with is running all the time and does it job
>> you still need to define monitor operation thou
On Tue, May 11, 2010 at 5:47 PM, Vadym Chepkov wrote:
> pingd is a daemon with is running all the time and does it job
> you still need to define monitor operation though, what if the daemon dies?
> op monitor just have a different meaning for ping and pingd.
> with pingd - monitor daemon
> with
Hello,
I'm using pacemaker 1.0.8 on rh el 5.5 x86 with clusterlabs repo.
Based on other posts on linux-ha I'm trying to configure a 2-nodes cluster
where one of the nodes is nfs-server and the other one is nfs-client of the
resource exported by the first one.
The main parts borrowed form the relat
pingd is a daemon with is running all the time and does it job
you still need to define monitor operation though, what if the daemon dies?
op monitor just have a different meaning for ping and pingd.
with pingd - monitor daemon
with ping - monitor connectivity
as for warnings:
crm configure prop
On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov wrote:
> First of all, none of the monitor operation is on by default in pacemaker,
> this is something that you have to turn on
> For the ping RA start and stop op parameters don't do much, so you can
> safely drop them.
>
>
>
Yes, but for the pace
Hi again!
All interfaces in SuSEfirewall2 is set to "Internal zone".
I start openais on one node of two configured.
Openais starts, but resources do not run.
When the SLES boots, I see, that SuSEfirewall2 phase 1 of 2 runs _before_
openais and phase 2 of 2 runs _after_ openais.
This is the dep
By the way, there is another issue with your config
Since you set multiplier to 100, it will negate your resource-stickiness which
is also set to 100.
Either reduce multiplier or increase default resource-stickiness ( I have mine
at 1000)
Vadym
On May 11, 2010, at 7:06 AM, Gianluca Cecchi wrot
Dejan,
that patch made it into 1.1, but not into stable-1.0. Please make sure
it's applied in (and pushed to) both branches. Thanks!
Cheers,
Florian
On 05/11/2010 11:47 AM, Dejan Muhamedagic wrote:
> Applied. Thanks!
>
> Dejan
>
> On Mon, May 10, 2010 at 03:21:18PM +0200, Florian Haas wrote:
>
First of all, none of the monitor operation is on by default in pacemaker, this
is something that you have to turn on
For the ping RA start and stop op parameters don't do much, so you can safely
drop them.
Here is my settings, they do work for me:
primitive ping ocf:pacemaker:ping \
On Tue, May 11, 2010 at 12:50 PM, Vadym Chepkov wrote:
> You forgot to turn on monitor operation for ping (actual job)
>
>
>
I saw from the
[r...@ha1 ~]# crm ra meta ping
command
Operations' defaults (advisory minimum):
start timeout=60
stop timeout=20
reload
You forgot to turn on monitor operation for ping (actual job)
On May 11, 2010, at 5:15 AM, Gianluca Cecchi wrote:
> On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
> # crm ra meta ping
>
> name (string, [undef]): Attribute name
> The name of the attributes to set. This is the name t
On Tue, May 11, 2010 at 11:58 AM, Dejan Muhamedagic
wrote:
> Do you see the attribute set in the status section (cibadmin -Ql
> | grep -w pingd)? If not, then the problem is with the resource.
[r...@ha1 ~]# cibadmin -Ql | grep -w pingd
Tried to ch
Hi,
On Tue, May 11, 2010 at 11:15:49AM +0200, Gianluca Cecchi wrote:
> On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
>
> > # crm ra meta ping
> >
> > name (string, [undef]): Attribute name
> > The name of the attributes to set. This is the name to be used in the
> > constraints.
> >
Applied. Thanks!
Dejan
On Mon, May 10, 2010 at 03:21:18PM +0200, Florian Haas wrote:
> # HG changeset patch
> # User Florian Haas
> # Date 1273497566 -7200
> # Branch stable-1.0
> # Node ID 70e87f10e76ba6cdada583c0c29ed47168b2878f
> # Parent 423891ec6d91c77582973bed51bc36068a550feb
> Medium: sh
After reconstructing the logs (because they were unreadable) I found
that they didn't go back far enough.
Please _attach_ logs from the time prmFsPostgreSQLDB3-2 was started by
the cluster.
On Tue, May 11, 2010 at 9:01 AM, wrote:
> Hi,
>
> On a test of Pacemaker before a little, the following pr
On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
> # crm ra meta ping
>
> name (string, [undef]): Attribute name
> The name of the attributes to set. This is the name to be used in the
> constraints.
>
> By default is "pingd", but you are checking against pinggw
>
> I suggest you do not
Andrew Beekhof пишет:
IIRC, Whatever port number you listed in openais.conf, you need to
open that port and that port + 1 in the firewall.
I agree. But in firewall this interface is set to "Internal Zone"... How
can I open an additional port for "internal zone"?
Does "internal zone" not mean
Hi,
On a test of Pacemaker before a little, the following problem happened.
* corosync 1.2.1
* Pacemaker-1-0-8463260ff667
* Reusable-Cluster-Components-c447fc25e119
* Cluster-Resource-Agents-f92935082277
A problem is that the monitor error of the prmFsPostgreSQLDB3-2 resource that
stopped o
21 matches
Mail list logo
