On Thu, 2012-12-13 at 12:01 +0900, Yuichi SEINO wrote:
> Hi Jiaju,
>
> 2012/12/12 Jiaju Zhang :
> > On Tue, 2012-12-11 at 20:15 +0900, Yuichi SEINO wrote:
> >> Hi Jiaju,
> >>
> >> Currently, booth is the state of "started" on pacemaker before booth
> >> writes ticket information in cib. So, If the
Hi,
I have structured my multi-state resource agent as below when the
underlying resource becomes unavailable for some reason:
monitor()
{
state=get_primitive_resource_state()
...
...
if ($state == unavailable)
return $OCF_NOT_RUNNING
...
...
}
stop()
{
monit
Hi, Jiaju
Thanks for the reply.
2012/12/12 Jiaju Zhang :
> This is what I wanted to do as well;) That is to say, the lease should
> keep renewing on the original site successfully unless it was down.
> Current implementation is to let the original site renew the ticket
> before ticket lease expir
Andrew Beekhof writes:
> On Wed, Dec 12, 2012 at 11:51 AM, wrote:
>>
>> Hi,
>>
>> I've just observed something weird.
>> A node is running a stonith resource for which gethosts gives an empty
>> node list. The result of stonith_admin -l does include it in the
>> device list !
>>
>> result of "s
Hello-
I'm running Pacemaker v. 1.1 (pacemaker-1.1.7-6.el6.x86_64) on CentOS 6.3 and
am observing behavior on my systems that differs from the behavior described in
the manual.
Basically, the desired behavior (and the behavior described in Pacemaker
Explained Section 6.3.1) is that when a "fir
Hi,
we have a 2 node corosync 1.4.2 and pacemaker 1.1.7 cluster running
drdb, nfs, solr and redis in master slave configurations.
Currently node 2 is unable to rejoin cluster after being fenced by stonith.
the logs on node 2
Dec 15 01:52:38 www2 cib: [6705]: info: ais_dispatch_message:
Membershi
