Hi Kristoffer,
> It is possible that there is a bug in crmsh, I will investigate.
>
> Could you file an issue for this problem at
> http://github.com/crmsh/crmsh/issues ? This would help me track the
> problem.
Okay!
Many Thanks!
Hideo Yamauchi.
- Original Message -
> From: Kristoffe
Hi All,
We confirmed a function of crmsh by the next combination.
* corosync-2.3.4
* pacemaker-Pacemaker-1.1.12
* crmsh-2.1.0
We prepared the following cli file.
---
### Cluster Option ###
property no-quorum-policy="ignore" \
stonith-enabled="true" \
startup
Hi David,
I made pullrequest.
* https://github.com/ClusterLabs/pacemaker/pull/620
And ... My pullrequest before the next waits for your approval, too.
Please confirm it.
* https://github.com/ClusterLabs/pacemaker/pull/594
Best Regards,
Hideo Yamauchi.
- Original Message -
> From:
Hi David,
Okay.
I will send pullrequest the day after tomorrow.
Many Thanks!
Hideo Yamauchi.
- Original Message -
> From: David Vossel
> To: renayama19661...@ybb.ne.jp; The Pacemaker cluster resource manager
>
> Cc:
> Date: 2014/12/22, Mon 23:43
> Subject: Re: [Pacemaker] [Patch]Me
Hi All,
Whenever a node to constitute a cluster repeats start and a stop, Pacemakerd of
the node not to stop leaks out memory.
I attached a patch.
Best Regards,
Hideo Yamauchi.
pacemakerd.patch
Description: Binary data
___
Pacemaker mailing list: Pace
Hi All,
Our user operated cibadmin command by mistake.
By an operation error, reboot of crmd occurs.
Step 1) Start a cluster.
[root@rh70-node1 ~]# crm_mon -1 -Af
Last updated: Wed Nov 5 10:26:51 2014
Last change: Wed Nov 5 10:23:39 2014
Stack: corosync
Current DC: rh70-node1 (3232238160) - par
Hi Andrew,
> I would suggest neither is correct.
> I've changed it to:
>
> [root@rh70-node1 ~]# crm_failcount
> You must supply a resource name to check. See 'crm_failcount --help' for
> details
This is the message which is plain with kindness.
Many Thanks!
Hideo Yamauchi.
- Origin
Hi All,
The next error is displayed when I carry out crm_failcount of Pacemaker.
[root@rh70-node1 ~]# crm_failcount
error: crm_abort: read_attr_delegate: Triggered assert at cib_attrs.c:342
: attr_name != NULL || attr_id != NULL
However, I think that the next error should be displayed.
Hi Andrew,
The problem was settled with your patch.
Please merge a patch into master.
Please confirm whether there is not a problem in other points either concerning
g_timeout_add() and g_source_remove() if possible.
Many Thanks!
Hideo Yamauchi.
- Original Message -
> From: "renayam
Hi Andrew,
Thank you for comments.
> diff --git a/lib/services/services_linux.c b/lib/services/services_linux.c
> index 961ff18..2279e4e 100644
> --- a/lib/services/services_linux.c
> +++ b/lib/services/services_linux.c
> @@ -227,6 +227,7 @@ recurring_action_timer(gpointer data)
> op->stdout_
Hi Andrew,
I applied three corrections that you made and checked movement.
I picked all "abort" processing with g_source_remove() of services.c just to
make sure.
* I set following "abort" in four places that carried out g_source_remove
>>> if (g_source_remove(op->opaque->repeat_timer)
Hi Andrew,
Okay!
I test your patch.
And I inform you of a result.
Many thanks!
Hideo Yamauchi.
- Original Message -
> From: Andrew Beekhof
> To: renayama19661...@ybb.ne.jp; The Pacemaker cluster resource manager
>
> Cc:
> Date: 2014/10/10, Fri 10:47
> Subject: Re: [Pacemaker] [Pro
Hi Andrew,
Setting of gdb of the Ubuntu environment does not yet go well and I touch lrmd
and cannot acquire trace.
Please wait for this a little more.
But.. I let lrmd terminate abnormally when g_source_remove() of
cancel_recurring_action() returned FALSE.
-
gboolean
cancel_recurring_acti
Hi Andrew,
> Not quite. Returning FALSE from the callback also removes the source from
> glib.
> So your test case effectively removes t1 twice: once implicitly by returning
> FALSE in timer_func1() and then again explicitly in timer_func3()
Your opinion is right.
If Pacemaker repeats and do
Hi Andrew,
>> These problems seem to be due to a correction of next glib somehow or
> other.
>> *
> https://github.com/GNOME/glib/commit/393503ba5bdc7c09cd46b716aaf3d2c63a6c7f9c
>
> The glib behaviour on unbuntu seems reasonable, removing a source multiple
> times
> IS a valid error.
> I ne
Hi All,
When I move the next sample in RHEL6.5(glib2-2.22.5-7.el6) and
Ubuntu14.04(libglib2.0-0:amd64 2.40.0-2), movement is different.
* Sample : test2.c
{{{
#include
#include
#include
#include
guint t1, t2, t3;
gboolean timer_func2(gpointer data){
printf("TIMER EXPIRE!2\n");
Hi Andrew,
>> lrmd[1632]: error: crm_abort: crm_glib_handler: Forked child 1840 to
> record non-fatal assert at logging.c:73 : Source ID 51 was not found when
> attempting to remove it
>> lrmd[1632]: crit: crm_glib_handler: GLib: Source ID 51 was not found
> when attempting to remove it
>
Hi Andrew,
About a similar problem, we confirmed it in Pacemaker1.1.12.
The problem occurs in (glib2.40.0) in Ubuntu14.04.
lrmd[1632]: error: crm_abort: crm_glib_handler: Forked child 1840 to record
non-fatal assert at logging.c:73 : Source ID 51 was not found when attempting
to remove it
lr
Hi Alex,
Because recheck_timer moves by default every 15 minutes, state transition is
calculated in pengine.
-
{ XML_CONFIG_ATTR_RECHECK, "cluster_recheck_interval", "time",
"Zero disables polling. Positive values are an interval in seconds (unless
other SI units are specified. eg. 5min
Hi Andrew,
>> Is my understanding wrong?
>
> Without the above commit, the lrmd logs as 'paceamker_remoted' and
> pacemaker_remoted logs as 'lrmd'.
> We just needed to swap the two cases. Which is what the commit achieves.
Okay!
We use it with the thing which invalidated the commit mentioned
Hi Andrew,
Thank you for comments.
>> In the log of latest Pacemaker, the name of the lrmd process is output by
> the name of the pacemaker_remoted process.
>> We like that log is output by default as lrmd.
>
> I think you just need: https://github.com/beekhof/pacemaker/commit/ad083a8
But, I
Hi All,
In the log of latest Pacemaker, the name of the lrmd process is output by the
name of the pacemaker_remoted process.
We like that log is output by default as lrmd.
These names seem to be changed on a macro.
However, the option which even "configure" command changes this macro to does
not
Hi Andrew,
Thank you for comments.
> I'll file a bug against glib on RHEL6 so that it gets fixed there.
> Can you send me your simple reproducer program?
I make revision during practice of timer_func2() at the time
When timer_func2() is carried out, time-out of timer_func() is completed befor
Hi Andrew,
I confirmed it in various ways.
The conclusion varies in movement by a version of glib.
* The problem occurs in RHEL6.x.
* The problem does not occur in RHEL7.0.
And this problem is solved in glib of a new version.
A change of next glib seems to solve a problem in a new version.
*
Hi Andrew,
I confirmed some problems, but seem to be caused by the fact that
> an event
>>> occurs somehow or other in g_main_loop of lrmd in the period when it is
> shorter
>>> than a monitor.
>>>
>>> So if you create a trivial program with g_main_loop and a timer, and
> then chan
Hi Andrew,
Thank you for comments.
>> I confirmed some problems, but seem to be caused by the fact that an event
> occurs somehow or other in g_main_loop of lrmd in the period when it is
> shorter
> than a monitor.
>
> So if you create a trivial program with g_main_loop and a timer, and then
Hi All,
We confirmed that lrmd caused the time-out of the monitor when the time of the
system was revised.
When a system considers revision of the time when I used ntpd, it is a problem
very much.
We can confirm this problem in the next procedure.
Step1) Start Pacemaker in a single node.
[root
Hi Andrew,
>> Perhaps someone feels like testing this:
>> https://github.com/beekhof/pacemaker/commit/3df6aff
>>
>> Otherwise I'll do it on monday
I confirmed the output of the SNMP trap of the resource and the SNMP trap of
STONITH.
By your correction, the crm_mon command came to send trap.
Hi Andrew,
> Perhaps someone feels like testing this:
> https://github.com/beekhof/pacemaker/commit/3df6aff
>
> Otherwise I'll do it on monday
An immediate correction, thank you.
I confirm snmp by the end of Monday.
Many Thanks!
Hideo Yamauchi.
- Original Message -
> From: Andrew
Hi All,
We were going to confirm snmptrap function in crm_mon of Pacemaker1.1.12.
However, crm_mon does not seem to support a message for a new difference of cib.
void
crm_diff_update(const char *event, xmlNode * msg)
{
int rc = -1;
long now = time(NULL);
(snip)
if (crm_mail_to || sn
Hi Andrew,
Thank you for comennts.
> Please use bugs.clusterlabs.org in future.
> I'll follow up in bugzilla
Okay!
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/6/10, Andrew Beekhof wrote:
>
> On 9 Jun 2014, at 12:01 pm, renayama19661...@ybb.ne.jp wrote:
>
> > Hi All,
> >
> > I submitted
Hi All,
I submitted a problem in next bugziila in the past.
* https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2501
A similar phenomenon is generated in attrd of latest Pacemaker.
Step 1) Set the setting of the cluster as follows.
export PCMK_fail_fast=no
Step 2) Start a cluster.
St
Hi Andrew,
I confirmed movement at once.
Your patch solves a problem.
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/5/28, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > Perhaps try:
> >
> > diff --git a/attrd/commands.c b/attrd/commands.c
> > index 7f1b4b0..7342e23 100644
> > --- a/at
Hi Andrew,
> Perhaps try:
>
> diff --git a/attrd/commands.c b/attrd/commands.c
> index 7f1b4b0..7342e23 100644
> --- a/attrd/commands.c
> +++ b/attrd/commands.c
> @@ -464,6 +464,15 @@ attrd_peer_update(crm_node_t *peer, xmlNode *xml, bool
> filter)
>
> a->changed |= changed;
>
> + if
Hi Andrew,
> > I'd expect that block to hit this clause though:
> >
> > } else if(mainloop_timer_running(a->timer)) {
> > crm_info("Write out of '%s' delayed: timer is running", a->id);
> > return;
>
> Which point of the source code does the suggested code mentioned above re
Hi Andrew,
Thank you for comment.
> > --- attrd/command.c -
> > (snip)
> > /* this only involves cluster nodes. */
> > if(v->nodeid == 0 && (v->is_remote == FALSE)) {
> > if(crm_element_value_int(xml, F_ATTRD_HOST_ID, (int*)&v->nodeid) ==
> >0) {
> > /* Create the nam
Hi All,
The attrd_updater command ignores the "dampen" parameter and updates an
attribute.
Step1) Start one node.
[root@srv01 ~]# crm_mon -1 -Af
Last updated: Tue May 27 19:36:35 2014
Last change: Tue May 27 19:34:59 2014
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
Hi Andrew,
I registered a problem in Bugzilla.
And I attached a file of crm_report.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5213
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/5/15, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > >> Your config looks reasonable... almost certain
Hi Andrwe,
> Here we go:
>
> https://github.com/ClusterLabs/pacemaker-1.0/blob/master/README.md
>
> If any additional bugs are found in 1.0, we should create a new entry at
> bugs.clusterlabs.org, add it to the above README and as long as 1.1 is
> unaffected: close the bug as WONTFIX.
All
Hi Andrew,
> >> Your config looks reasonable... almost certainly a bug in the PE.
> >> Do you happen to have the relevant pengine input file available?
> >
> > Really?
>
> I would expect that:
>
> colocation rsc_colocation-master-1 INFINITY: msPostgresql:Master A-master
>
> would only promot
Hi Andrew,
Thank you for comments.
> > We do not want to be promoted to Master in the node that primitive resource
> > does not start.
> > Is there the setting of colocation and order which are not promoted to
> > Master of the Master node?
>
> Your config looks reasonable... almost certainly
Hi Andrew,
> > It is not necessary at all to revise it for Pacemaker1.0.
>
> Maybe we need to add KnownIssues.md to the repo for anyone thats slow to
> update.
> Are there any 1.0 bugs that really really need fixing or shall we move them
> all to the KnownIssues file?
That's a good idea.
In th
Hi Andrew,
Thank you for comments.
> Do you guys have any timeframe for moving away from 1.0.x?
> The 1.1 series is over 4 years old now and quite usable :-)
>
> There is really a (low) limit to how much effort I can put into support for
> it.
We gradually move from Pacemaker1.0 to Pacemaker1.
Hi All,
We assume special resource constitution.
Master of master-slave depends on primitive resource for the constitution.
We performed the setting that Master stopped becoming it in Slave node
experimentally.
location rsc_location-msStateful-1 msPostgresql \
rule $role="master" 20
Hi Andrew,
> > Okay.
> > I wish this problem is revised by the next release.
>
> crm_report?
I confirmed a problem again in PM1.2-rc1 and registered in Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5212
Towards Bugzilla, I attached the crm_report file.
Best Regards,
Hideo Yamauchi.
Hi Andrew,
Thank you for comment.
> > Is it responsibility of the resource agent side to prevent a state of these
> > plural Master?
>
> No.
>
> In this scenario, no nodes have quorum and therefor no additional instances
> should have been promoted. Thats the definition of "freeze" :)
> Even
Hi All,
We confirmed a problem when we performed "clean up" of the Master/Slave
resource in Pacemaker1.0.
When this problem occurs, "probe" processing is not carried out.
I registered the problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5211
In addition, I wrote the method
Hi Emmanuel,
> Why are you using ssh as stonith? i don't think the fencing is working
> because your nodes are in unclean state
No, STONITH is not carried out because all nodes lose quorum.
This is right movement of Pacemaker.
It is an example to use STONITH of ssh.
Best Regards,
Hideo Yamauch
Hi All,
I composed Master/Slave resource of three nodes that set quorum-policy="freeze".
(I use Stateful in Master/Slave resource.)
-
Current DC: srv01 (3232238280) - partition with quorum
Version: 1.1.11-830af67
3 Nodes configured
9 Resources configured
Online:
Hi All,
I made a patch.
Please confirm the contents of the patch.
If there is not a problem, please reflect it in github.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/2/20, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> The timer which is not stopped at the time of the stop of the monitor
Hi All,
The timer which is not stopped at the time of the stop of the monitor of the
master slave resource of the local node runs.
Therefore, warning to cancel outputs a timer when crmd handles the transition
that is in a new state.
I confirm it in the next procedure.
Step1) Constitute a clust
Hi Andrew,
> > I wish it is displayed as follows.
> >
> >
> > * Node srv01:
> > + default_ping_set : 0 : Connectivity is
> >lost
>
> Ah! https://github.com/beekhof/pacemaker/commit/5d51930
It was displayed definitely.
Many Thanks!
Hideo Yamauchi.
--- On Wed
Hi Andrew,
Thank you for comments.
> So I'm confused as to what the problem is.
> What are you expecting crm_mon to show?
I wish it is displayed as follows.
* Node srv01:
+ default_ping_set : 0 : Connectivity is lost
Best Regards,
Hideo Yamauchi.
--- On Wed, 2
Hi Andrew,
> I'll follow up on the bug.
Thanks!
Hideo Yamauch.
--- On Wed, 2014/2/19, Andrew Beekhof wrote:
> I'll follow up on the bug.
>
> On 19 Feb 2014, at 10:55 am, renayama19661...@ybb.ne.jp wrote:
>
> > Hi David,
> >
> > Thank you for comments.
> >
> >> You have resource-stickiness
Hi David,
Thank you for comments.
> You have resource-stickiness=INFINITY, this is what is preventing the
> failover from occurring. Set resource-stickiness=1 or 0 and the failover
> should occur.
>
However, the resource moves by a calculation of the next state transition.
By a calculation of
Hi Andrew,
I attach the result of the cibadmin -Q command.
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/2/18, Andrew Beekhof wrote:
>
> On 18 Feb 2014, at 1:45 pm, renayama19661...@ybb.ne.jp wrote:
>
> > Hi Andrew,
> >
> > Thank you for comments.
> >
> >> can I see the config of yours t
Hi Andrew,
Thank you for comments.
> can I see the config of yours that crm_mon is not displaying correctly?
It is displayed as follows.
-
[root@srv01 tmp]# crm_mon -1 -Af
Last updated: Tue Feb 18 19:51:04 2014
Last change: Tue Feb 18 19:48:55 2014 via
Hi Andrew,
> I'm confused... that patch seems to be the reverse of yours.
> Are you saying that we need to undo Lars' one?
No, I do not understand the meaning of the correction of Mr. Lars.
However, as now, crm_mon does not display a right attribute.
Possibly did you not discuss the correction t
Hi All,
I confirmed movement at the time of the trouble in one of Master/Slave in
Pacemaker1.1.11.
-
Step1) Constitute a cluster.
[root@srv01 ~]# crm_mon -1 -Af
Last updated: Tue Feb 18 18:07:24 2014
Last change: Tue Feb 18 18:05:46 2014 via crmd on srv01
St
Hi All,
The next change was accomplished by Mr. Lars.
https://github.com/ClusterLabs/pacemaker/commit/6a17c003b0167de9fe51d5330fb6e4f1b4ffe64c
I may lack the correction of other parts which are not the patch which I sent.
Best Regards,
Hideo Yamauchi.
--- On Mon, 2014/2/17, renayama19661...@
Hi All,
The crm_mon tool which is attached to Pacemaker1.1 seems to have a problem.
I send a patch.
Best Regards,
Hideo Yamauchi.
trac2781.patch
Description: Binary data
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.o
Hi Andrew,
> >> Is this related to your email about symmetrical not being defaulted
> >> consistently between colocate_rsc_sets() and unpack_colocation_set()?
> >
> > Yes.
> > I think that a default is not handled well.
> > I will not have any problem when "sequential" attribute is set in cib by
Hi Andrew,
I found your correction.
https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/2/12, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> There is difference in two between handling of "sequential" of "resouc
Hi Andrew,
Thank you for comments.
> Is this related to your email about symmetrical not being defaulted
> consistently between colocate_rsc_sets() and unpack_colocation_set()?
Yes.
I think that a default is not handled well.
I will not have any problem when "sequential" attribute is set in cib
Hi Kristoffer,
Thank you for comments.
> > But the next information appeared when I put crm.
> > Does this last message not have any problem?
> >
> > ---
> > [root@srv01 ~]# crm configure load update
> > db2-resource_set_0207.crm WARNING: pgsql: action monitor not
> >
Hi Kristoffer,
Thank you for comments.
By crmsh-7f620e736895.tar.gz, I did "make install" well.
I seem to be able to set the sequential attribute definitely.
The sequential attribute does become true.
---
(snip)
colocation rsc_colocation-master INFINITY: [ vip-maste
Hi Kristoffer,
Thank you for comments.
> Could you try with the latest changeset 337654e0cdc4?
However, the problem seems to still occur.
[root@srv01 crmsh-337654e0cdc4]# make install
Making install in doc
make[1]: Entering directory `/opt/crmsh-337654e0cdc4/doc'
a2x -f manpage crm.8.txt
WARNIN
Hi All,
There is difference in two between handling of "sequential" of "resouce_set" of
colocation.
Is either one not a mistake?
static gboolean
unpack_colocation_set(xmlNode * set, int score, pe_working_set_t * data_set)
{
xmlNode *xml_rsc = NULL;
resource_t *w
Hi Kristoffer,
Thank you for comments.
I tested it.
However, the problem seems to still occur.
---
[root@srv01 crmsh-8d984b138fc4]# pwd
/opt/crmsh-8d984b138fc4
[root@srv01 crmsh-8d984b138fc4]# ./autogen.sh
autoconf: autoconf (GNU Autoconf) 2.63
aut
Hi Kristoffer,
In RHEL6.4, crmsh-c8f214020b2c gives the next error and cannot install it.
Does a procedure of any installation have a problem?
---
[root@srv01 crmsh-c8f214020b2c]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Hi Kristoffer.
Thank you for comments.
We wait for a correction.
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/2/5, Kristoffer Grönlund wrote:
> On Wed, 5 Feb 2014 15:55:42 +0900 (JST)
> renayama19661...@ybb.ne.jp wrote:
>
> > Hi All,
> >
> > We tried to set sequential attribute of resource
Hi All,
We tried to set sequential attribute of resource_set of colocation in true in
crmsh.
We tried the next method, but true was not able to set it well.
-
[pengine]# crm --version
2.0 (Build 7cd5688c164d2949009accc7f172ce559cadbc4b)
- Pattern 1 -
colocation rsc_colocat
Hi Andrew,
It became late.
I registered this problem by Bugzilla.
The report file is attached, too.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5194
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/1/14, Andrew Beekhof wrote:
>
> On 14 Jan 2014, at 4:33 pm, renayama19661...@ybb.ne.jp wrote:
Hi All,
My test seemed to include a mistake.
It seems to be replaced by two limitation.
> However, I think that symmetircal="false" is applied to all order limitation
> in this.
> (snip)
>
>
>
>
>
>
> ...
>
>
Hi All,
We confirm a function of resource_set.
There were the resource of the group and the resource of the clone.
(snip)
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
Version: 1.1.10-f2d0cbc
1 Nodes configured
7 Resources configured
Online: [ srv01 ]
Resource Gro
Hi Andrew,
Sorry
This problem is a thing of Pacemaker1.0.
On Pacemaker1.1.11, the resource did movement to stop definitely.
When "globally-unique" attribute changed somehow or other in Pacemaker1.1,
Pacemkaer seems to carry out the reboot of the resource.
(snip)
Jan 15 18:29:40 rh64-2744 p
Hi Andrew,
Thank you for comment.
> > But, the resource does not stop because PID file was changed as for the
> > changed resource of the "globally-unique" attribute.
>
> I'd have expected the stop action to be performed with the old attributes.
> crm_report tarball?
Okay.
I register this top
Hi All,
When a user changes the "globally-unique" attribute of the resource, a problem
occurs.
When it manages the resource with PID file, this occurs, but this is because
PID file name changes by "globally-unique" attribute.
(snip)
if [ ${OCF_RESKEY_CRM_meta_globally_unique} = "false" ]; then
Hi Andrew,
> >> Are you using the new attrd code or the legacy stuff?
> >
> > I use new attrd.
>
> And the values are not being sent to the cib at the same time?
As far as I looked. . .
When the transmission of the attribute of attrd of the node was late, a leader
of attrd seemed to send an a
Hi Andrew,
Thank you for comments.
> Are you using the new attrd code or the legacy stuff?
I use new attrd.
>
> If you're not using corosync 2.x or see:
>
> crm_notice("Starting mainloop...");
>
> then its the old code. The new code could also be used with CMAN but isn't
> configured t
Hi All,
I contributed next bugzilla by a problem to occur for the difference of the
timing of the attribute update by attrd before.
* https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2528
We can evade this problem now by using crmd-transition-delay parameter.
I confirmed whether I cou
Hi Andrew,
Hi Takatsuka san,
What kind of procedure did the problem that became this problem cause it in?
If a problem easily happens in the environment of the user, we think that it is
necessary to contact a user using Pacemaker1.0.13.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/11/14, TAKA
Hi Andrew,
I confirmed that a problem was solved in a revision.
Thanks!
Hideo Yamauchi.
--- On Wed, 2013/9/4, Andrew Beekhof wrote:
> Thanks (also to Andreas for sending me an example too)!
>
> Fixed:
> https://github.com/beekhof/pacemaker/commit/a32474b
>
> On 04/09/2013, at 11:02 AM, re
Hi Andrew,
> > > Though the trouble is only once, two error information is displayed in
> > > crm_mon.
> >
> > Have you got the full cib for when crm_mon is showing this?
>
> No.
> I reproduce a problem once again and acquire cib.
I send the result that I acquired by cibadmin -Q command.
Best
Hi Andrew,
> > Hi All,
> >
> > Though the trouble is only once, two error information is displayed in
> > crm_mon.
>
> Have you got the full cib for when crm_mon is showing this?
No.
I reproduce a problem once again and acquire cib.
Best Regards,
Hideo Yamauchi.
_
Hi Andres,
Thank you for comment.
> But to be seriously: I see this phaenomena, too.
> (pacemaker 1.1.11-1.el6-4f672bc)
If the version that you confirm is the same as next, probably it will be that
the same problem happens.
There is a similar cord.
(https://github.com/ClusterLabs/pacemaker/blob
Hi All,
Though the trouble is only once, two error information is displayed in crm_mon.
-
[root@rh64-coro2 ~]# crm_mon -1 -Af
Last updated: Thu Aug 29 18:11:00 2013
Last change: Thu Aug 29 18:10:45 2013 via cibadmin on rh64-coro2
Stack: corosync
Current DC
Hi Andrew,
> Yep, sounds like a problem.
> I'll follow up on bugzilla
All right!
Many Thanks!
Hideo Yamauchi.
--- On Tue, 2013/6/4, Andrew Beekhof wrote:
>
> On 04/06/2013, at 3:00 PM, renayama19661...@ybb.ne.jp wrote:
>
> >
> > It is right movement that recognize other nodes in a UNCLEAN
Hi All,
I registered this problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5160
Best Regards,
Hideo Yamauchi.
--- On Tue, 2013/6/4, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> We confirmed a state of the recognition of the cluster in the next procedure.
> We confirm
Hi All,
We confirmed a state of the recognition of the cluster in the next procedure.
We confirm it by the next combination.(RHEL6.4 guest)
* corosync-2.3.0
* pacemaker-Pacemaker-1.1.10-rc3
-
Step 1) Start all nodes and constitute a cluster.
[root@rh64-coro1 ~]# crm_mo
Hi Andrew,
I registered a demand with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5158
Many Thanks!
Hideo Yamauchi.
--- On Fri, 2013/5/24, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > > To Andrew :
> > > If you make a patch removing a block of the file handling of pengi
Hi Andrew,
> > To Andrew :
> > If you make a patch removing a block of the file handling of pengine, I
> > confirm the movement.
> > If a problem is evaded without using tmpfs, many users welcome it.
> >
>
> You mean this patch? https://github.com/beekhof/pacemaker/commit/c7e10c6
> Or another
Hi Andrew,
Hi Vladislav,
> We test movement when we located pe file in tmpfs repeatedly.
> It seems to move well for the moment.
I only adopted tmpfs, and the I/O block of pengine was improved.
I confirm the synchronization with the fixed file, but think that there is not
the problem from now on
Hi Andrew,
Hi Vladislav,
We test movement when we located pe file in tmpfs repeatedly.
It seems to move well for the moment.
I confirm movement a little more, and we are going to try the method that Mr.
Vladislav synchronizes.
Best Regards,
Hideo Yamauchi.
--- On Wed, 2013/5/22, Andrew Beekhof
Hi Vladislav,
> For just this, patch is unneeded. It only plays when you have that
> pengine files symlinked from stable storage to tmpfs, Without patch,
> pengine would try to rewrite file where symlink points it - directly on
> a stable storage. With that patch, pengine will remove symlink (and
Hi Vladislav,
Thank you for advice.
I try the patch which you showed.
We use Pacemaker1.0, but apply a patch there because there is a similar code.
If there is a question by setting, I ask you a question by an email.
* At first I only use tmpfs, and I intend to test it.
> P.S. Andrew, is this
Hi Andrew,
Hi Vladislav,
I try whether this correction is effective for this problem.
*
https://github.com/beekhof/pacemaker/commit/eb6264bf2db395779e65dadf1c626e050a388c59
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/5/16, Andrew Beekhof wrote:
>
> On 16/05/2013, at 3:49 PM, Vladislav Bo
Hi Andrew,
> > Thank you for comments.
> >
> >>> The guest located it to the shared disk.
> >>
> >> What is on the shared disk? The whole OS or app-specific data (i.e.
> >> nothing pacemaker needs directly)?
> >
> > Shared disk has all the OS and the all data.
>
> Oh. I can imagine that bein
Hi Andrew,
Thank you for comments.
> > The guest located it to the shared disk.
>
> What is on the shared disk? The whole OS or app-specific data (i.e. nothing
> pacemaker needs directly)?
Shared disk has all the OS and the all data.
The placement of this shared disk is similar in KVM where t
Hi All,
We constituted a simple cluster in environment of vSphere5.1.
We composed it of two ESXi servers and shared disk.
The guest located it to the shared disk.
Step 1) Constitute a cluster.(A DC node is an active node.)
Last updated: Mon May 13 14:16:09 2013
Stack: Heartbeat
C
1 - 100 of 376 matches
Mail list logo
