On Thu, 2023-09-14 at 18:28 +0800, Mr.R via Users wrote:
> Hi all，
>
> In Pacemaker-Remote 2.1.6, the pacemaker package is required
> for guest nodes and not for remote nodes. Why is that? What does
> pacemaker do?
> After adding guest node, pacemaker package does not seem to be
> needed.
Hi all??
In Pacemaker-Remote 2.1.6, the pacemaker package is required
for guest nodes and not for remote nodes. Why is that? What does
pacemaker do?
After adding guest node, pacemaker package does not seem to be
needed. Can I not install it here?
After testing, remote nodes can be offline, but
Probably I didn't configure pacemaker resource properly, now it's OK.
---
crm configure show remote-db8-ca-3a-69-60-f4
node remote-db8-ca-3a-69-60-f4:remote \
attributes OpenStack-role=compute standby=off
primitive remote-db8-ca-3a-69-60-f4 ocf:pacemaker:remote \
params
Hi, guys,
I'm running SLES12 sp3 and pacemaker-remote-1.1.16-4.8.x86_64, a few
months ago, compute nodes of openstack are running well. But today when I
setup a new compute node, it's said,"
-
Aug 13 16:31:04 [43122] db8-ca-3a-69-60-f4 pacemaker_remoted: notice:
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:
>
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
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
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
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
>
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
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:
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
Hi,
I am sorry for the long delay, just I moved on with my tool and had to
narrow down the circumstances of this error.
So apparently this error is related to many remote nodes querying CIB (I
had an OCF monitor agent running on all nodes), once turned off it works
with ~100 nodes.
Parts of the
On 30/09/16 11:28 -0500, Radoslaw Garbacz wrote:
> I have posted a question about this error attached to another thread, but
> because it was old and there is no answer I thought it could have been
> missed, so I am sorry for repeating it.
>
> Regarding the problem.
> I have a cluster, and when
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:
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:
>
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
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
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,
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
>
>
On 02/08/2016 07:55 AM, Ferenc Wágner wrote:
> Hi,
>
> I'm looking for information about the component interdependencies,
> because I'd like to split the Pacemaker packages in Debian properly.
> The current idea is to create two daemon packages, pacemaker and
> pacemaker-remote, which exclude
21 matches
Mail list logo
