On Mon, Aug 27, 2012 at 1:44 AM, Eliot Gable wrote:
> On Sun, Aug 26, 2012 at 11:31 AM, Eliot Gable
> wrote:
>>
>>
>> I have also tried doing a resource cleanup on FreeSWITCH-MS, restarting
>> pacemaker and corosync, putting the node in standby and bringing it back
>> out, upgrading pacemaker and
On 2012-08-27T10:10:06, Eliot Gable wrote:
> I was not; but now I am setting the final score on successful start. I am
> calculating the score by using the monitor actions. For each portion of
> monitoring which returns successful, I am adding 10 to the score. The final
> score set should be 40.
I was not; but now I am setting the final score on successful start. I am
calculating the score by using the monitor actions. For each portion of
monitoring which returns successful, I am adding 10 to the score. The final
score set should be 40. However, it is still not working. Any other
suggestio
On 2012-08-26T11:44:52, Eliot Gable wrote:
> Looking back through my E-mails, it looks like this was originally deployed
> on 1.1.2. My guess is that someone did a sweeping software update on the
> system but never restarted/reloaded pacemaker + corosync until that reboot
> occurred last week. Di
On Sun, Aug 26, 2012 at 11:31 AM, Eliot Gable wrote:
>
> I have also tried doing a resource cleanup on FreeSWITCH-MS, restarting
> pacemaker and corosync, putting the node in standby and bringing it back
> out, upgrading pacemaker and corosync (to the version you seen in the
> output in this E-mai
node node1
primitive FreeSWITCH ocf:fssolutions:FreeSWITCH \
params ips="bond2/212.163.22.155/26:bond2/212.163.22.156/26"
user="freeswitch" group="freeswitch" \
op monitor interval="3s" role="Master" depth="0" \
op monitor interval="10s" role="Slave" depth="0" \
op s
