[Pacemaker] PE-Engine-Processing

[Andrew Beekhof]

On Jan 17, 2008, at 11:14 PM, Andreas Mock wrote:

> Hi Lars,
>
> thank you for your quick reply.
>
> I saw the graphics at http://clusterlabs.org/#Architecture and  
> therefore
> thought that PE related questions belong to CRM et altera.
> Sorry for posting to the wrong place.

No need to apologize,  lmb and I just need to get our stories  
straight :-)

I'll continue to also answer pacemaker/crm questions on linux-ha but,  
personally, I'd prefer questions to be sent to this list.
Particularly since not everyone will be using the heartbeat stack  
anymore.


In answer to your original question, yeah, there will have been some  
errors earlier on that might make this particular input "interesting"  
to an admin/debugger at a later point.
So it saves it as pe-warn-* (instead of pe-input-*) and logs that  
message.

> But probably I'm just the first one doing it wrong.
> Please announce where to post the right questions to not seperating
> the HA community. :-)
>
> Best regards
> Andreas Mock
>
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: pacemaker-bounces at clusterlabs.org
>> [mailto:pacemaker-bounces at clusterlabs.org] Im Auftrag von
>> Lars Marowsky-Bree
>> Gesendet: Donnerstag, 17. Januar 2008 23:05
>> An: The Pacemaker cluster resource manager
>> Betreff: Re: [Pacemaker] PE-Engine-Processing
>>
>>
>> On 2008-01-17T22:56:27, Andreas Mock <Andreas.Mock at web.de> wrote:
>>
>>> Hi all, hi Andrew,
>>>
>>> HAv2 (2.1.2 or 2.1.3): When I find messages like the
>> following in the log file:
>>
>> That doesn't appear pacemaker-specific, please don't split the lists
>> unnecessarily.
>>
>>
>>> --------------------------8<---------------------------------------
>>> Jan 17 22:27:02 dis01 pengine: [18830]: WARN:
>> process_pe_message: Transition 1: WARNINGs found during PE
>> processing. PEngine Input
>>> stored in: /var/lib/heartbeat/pengine/pe-warn-35.bz2
>>> Jan 17 22:27:02 dis01 pengine: [18830]: info:
>> process_pe_message: Configuration WARNINGs found during PE
>> processing.  Please run
>>> "crm_verify -L" to identify issues.
>>
>> Usually, there should be something in the logs above it which
>> indicates
>> why.
>>
>>> --------------------------8<---------------------------------------
>>>
>>> what do I have to do?
>>> a) Take pe-warn-35.bz2, unzip it and push it through
>> 'crm_verify -VVVVV -x pe-warn-35'?
>>> b) Or make a plain 'crm_verify -L -VVVVV'?
>>>
>>> In both cases I don't get a hint why I got a warning
>> message in the logs.
>>> What do I have to do to find the related "WARNINGS"
>> mentioned by the transition?
>>
>> Of course, you can also try ptest -VVVVVV and see what that tells  
>> you,
>> which is the PE by another name.
>>
>>
>>
>> Regards,
>>    Lars
>>
>> -- 
>> Teamlead Kernel, SuSE Labs, Research and Development
>> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
>> "Experience is the name everyone gives to their mistakes." --
>> Oscar Wilde
>>
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at clusterlabs.org
>> http://list.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> __________ NOD32 2802 (20080117) Information __________
>>
>> Diese E-Mail wurde vom NOD32 antivirus system geprüft
>> http://www.nod32.com
>>
>>
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker