Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-22 Thread Ken Gaillot
On 03/19/2016 10:40 PM, Сергей Филатов wrote: > I’m fairly new to pacemaker, could you tell me what could the blocker? It's not clear from this information. There do not appear to be any constraints related to compute-1, so that doesn't seem to be an issue. Make sure it is enabled (pcs resource e

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-19 Thread Сергей Филатов
I’m fairly new to pacemaker, could you tell me what could the blocker? root@controller-1:~# pcs constraint Location Constraints: Resource: clone_p_dns Enabled on: controller-1.domain.com (score:100) Resource: clone_p_haproxy Enabled on: controller-1.domain.com (score:100) Resource: cl

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-11 Thread Ken Gaillot
On 03/10/2016 11:36 PM, Сергей Филатов wrote: > This one is the right log Something in the cluster configuration and state (for example, an unsatisfied constraint) is preventing the cluster from starting the resource: Mar 10 04:00:53 [11785] controller-1.domain.compengine: info: native_pr

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-09 Thread Ken Gaillot
On 03/08/2016 11:38 PM, Сергей Филатов wrote: > ssh -p 3121 compute-1 > ssh_exchange_identification: read: Connection reset by peer > > That’s what I get in /var/log/pacemaker.log after restarting pacemaker_remote: > Mar 09 05:30:27 [28031] compute-1.domain.com lrmd: info: > crm_signal_

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-08 Thread Сергей Филатов
ssh -p 3121 compute-1 ssh_exchange_identification: read: Connection reset by peer That’s what I get in /var/log/pacemaker.log after restarting pacemaker_remote: Mar 09 05:30:27 [28031] compute-1.domain.com lrmd: info: crm_signal_dispatch: Invoking handler for signal 15: Terminated Mar

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-08 Thread Ken Gaillot
On 03/07/2016 09:10 PM, Сергей Филатов wrote: > Thanks for an answer. Turned out the problem was not in ipv6. > Remote node is listening on 3121 port and it’s name is resolving fine. > Got authkey file at /etc/pacemaker on both remote and cluster nodes. > What can I check in addition? Is there any

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-07 Thread Сергей Филатов
Thanks for an answer. Turned out the problem was not in ipv6. Remote node is listening on 3121 port and it’s name is resolving fine. Got authkey file at /etc/pacemaker on both remote and cluster nodes. What can I check in addition? Is there any walkthrough for ubuntu? > On 07 Mar 2016, at 09:40,

Re: [ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-07 Thread Ken Gaillot
On 03/06/2016 07:43 PM, Сергей Филатов wrote: > Hi, > I’m trying to set up pacemaker_remote resource on ubuntu 14.04 > I followed "remote node walkthrough” guide > (http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280 > >

[ClusterLabs] pacemaker remote configuration on ubuntu 14.04

2016-03-06 Thread Сергей Филатов
Hi, I’m trying to set up pacemaker_remote resource on ubuntu 14.04 I followed "remote node walkthrough” guide (http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280