On Thu, 2018-08-02 at 02:25 +, Eric Robinson wrote:
> > > The message likely came from the resource agent calling
> > > crm_attribute
> > > to set a node attribute. That message usually means the cluster
> > > isn't
> > > running on that node, so it's highly suspect. The cib might have
> > >
> > The message likely came from the resource agent calling crm_attribute
> > to set a node attribute. That message usually means the cluster isn't
> > running on that node, so it's highly suspect. The cib might have
> > crashed, which should be in the log as well. I'd look into that first.
>
>
> -Original Message-
> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Ken Gaillot
> Sent: Wednesday, August 01, 2018 2:17 PM
> To: Cluster Labs - All topics related to open-source clustering welcomed
>
> Subject: Re: [ClusterLabs] Why Won't Resources
On Wed, 2018-08-01 at 03:49 +, Eric Robinson wrote:
> I have what seems to be a healthy cluster, but I can’t get resources
> to move.
>
> Here’s what’s installed…
>
> [root@001db01a cluster]# yum list installed|egrep "pacem|coro"
> corosync.x86_64 2.4.3-2.el7_5.1
I have what seems to be a healthy cluster, but I can't get resources to move.
Here's what's installed...
[root@001db01a cluster]# yum list installed|egrep "pacem|coro"
corosync.x86_64 2.4.3-2.el7_5.1 @updates
corosynclib.x86_64 2.4.3-2.el7_5.1
