Thank you!
I'll try 1.1.12.
--
Best regards,
Sergey Arlashin
On Jan 6, 2015, at 3:23 AM, Andrew Beekhof wrote:
> Yeah, I can imagine 1.1.6 behaving like this.
> I'd highly recommend 1.1.12
>
>> On 5 Jan 2015, at 5:14 pm, Sergey Arlashin
>> wrote:
>>
>> Pacemaker 1.1.6
>>
>> It runs on Ub
> On 4 Dec 2014, at 7:52 pm, Daniel Dehennin
> wrote:
>
> Andrew Beekhof writes:
>
>> What version of pacemaker is this?
>> Some very old versions wanted the agent to be installed on all nodes.
>
> It's 1.1.10+git20130802-1ubuntu2.1 on Trusty Tahr.
I'm reasonably sure you need:
+ Gao,Yan (
> On 20 Dec 2014, at 6:21 am, Покотиленко Костик wrote:
>
> Hi,
>
> Simple scenario, several floating IPs should be living on "front" nodes
> only if there is working Nginx. There are several reasons against Nginx
> being controlled by Pacemaker.
>
> So, decided to colocate FIPs with unmanaged
> On 6 Jan 2015, at 3:37 am, Marco Querci wrote:
>
> Hi All.
> Any news for my problem?
Maybe post your /home/administrator/clustermonitor_notification.sh script?
>
> Many thanks.
>
>
> Il 19/12/2014 12:13, Marco Querci ha scritto:
>> Many tahnk for your reply.
>> Here is my configuration:
Yeah, I can imagine 1.1.6 behaving like this.
I'd highly recommend 1.1.12
> On 5 Jan 2015, at 5:14 pm, Sergey Arlashin
> wrote:
>
> Pacemaker 1.1.6
>
> It runs on Ubuntu 12.04 LTS 64bit.
>
> Linux lb-node1 3.11.0-23-generic #40~precise1-Ubuntu SMP Wed Jun 4 22:06:36
> UTC 2014 x86_64 x86_64
Hi All.
Any news for my problem?
Many thanks.
Il 19/12/2014 12:13, Marco Querci ha scritto:
Many tahnk for your reply.
Here is my configuration:
validate-with="pacemaker-1.2" cib-last-written="Thu Dec 18 20:04:43
2014" update-origin="langate1" update-client="crmd"
crm_feature_set="3.0.9" ha
Dmitry,
> Sure, in logs I see "adding new UDPU member {IP_ADDRESS}" (so DNS names
> are definitely resolved), but in practice the cluster does not work, as I
> said above. So validations of ringX_addr in corosync.conf would be very
> helpful in corosync.
that's weird. Because as long as DNS is r
