"crm_verify -L" or "crm_mon" will point you in the right direction.
looks like apache isn't happy on vm2
2010/5/17 李森 :
> Thanks for you reply.
>
> 1.the version is 1.0.8 for heartbeat 3.0.2.
>
>
> 2.
> there are two nodes in my cluster : vm1 172.16.0.11 vm2 172.16.0.12
> the ip-aliase is 172.16.
I've put together a Pacemaker configuration using one failover IP, four DRBD
resources, four iSCSI Targets, and four iSCSI Logical Units. The Pacemaker
config file is listed at the bottom. I'm curious if there is a better way for
the resources in my config file to be arranged/listed/grouped?
On May 17, 2010, at 5:40 PM, Ruiyuan Jiang wrote:
> Hi, Gianluca
>
> I modified my configuration and deleted “crm configure property
> no-quorum-policy=ignore” as you suggested but I have the same problem that
> the IP address does not fail. Thanks.
>
> [r...@usnbrl52 log]# crm configure sh
Hi, Gianluca
I modified my configuration and deleted "crm configure property
no-quorum-policy=ignore" as you suggested but I have the same problem that the
IP address does not fail. Thanks.
[r...@usnbrl52 log]# crm configure show
node usnbrl52
node usnbrl53
primitive ClusterIP ocf:heartbeat:IPa
On May 17, 2010, at 11:56 AM, Simon Lavigne-Giroux wrote:
> Hi,
>
> I have 2 servers running Pacemaker. When the router fails, both nodes become
> primary. Is it possible for Pacemaker on the secondary server to detect that
> the network connection is not available and not become primary.
>
Thanks. Then the patch will look like this:
--- a/heartbeat/pgsql 2010-05-03 01:20:16.0 -0600
+++ b/heartbeat/pgsql 2010-05-17 13:43:04.0 -0600
@@ -343,21 +343,10 @@
# Validate most critical parameters
pgsql_validate_all() {
-if ! have_binary $SH
-then
-retur
Hi Serge,
On 05/17/2010 07:50 PM, Serge Dubrouski wrote:
> I'm really sorry but please disregard that patch. The more appropriate
> would be these two attached patches.
> # Validate most critical parameters
> pgsql_validate_all() {
> -if ! have_binary $SH
> +if ! check_binary $SH
>
I'm really sorry but please disregard that patch. The more appropriate
would be these two attached patches.
On Mon, May 17, 2010 at 11:35 AM, Serge Dubrouski wrote:
> Hello -
>
> Here is follow up patch for today's incident with pgsql script. The
> patch is intended to cover up an issue with miss
Hello -
Here is follow up patch for today's incident with pgsql script. The
patch is intended to cover up an issue with missed /sbin/fuser tool:
--- /usr/lib/ocf/resource.d/heartbeat/pgsql 2010-05-03 01:20:16.0
-0600
+++ usr/lib/ocf/resource.d/heartbeat/pgsql.new 2010-05-17
11:32:33
On Mon, May 17, 2010 at 12:56 PM, Vadym Chepkov wrote:
>
> On May 17, 2010, at 2:52 AM, Andrew Beekhof wrote:
>
>> On Sun, May 16, 2010 at 1:09 AM, Vadym Chepkov wrote:
>>> Hi
>>>
>>> I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
>>> /var/lib/pengine,
>>> especially wh
Hi,
I have 2 servers running Pacemaker. When the router fails, both nodes become
primary. Is it possible for Pacemaker on the secondary server to detect that
the network connection is not available and not become primary.
Thanks
Simon
___
Pacemaker mai
Hi,
On Mon, May 17, 2010 at 06:56:00AM -0400, Vadym Chepkov wrote:
>
> On May 17, 2010, at 2:52 AM, Andrew Beekhof wrote:
>
> > On Sun, May 16, 2010 at 1:09 AM, Vadym Chepkov wrote:
> >> Hi
> >>
> >> I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
> >> /var/lib/pengin
Hi,
On Mon, May 17, 2010 at 12:24:12PM +0200, patrik.rappo...@knapp.com wrote:
>
> hy,
>
> I have following problem:
>
> I configured a 2 node cluster running SLES11 with the HAE extension. I use
> "pacemaker-1.0.3-4.1", "openais-0.80.3-26.1" and "ocfs2 1.4.1".
> I used the SLES high availabilt
For if it helps someone, I solved by putting the rings and the drbd
connection on separate cards, 3 in total, one for each thing
Ivan
De: Ivan Coronado [mailto:icoron...@epcge.com]
Enviado el: viernes, 14 de mayo de 2010 17:25
Para: The Pacemaker cluster res
On May 17, 2010, at 2:52 AM, Andrew Beekhof wrote:
> On Sun, May 16, 2010 at 1:09 AM, Vadym Chepkov wrote:
>> Hi
>>
>> I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
>> /var/lib/pengine,
>> especially when cluster-recheck-interval is set to enable failure-timeout
>> c
Hi,
On Thu, May 13, 2010 at 07:37:31PM +0200, Ivan Coronado wrote:
> Hello to everybody,
>
> I have a problem with the corosync.conf setup. I have a drbd service
> runing on eth3, and a general network and the stonith device (idrac6) in
> the eth0. If I unplug the eth3 to simulate a network fail
Thanks for you reply.
1.the version is 1.0.8 for heartbeat 3.0.2.
2.
there are two nodes in my cluster : vm1 172.16.0.11 vm2 172.16.0.12
the ip-aliase is 172.16.0.100
i use the crm cli command to config:
primitive ip-aliase ocf:heartbeat:IPaadr2 params ip="172.16.0.100" op
monitor interval="5s
On 05/17/2010 08:52 AM, Andrew Beekhof wrote:
> On Sun, May 16, 2010 at 1:09 AM, Vadym Chepkov wrote:
>> Hi
>>
>> I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
>> /var/lib/pengine,
>> especially when cluster-recheck-interval is set to enable failure-timeout
>> checks.
>
version? actual config? cibadmin output?
On Mon, May 17, 2010 at 9:14 AM, 李森 wrote:
> hi all:
>
> I create a group with two resources:
>
> group1:
> ip-aliase
> apache
>
> my cluster has two nodes:
>
> crm(live)# configure
> crm(live)configure# property symme
The problem is that you have
and
This causes a problem when nfsclient can only run on the current drbd master.
Its best to linearize the colocation chain where possible, try this
instead of the second constraint:
On Wed, May 12, 2010 at 10:22 PM, Gianluca Cecchi
wrote:
>
hi all:
I create a group with two resources:
group1:
ip-aliase
apache
my cluster has two nodes:
crm(live)# configure
crm(live)configure# property symmetric-cluster=false
crm(live)configure# location constrain1 group1 200: host1
crm(live)configure# location
21 matches
Mail list logo
