On 04.02.2016 15:43, Bogdan Dobrelya wrote:
> Hello.
> Regarding the original issue, good news are the resource-agents
> ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0]
> after the fix [1] done. The bad news are that "self-forking" monitors
> issue seems remaining for the rabbi
Hello.
Regarding the original issue, good news are the resource-agents
ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0]
after the fix [1] done. The bad news are that "self-forking" monitors
issue seems remaining for the rabbitmq OCF RA [2], and I can reproduce
it for another cus
Hi,
2016-01-06 22:57 GMT+09:00 Jan Pokorný :
> Hello ,
>
> On 04/01/16 17:33 +0100, Bogdan Dobrelya wrote:
>> Note, that it seems the very import action causes the issue, not the
>> ocf_run or ocf_log code itself.
>>
>> [0] https://github.com/ClusterLabs/resource-agents/issues/734
>
> Have to won
Hello ,
On 04/01/16 17:33 +0100, Bogdan Dobrelya wrote:
> On 04.01.2016 17:14, Dejan Muhamedagic wrote:
>> Hi,
>>
>> On Mon, Jan 04, 2016 at 04:52:43PM +0100, Bogdan Dobrelya wrote:
>>> On 04.01.2016 16:36, Ken Gaillot wrote:
On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
> On 04.01.2016
On 04.01.2016 17:14, Dejan Muhamedagic wrote:
> Hi,
>
> On Mon, Jan 04, 2016 at 04:52:43PM +0100, Bogdan Dobrelya wrote:
>> On 04.01.2016 16:36, Ken Gaillot wrote:
>>> On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
On 04.01.2016 15:50, Bogdan Dobrelya wrote:
> [...]
Also note, that lrmd
Hi,
On Mon, Jan 04, 2016 at 04:52:43PM +0100, Bogdan Dobrelya wrote:
> On 04.01.2016 16:36, Ken Gaillot wrote:
> > On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
> >> On 04.01.2016 15:50, Bogdan Dobrelya wrote:
[...]
> >> Also note, that lrmd spawns *many* monitors like:
> >> root 6495 0.0
On 04.01.2016 16:36, Ken Gaillot wrote:
> On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
>> On 04.01.2016 15:50, Bogdan Dobrelya wrote:
>>> So far so bad.
>>> I made a dummy OCF script [0] to simulate an example
>>> promote/demote/notify failure mode for a multistate clone resource which
>>> is ver
On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
> On 04.01.2016 15:50, Bogdan Dobrelya wrote:
>> So far so bad.
>> I made a dummy OCF script [0] to simulate an example
>> promote/demote/notify failure mode for a multistate clone resource which
>> is very similar to the one I reported originally. And
On 04.01.2016 15:50, Bogdan Dobrelya wrote:
> So far so bad.
> I made a dummy OCF script [0] to simulate an example
> promote/demote/notify failure mode for a multistate clone resource which
> is very similar to the one I reported originally. And the test to
> reproduce my case with the dummy is:
>
On 01/04/2016 08:50 AM, Bogdan Dobrelya wrote:
> So far so bad.
> I made a dummy OCF script [0] to simulate an example
> promote/demote/notify failure mode for a multistate clone resource which
> is very similar to the one I reported originally. And the test to
> reproduce my case with the dummy is
So far so bad.
I made a dummy OCF script [0] to simulate an example
promote/demote/notify failure mode for a multistate clone resource which
is very similar to the one I reported originally. And the test to
reproduce my case with the dummy is:
- install dummy resource ocf ra and create the dummy re
On 01.01.2016 11:34, Vladislav Bogdanov wrote:
> 31.12.2015 15:33:45 CET, Bogdan Dobrelya wrote:
>> On 31.12.2015 14:48, Vladislav Bogdanov wrote:
>>> blackbox tracing inside pacemaker, USR1, USR2 and TRAP signals iirc,
>> quick google search should point you to Andrew's blog with all
>> informati
31.12.2015 15:33:45 CET, Bogdan Dobrelya wrote:
>On 31.12.2015 14:48, Vladislav Bogdanov wrote:
>> blackbox tracing inside pacemaker, USR1, USR2 and TRAP signals iirc,
>quick google search should point you to Andrew's blog with all
>information about that feature.
>> Next, if you use ocf-shellfunc
On 31.12.2015 14:48, Vladislav Bogdanov wrote:
> blackbox tracing inside pacemaker, USR1, USR2 and TRAP signals iirc, quick
> google search should point you to Andrew's blog with all information about
> that feature.
> Next, if you use ocf-shellfuncs in your RA, you could enable tracing for
> re
31.12.2015 12:57:45 CET, Bogdan Dobrelya wrote:
>Hello.
>I've been hopelessly fighting a bug [0] in the custom OCF agent of Fuel
>for OpenStack project. It is related to the destructive test case when
>one node of 3 or 5 total goes down and then back. The bug itself is
>tricky (is rarely reproduce
Hello.
I've been hopelessly fighting a bug [0] in the custom OCF agent of Fuel
for OpenStack project. It is related to the destructive test case when
one node of 3 or 5 total goes down and then back. The bug itself is
tricky (is rarely reproduced), tl;dr, and has many duplicates. So I only
put here
16 matches
Mail list logo
