On 10/08/2013, at 12:36 AM, Andrew Martin wrote:
> - Original Message -
>> From: "Andrew Beekhof"
>> To: "The Pacemaker cluster resource manager"
>> Sent: Thursday, August 8, 2013 7:42:22 PM
>> Subject: Re: [Pacemaker] Announce: Pacemake
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Thursday, August 8, 2013 7:42:22 PM
> Subject: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
>
>
> On 08/08/2013, at 11:48 PM, Andr
On 08/08/2013, at 11:48 PM, Andrew Martin wrote:
> - Original Message -
>> From: "Andrew Beekhof"
>> To: "The Pacemaker cluster resource manager"
>> Sent: Thursday, August 8, 2013 2:35:53 AM
>> Subject: Re: [Pacemaker] Announce: Pacemake
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Thursday, August 8, 2013 2:35:53 AM
> Subject: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
>
>
> On 08/08/2013, at 5:13 PM, Vladi
On 08/08/2013, at 5:13 PM, Vladislav Bogdanov wrote:
> 26.07.2013 03:43, Andrew Beekhof wrote:
>
> ...
>
>> Release candidates for the next Pacemaker release (1.1.11) can be
>> expected some time around Novemeber.
>
> Did you completely discard plan of releasing 2.0.0?
Short answer, yes.
We'
26.07.2013 03:43, Andrew Beekhof wrote:
...
> Release candidates for the next Pacemaker release (1.1.11) can be
> expected some time around Novemeber.
Did you completely discard plan of releasing 2.0.0?
___
Pacemaker mailing list: Pacemaker@oss.clust
For RHEL5 you'll probably want to revert the following patch:
https://github.com/beekhof/pacemaker/commit/a81d222
On 31/07/2013, at 1:44 AM, Kirill Proskurin wrote:
> Quick follow-up
>
> I add --enable-fatal-warnings=no
> And now make start to work.
>
> I see a lot of
> ../../include/portab
in due course there will be 1.1.11 as happens for any other bug that is
fixed after a release.
>
> Rainer
> Gesendet: Donnerstag, 01. August 2013 um 05:56 Uhr
> Von: "Takatoshi MATSUO"
> An: "The Pacemaker cluster resource manager"
> Betreff: Re: [Pacemak
operation
Will there be a new tag (like 1.1.10-2) for version 1.1.10 with applied patch ?
Rainer
Gesendet: Donnerstag, 01. August 2013 um 05:56 Uhr
Von: "Takatoshi MATSUO"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now av
Pacemaker on int2node2
>>>> https://www.dropbox.com/s/s3jnxqvod9mlyz1/step2.log.tar.bz2
>>>> monitor on master is not called any more
>>>>
>>>> 3.) 19:37:14 stop Pacemaker on int2node2
>>>> https://www.dropbox.com/s/w75myab6fxh7mak/step3.log.tar
md[16444] notice: notice:
>>>> peer_update_callback: do_shutdown of int2node2 (op 45) is complete
>>>>
>>>> Output from RA on int2node1:
>>>> Wed Jul 31 08:30:52 CEST 2013 resABC: operation notify, type pre,
>>>> operation start
>>>>
/s/p00wl9kx4vwhilh/step4.log.tar.bz2
>> monitor on master is called normally
>>
>> Hope this gives a clearer picture which component has forgotten the monitor
>> action.
>>
>> Rainer
>> Gesendet: Mittwoch, 31. Juli 2013 um 14:19 Uhr
>>
>> Von:
t; action.
>
> Rainer
> Gesendet: Mittwoch, 31. Juli 2013 um 14:19 Uhr
>
> Von: "Andrew Beekhof"
> An: "The Pacemaker cluster resource manager"
> Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
>
> On 31/07/2013, at 5:17 PM, Rainer Bres
ture which component has forgotten the monitor action.
Rainer
Gesendet: Mittwoch, 31. Juli 2013 um 14:19 Uhr
Von: "Andrew Beekhof"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
On 31/07/2013, at 5:17 PM, Rainer B
On 7/31/13 16:17 , Andrew Beekhof wrote:
On 31/07/2013, at 6:28 PM, Kirill Proskurin wrote:
On 7/31/13 03:51 , Andrew Beekhof wrote:
On 31/07/2013, at 1:44 AM, Kirill Proskurin wrote:
Quick follow-up
I add --enable-fatal-warnings=no
And now make start to work.
I see a lot of
../../incl
On 31/07/2013, at 6:28 PM, Kirill Proskurin wrote:
> On 7/31/13 03:51 , Andrew Beekhof wrote:
>>
>> On 31/07/2013, at 1:44 AM, Kirill Proskurin wrote:
>>
>>> Quick follow-up
>>>
>>> I add --enable-fatal-warnings=no
>>> And now make start to work.
>>>
>>> I see a lot of
>>> ../../include/por
n
> Wed Jul 31 08:36:33 CEST 2013 resABC: operation monitor, type , operation
> Wed Jul 31 08:36:53 CEST 2013 resABC: operation monitor, type , operation
> Wed Jul 31 08:37:13 CEST 2013 resABC: operation monitor, type , operation
> Wed Jul 31 08:37:33 CEST 2013 resABC: operation monitor, ty
On 7/31/13 03:51 , Andrew Beekhof wrote:
On 31/07/2013, at 1:44 AM, Kirill Proskurin wrote:
Quick follow-up
I add --enable-fatal-warnings=no
And now make start to work.
I see a lot of
../../include/portability.h:165: warning: implicit declaration of function
'strcmp'
warnings, but all wer
13 resABC: operation notify, type post, operation stop
After 08:37:51 no log output from Pacemaker for resABC, nor any output from RA on int2node1.
Gesendet: Mittwoch, 31. Juli 2013 um 02:10 Uhr
Von: "Andrew Beekhof"
An: "The Pacemaker cluster resource manager"
Betreff:
; An: "The Pacemaker cluster resource manager"
> Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
> Hi
>
> I used Stateful RA and caught a same issue.
>
> 1. before starting slave
>
> # crm_simulate -VVV -S -x /var/lib/pacemaker/pengine/pe-input-
On 26/07/2013, at 12:21 PM, Takatoshi MATSUO wrote:
> Hi
>
> My report is late for 1.1.10 :(
>
> I am using pacemaker 1.1.10-0.1.ab2e209.git.
> It seems that master's monitor is stopped when slave is started.
Where the master and slave are on different machines?
Can you include a crm_report a
On 30/07/2013, at 11:04 PM, Kirill Proskurin wrote:
> On 7/30/13 05:51 , Andrew Beekhof wrote:
>>
>> On 29/07/2013, at 10:37 PM, Kirill Proskurin
>> wrote:
>>
>>> On 7/29/13 03:50 , Andrew Beekhof wrote:
On 26/07/2013, at 8:20 PM, Kirill Proskurin
wrote:
> Hi!
>>>
On 31/07/2013, at 1:44 AM, Kirill Proskurin wrote:
> Quick follow-up
>
> I add --enable-fatal-warnings=no
> And now make start to work.
>
> I see a lot of
> ../../include/portability.h:165: warning: implicit declaration of function
> 'strcmp'
>
> warnings, but all were ok before this:
>
> h
; error
> 1.1.10-rc5 -> no error
> 1.1.10-rc6 -> no error
> 1.1.10-rc7 -> no error
> 1.1.10-1 -> error
>
> Rainer
> Gesendet: Freitag, 26. Juli 2013 um 09:32 Uhr
> Von: "Takatoshi MATSUO"
> An: "The Pacemaker cluster resource manager"
>
Quick follow-up
I add --enable-fatal-warnings=no
And now make start to work.
I see a lot of
../../include/portability.h:165: warning: implicit declaration of
function 'strcmp'
warnings, but all were ok before this:
http://www.fpaste.org/29029/97867137/
There is no sygnalfd.h in Centos5 (2.6
On 7/30/13 05:51 , Andrew Beekhof wrote:
On 29/07/2013, at 10:37 PM, Kirill Proskurin wrote:
On 7/29/13 03:50 , Andrew Beekhof wrote:
On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
Hi!
Is it RHEL5.x friendly?
I'm assuming yes, as no-one complained during the 3 month release candid
.1.10-rc7 -> no error
1.1.10-1 -> error
Rainer
Gesendet: Freitag, 26. Juli 2013 um 09:32 Uhr
Von: "Takatoshi MATSUO"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
Hi
I used Stateful RA and caugh
On 30/07/13 02:51, Andrew Beekhof wrote:
>> [k.proskurin@video-build libqb]$ ./autogen.sh
>> > autoreconf: Entering directory `.'
>> > autoreconf: configure.ac: not using Gettext
>> > autoreconf: running: aclocal -I m4
>> > configure.ac:4: error: Autoconf version 2.61 or higher is required
>> >
>>
On 29/07/2013, at 10:37 PM, Kirill Proskurin wrote:
> On 7/29/13 03:50 , Andrew Beekhof wrote:
>>
>> On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
>>
>>> Hi!
>>>
>>> Is it RHEL5.x friendly?
>>
>> I'm assuming yes, as no-one complained during the 3 month release candidate
>> phase ;-)
On 7/29/13 03:50 , Andrew Beekhof wrote:
On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
Hi!
Is it RHEL5.x friendly?
I'm assuming yes, as no-one complained during the 3 month release candidate
phase ;-)
Look like it's not.
[k.proskurin@video-build pacemaker]$ make release
sort: inva
On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
> Hi!
>
> Is it RHEL5.x friendly?
I'm assuming yes, as no-one complained during the 3 month release candidate
phase ;-)
>
> On 7/26/13 04:43 , Andrew Beekhof wrote:
>> Announcing the release of Pacemaker 1.1.10
>>
>>https://github.com/
Hi!
Is it RHEL5.x friendly?
On 7/26/13 04:43 , Andrew Beekhof wrote:
Announcing the release of Pacemaker 1.1.10
https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.10
--
Best regards,
Proskurin Kirill
___
Pacemaker mailing list: Pa
Hi
I used Stateful RA and caught a same issue.
1. before starting slave
# crm_simulate -VVV -S -x /var/lib/pacemaker/pengine/pe-input-1543.bz2
| grep "Resource action"
* Resource action: statefulmonitor=2000 on 16-sl6
2. starting slave
# crm_simulate -VVV -S -x /var/lib/pacemaker/peng
Hi
My report is late for 1.1.10 :(
I am using pacemaker 1.1.10-0.1.ab2e209.git.
It seems that master's monitor is stopped when slave is started.
Does someone encounter same problem ?
I attach a log and settings.
Thanks,
Takatoshi MATSUO
2013/7/26 Digimer :
> Congrats!! I know this was a long
Congrats!! I know this was a long time in the making.
digimer
On 25/07/13 20:43, Andrew Beekhof wrote:
Announcing the release of Pacemaker 1.1.10
https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.10
There were three changes of note since rc7:
+ Bug cl#5161 - crmd: Preven
Announcing the release of Pacemaker 1.1.10
https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.10
There were three changes of note since rc7:
+ Bug cl#5161 - crmd: Prevent memory leak in operation cache
+ cib: Correctly read back archived configurations if the primary is corru
36 matches
Mail list logo
