[ClusterLabs] Antw: Re: [Question] About movement of pacemaker_remote.

[Ulrich Windl]

>>> Andrew Beekhof <andrew at beekhof.net> schrieb am 30.03.2015 um 02:17 in Nachricht
<1243B3D8-F864-4AA4-AEED-10A9D93315A3 at beekhof.net>:

>> On 14 Mar 2015, at 10:14 am, David Vossel <dvossel at redhat.com> wrote:
>> 
>> 
>> 
>> ----- Original Message -----
>>> 
>>> Failed actions:
>>>     snmp2_start_0 on sl7-01 'unknown error' (1): call=8, status=Timed Out,
>>>     exit-reason='none', last-rc-change='Thu Mar 12 14:26:26 2015',
>>>     queued=0ms, exec=0ms
>>>     snmp2_start_0 on sl7-01 'unknown error' (1): call=8, status=Timed Out,
>>>     exit-reason='none', last-rc-change='Thu Mar 12 14:26:26 2015',
>>>     queued=0ms, exec=0ms
>>> -----------------------
>> 
>> Pacemaker is attempting to restore connection to the remote node here, are 
> you
>> sure the remote is accessible? The "Timed Out" error means that pacemaker 
> was
>> unable to establish the connection during the timeout period.
> 
> Random question: Are we smart enough not to try and start pacemaker-remote 
> resources for node's we've just fenced?

I'm surprised: This sounds like asking: "Is water wet?" I never doubted that ;-)

Regards,
Ulrich