Hello, the following is the /etc/hosts for all my controllers:
127.0.0.1 localhost
10.102.184.70 tst-controller-01
10.102.184.71 tst-controller-02
10.102.184.72 tst-controller-03
10.102.119.223 iapi-tst-controller-01
10.102.119.224 iapi-tst-controller-02
10.102.119.225 iapi-tst-controller-03
10.10
On 05/15/2017 01:16 PM, Ignazio Cassano wrote:
> Hello, cluster-recheck-interval=1min.
>
>
> When I use the sytax:
> " pcs resource create computenode1 ocf:pacemaker:remote"
>
> the name is resolved in /etc/hosts
Just wanted to know if you have it in /etc/hosts ...
>
> When I use the syntax:
>
>
Hello, cluster-recheck-interval=1min.
When I use the sytax:
" pcs resource create computenode1 ocf:pacemaker:remote"
the name is resolved in /etc/hosts
When I use the syntax:
pcs resource create computenode1 remote server=10.102.184.91
I cannot avoid to resolve it.
Regards
Ignazio
___
On 05/15/2017 08:43 AM, Ignazio Cassano wrote:
> Hello,
> adding remote compute with:
> pcs resource create computenode1 remote server=10.102.184.91
>
> instead of:
> pcs resource create computenode1 ocf:pacemaker:remote
> reconnect_interval=60 op monitor interval=20
Have never tried it without g
Hello,
adding remote compute with:
pcs resource create computenode1 remote server=10.102.184.91
instead of:
pcs resource create computenode1 ocf:pacemaker:remote reconnect_interval=60
op monitor interval=20
SOLVES the issue when unexpected compute node reboot happens.
It returns online and works
Hello, there are no constraints for node compute-1.
The following is the corosync.log on the cluste node :
ay 12 13:14:47 [7281] tst-controller-01cib: info:
cib_process_request:Forwarding cib_delete operation for section
//node_state[@uname='compute-0']//lrm_resource[@id='compute
On 05/12/2017 12:32 PM, Ignazio Cassano wrote:
> Hello, some updates.
> Now I am not able enable compute-1 like yesterday: removing and
> readding it.
> Must If I remove it and add in the /etc/hosts of the cluster nodes an
> alias like compute1 , removing compute-1 and addiing compute1, it goes
> o
Hello, some updates.
Now I am not able enable compute-1 like yesterday: removing and readding it.
Must If I remove it and add in the /etc/hosts of the cluster nodes an alias
like compute1 , removing compute-1 and addiing compute1, it goes online .
2017-05-12 12:08 GMT+02:00 Ignazio Cassano :
> H
Hello, I do not know if it is the correct mode to answer in this mailing
list.
Anycase, either shutdown the remote node or fencing it with ipmi , it does
not retrurn online.
them pacemaker-remote service is enabled and restart at reboot.
But I continue to have the following on my cluster:
Online:
On 05/11/2017 03:45 PM, Ignazio Cassano wrote:
> Hello, I installed a pacemaker cluster with 3 nodes and 2 remote nodes
> (pacemaker remote). All nodes are centos 7.3. The remote nodes are
> online and pacemaker resources are running on them. When I reboot e
> remote pacemaker node it does not ret
Hello, I installed a pacemaker cluster with 3 nodes and 2 remote nodes
(pacemaker remote). All nodes are centos 7.3. The remote nodes are online
and pacemaker resources are running on them. When I reboot e remote
pacemaker node it does not return online and Its pacemaker resources
remain blocked.
11 matches
Mail list logo
