Hi all
I'm struggling with the use of failure-timeout. Altough the failcount is
expired, it is not reset. This is what the logs show:
Failcount for C_STONITH_VMWARE on id17 has expired (limit was 60s)
With pacemaker > 1.0 the failcounts should be reset when they have expired.
What am I missing
On Tue, Dec 27, 2011 at 3:30 PM, Vogt Josef wrote:
>> Just a question here: I could't get it to work without setting the gracetime
>> - which isn't set in the exportfs RA. Are you sure this works as expected?
> Thanks, good input. I'd be happy to add that (as in,
>On Tue, Dec 27, 2011 at 12:05 PM, Vogt Josef wrote:
>> Hi all,
>>
>> I wrote a patch to the ressource agent "nfsserver" which deals with NFSv4
>> (see attachment). It's now possible to use either NFSv3 or NFSv4 with this
>> ressource agent.
&g
Hi all,
I wrote a patch to the ressource agent "nfsserver" which deals with NFSv4 (see
attachment). It's now possible to use either NFSv3 or NFSv4 with this ressource
agent.
When using nfsv4, the nfsserver always needs about 90 seconds after a failover
until the shared directory is writeable a
