[Pacemaker] 1) attrd, crmd, cib, stonithd going to 100% CPU after standby 2) monitoring bug 3) meta failure-timeout issue

[Proskurin Kirill]

On 10/05/2011 04:19 AM, Andrew Beekhof wrote:
> On Mon, Oct 3, 2011 at 5:50 PM, Proskurin Kirill
> <k.proskurin at corp.mail.ru>  wrote:
>> On 10/03/2011 05:32 AM, Andrew Beekhof wrote:
>>>>
>>>> corosync-1.4.1
>>>> pacemaker-1.1.5
>>>> pacemaker runs with "ver: 1"
>>
>>>> 2)
>>>> This one is scary.
>>>> I twice run on situation then pacemaker thinks what resource is started
>>>> but
>>>> it is not.
>>>
>>> RA is misbehaving.  Pacemaker will only consider a resource running if
>>> the RA tells us it is (running or in a failed state).
>>
>> But you can see below, what agent return "7".
>
> Its still broken. Not one stop action succeeds.
>
> Sep 30 13:58:41 mysender34.mail.ru lrmd: [26299]: WARN:
> tranprocessor:stop process (PID 4082) timed out (try 1).  Killing with
> signal SIGTERM (15).
> Sep 30 14:09:34 mysender34.mail.ru lrmd: [26299]: WARN:
> tranprocessor:stop process (PID 21859) timed out (try 1).  Killing
> with signal SIGTERM (15).
> Sep 30 20:04:17 mysender34.mail.ru lrmd: [26299]: WARN:
> tranprocessor:stop process (PID 24576) timed out (try 1).  Killing
> with signal SIGTERM (15).
>
> /That/ is why pacemaker thinks its still running.

Hm, I think in this situation it must become unmanaged, no?

-- 
Best regards,
Proskurin Kirill