On 5 October 2010 22:12, Mike A Meyer wrote:
> We are setup in a two node active/passive cluster using pacemaker/corosync.
> We shutdown the pacemaker/corosync on both nodes and changed the uname -n
> on our nodes to show the short name instead of the FQDN. Started up
> pacemaker/corosync and e
On Tue, Oct 5, 2010 at 7:53 PM, Shravan Mishra wrote:
> Hi,
>
> I was interested in knowing that if I have to choose between pacemaker
> 1.0 vs 1.1 which one should I use.
Have a read of:
http://theclusterguy.clusterlabs.org/post/441442543/new-pacemaker-release-series
I would recommend 1.1.
I am having a similar problem, so let's wait for the experts, But in the
meanwhile, try changing
location loc_pingd g_cluster_services rule -inf: not_defined p_pingd
or p_pingd lte 0
to
location loc_pingd g_cluster_services rule -inf: not_defined pingd
or pingd number:lte 0
and see what happ
Hello,
I have a 2 node cluster, running DRBD, heartbeat and pacemaker in
active/passive mode. On both nodes, eth0 is connected to the main
network, eth1 is used to connect the nodes directly to each other.
The nodes share a virtual IP address on eth0. Pacemaker is also
controlling a custom servi
We are setup in a two node active/passive
cluster using pacemaker/corosync. We shutdown the pacemaker/corosync
on both nodes and changed the uname -n on our nodes to show the short name
instead of the FQDN. Started up pacemaker/corosync and ever since
we done that, when we run the crm_mon command
Hi,
I was interested in knowing that if I have to choose between pacemaker
1.0 vs 1.1 which one should I use.
Thanks
Shravan
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home:
05.10.2010 12:12, Andrew Beekhof wrote:
> On Mon, Oct 4, 2010 at 6:31 AM, Vladislav Bogdanov
> wrote:
>> Hi all,
>>
>> just wondering, is there a way to make resource depend on (be colocated
>> with) either of two other resources?
>
> Not yet. Its something we want to support eventually though.
Really appreciate your response.
I just wanted to close this thread by saying that we were able to
figure out the problem.
Since pacemaker was running on other virtual machines except our
appliance clearly the problem was our runtime environment.
It turns out that our libxml2 library on our appli
Hi,
I use pacemaker 1.1.2.1 + corosync 1.2.1 (on openSuse 11.3).
Logging is configured in corosync.conf as follows:
logging {
fileline: off
to_stderr: no
to_logfile: no
to_syslog: yes
syslog_facility: daemon
syslog_priority: warn
Hi,
On Tue, Oct 05, 2010 at 11:18:37AM +0200, Andrew Beekhof wrote:
> Dejan: looks like something in the lrm library.
> Any idea why the message doesn't contain lrm_opstatus?
Becase this monitor operation never run. Which seems to be a
plausible explanation since the start-delay is set to 600s.
On 5 October 2010 13:19, Andrew Beekhof wrote:
> On Tue, Oct 5, 2010 at 12:51 PM, Pavlos Parissis
> wrote:
> > Hi,
> >
> > I am thinking to put under cluster control the sshd and I am checking if
> the
> > /etc/init.d/sshd supplied by RedHat 5.4 is compatible with LSB.
> > So, I run the test men
On Tue, Oct 5, 2010 at 12:51 PM, Pavlos Parissis
wrote:
> Hi,
>
> I am thinking to put under cluster control the sshd and I am checking if the
> /etc/init.d/sshd supplied by RedHat 5.4 is compatible with LSB.
> So, I run the test mentioned here [1] and it fails at test 6, it returns 1
> and failed
The resource failed when the sleep expired, i.e. each 600 secs.
Now I changed the resource to
sleep 7200, failure-timeout 3600
i.e. to values far beyond the recheck-interval opf 15m.
Now everything behaves as expected.
Mit freundlichen Grüßen / Kind regards
Holger Teutsch
From: Andre
Hi,
I am thinking to put under cluster control the sshd and I am checking if the
/etc/init.d/sshd supplied by RedHat 5.4 is compatible with LSB.
So, I run the test mentioned here [1] and it fails at test 6, it returns 1
and failed message.
Could this create problems within pacemaker?
Regards,
Pav
On 5 October 2010 11:15, Andrew Beekhof wrote:
> On Fri, Oct 1, 2010 at 9:53 AM, Pavlos Parissis
> wrote:
> > Hi,
> > It seams that it happens every time PE wants to check the conf
> > 09:23:55 crmd: [3473]: info: crm_timer_popped: PEngine Recheck Timer
> > (I_PE_CALC) just popped!
> >
> > and t
On Monday 04 October 2010 15:00:25 mathias.enzensber...@knapp.com wrote:
> Hi all,
>
> I use openais/pacemaker v.1.1.2 on SLES 11.1 and would like to use the
> SNMP function of crm_mon.
> But this part is documented really scanty (e.g. the part for configuring
> SNMP notifications is blank).
> I f
Dejan: looks like something in the lrm library.
Any idea why the message doesn't contain lrm_opstatus?
lrm_targetrc also looks strange.
On Thu, Sep 30, 2010 at 9:41 PM, Ron Kerry wrote:
> Folks -
>
> I am seeing the following message sequence that results in a "bogus"
> declaration of monitor fai
Hi Andrew,
I registered these contents with Bugzilla as enhancement of the functions.
* http://developerbugs.linux-foundation.org/show_bug.cgi?id=2501
Thanks,
Hideo Yamauchi.
--- renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> Thank you for comment.
>
> > > Is the change of this attrd a
On Fri, Oct 1, 2010 at 9:53 AM, Pavlos Parissis
wrote:
> Hi,
> It seams that it happens every time PE wants to check the conf
> 09:23:55 crmd: [3473]: info: crm_timer_popped: PEngine Recheck Timer
> (I_PE_CALC) just popped!
>
> and then check_rsc_parameters() wants to reset my resources
>
> 09:23:
On Mon, Oct 4, 2010 at 6:31 AM, Vladislav Bogdanov wrote:
> Hi all,
>
> just wondering, is there a way to make resource depend on (be colocated
> with) either of two other resources?
Not yet. Its something we want to support eventually though.
> Use case is iSCSI initiator connection to iSCSI t
On Mon, Oct 4, 2010 at 3:00 PM, wrote:
>
> Hi all,
>
> I use openais/pacemaker v.1.1.2 on SLES 11.1 and would like to use the SNMP
> function of crm_mon.
> But this part is documented really scanty (e.g. the part for configuring
> SNMP notifications is blank).
> I found out that there is a specia
On Tue, Oct 5, 2010 at 11:07 AM, Andrew Beekhof wrote:
> On Fri, Oct 1, 2010 at 3:40 PM, wrote:
>> Hi,
>> I observed the following in pacemaker Versions 1.1.3 and tip up to patch
>> 10258.
>>
>> In a small test environment to study fail-count behavior I have one resource
>>
>> anything
>> doing
On Fri, Oct 1, 2010 at 3:40 PM, wrote:
> Hi,
> I observed the following in pacemaker Versions 1.1.3 and tip up to patch
> 10258.
>
> In a small test environment to study fail-count behavior I have one resource
>
> anything
> doing sleep 600 with monitoring interval 10 secs.
>
> The failure-timeou
On Fri, Oct 1, 2010 at 3:45 PM, Shravan Mishra wrote:
> Hi,
>
> Just a quick question, who generates the very first cib.xml when
> pacemaker processes are initialized?
The cib
>
> Thanks
> Shravan
>
> On Thu, Sep 30, 2010 at 4:22 AM, Andrew Beekhof wrote:
>> On Tue, Sep 28, 2010 at 11:47 AM, An
On Sun, Oct 3, 2010 at 4:01 PM, hudan studiawan wrote:
> Hi,
>
> I want to start to contribute to Pacemaker project. I start to read
> Documentation and try some basic configurations. I have a question: what
> kind of algorithm used by Pacemaker to choose another node when a node die
> in a cluste
25 matches
Mail list logo
