[ClusterLabs] -INFINITY location constraint not honored?

explicitly assigned -INFINITY to CouchIP resource related to node SRVDRSW01 (as stated by pcs constraint: Disabled on: SRVRDSW01 (score:-INFINITY) ). What am I missing or doing wrong? Thanks!!! Raffaele Pantaleoni ___ Manage your subscription: https://l

Re: [ClusterLabs] -INFINITY location constraint not honored?

Il 17/10/2019 14:51, Jan Pokorný ha scritto: On 17/10/19 08:22 +0200, Raffaele Pantaleoni wrote: I'm rather new to Pacemaker, I'm performing early tests on a set of three virtual machines. I am configuring the cluster in the following way: 3 nodes configured 4 resources configur

Re: [ClusterLabs] -INFINITY location constraint not honored?

Il 17/10/2019 16:47, Raffaele Pantaleoni ha scritto: Il 17/10/2019 14:51, Jan Pokorný ha scritto: On 17/10/19 08:22 +0200, Raffaele Pantaleoni wrote: I'm rather new to Pacemaker, I'm performing early tests on a set of three virtual machines. I am configuring the cluster in the fol

Re: [ClusterLabs] -INFINITY location constraint not honored?

while I added three nodes more, but the behaviour has not changed) Thanks On Thu, 2019-10-17 at 16:55 +0200, Raffaele Pantaleoni wrote: Il 17/10/2019 16:47, Raffaele Pantaleoni ha scritto: Il 17/10/2019 14:51, Jan Pokorný ha scritto: On 17/10/19 08:22 +0200, Raffaele Pantaleoni wrote: I&

Re: [ClusterLabs] -INFINITY location constraint not honored?

inted configuration, crm_simulate doesn't agree on such constraints on the other hand. :D On Fri, Oct 18, 2019 at 10:29 AM Raffaele Pantaleoni wrote: > > Il 17/10/2019 18:08, Ken Gaillot ha scritto: >> This does sound odd, possibly a bug. Can you provide the output of "pcs >

[ClusterLabs] Node replies with 401 ssl connect error

Error: SSL_accept returned=1 errno=0 state=error: sslv3 alert handshake failure     /usr/lib/ruby/2.3.0/openssl/ssl.rb:404:in `accept' Debian 10 versions:     corosync 3.0.1     pacemaker 2.0.1 Debian 9 versions:     corosync 2.4.2     pacemaker 1.1.6 Any hints? (I previously setup

[ClusterLabs] Unable to connect to node , no token available

e no ideas left. Thank you in advance. --- Raffaele Pantaleoni / / ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Unable to connect to node , no token available

ри 2020 г., 11:18:11 Гринуич+2, Raffaele Pantaleoni написа: Hello everybody, I'm trying to add an existing cluster into the pcsd web gui. When I try to add it, I select a node (SRVDRSW01.seko.com) and right after I am requested to enter the password for the hacluster user but from the pcsd

Re: [ClusterLabs] Unable to connect to node , no token available

ted, which seems to be the case as pcsd is asking for a password, then the log simply states the node is not authenticated. We would need a bigger portion of the log to see what's happening when you are trying to add the cluster to the web UI. Thanks, Tomas Dne 29. 10. 20 v 8:02 Raffae

Re: [ClusterLabs] Unable to connect to node , no token available

box. On 28/10/20 10:17, Raffaele Pantaleoni wrote: Hello everybody, I'm trying to add an existing cluster into the pcsd web gui. When I try to add it, I select a node (SRVDRSW01.seko.com) and right after I am requested to enter the password for the hacluster user but from the pcsd log

[ClusterLabs] Total resources limitation

f the resources are limited in number as well. Thank you -- Signature *Raffaele Pantaleoni* *IOT Design R&D Unit* Tel. +39 0746 605885 Fax.    +39 0746 607072 Mail *r.pantale...@seko.com <mailto:r.pantale...@seko.com>* Skype r.pantaleoni.seko *www.seko.com* <https://www.seko.com/