On Fri, 2021-06-25 at 14:41 +0800, luckydog xf wrote:
> > 1. deleted recorded failures.
> > crm_failcount -V -D -r nova-compute -N remote-db8-ca-3a-69-50-34 -n
> > monitor -I 1
> >
> > 2. cleanup resource status
> > crm resource cleanup nova-compute re
r the
resource is running.
On Wed, Jun 23, 2021 at 5:13 PM luckydog xf wrote:
> hello, guys,
>
> I built an openstack cluster with pacemaker, all nova-compute nodes are
> running. Yet
> `crm_mon -1r` shows only a nova-compute service is wrong
> ---
> Failed Actions:
> *
hello, guys,
I built an openstack cluster with pacemaker, all nova-compute nodes are
running. Yet
`crm_mon -1r` shows only a nova-compute service is wrong
---
Failed Actions:
* nova-compute_monitor_1 on remote-db8-ca-3a-69-50-34 'not running'
(7): call=719373, status=complete, exitreason='no
params reconnect_interval=60s server=db8-ca-3a-69-60-f4.ipa.pthl.hk
\
op monitor interval=30s \
op start interval=0 timeout=60s \
op stop interval=0 timeout=60s \
meta target-role=Started
---
On Thu, Aug 13, 2020 at 4:33 PM luckydog xf wrote:
> Hi, guys,
>
>
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:
lrmd_init_remote_
