[ClusterLabs] Why Won't Resources Move?

[Eric Robinson]

> > 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.
> 
> 
> I rebooted the server and afterwards I'm still getting tons of these...
> 
> Aug  2 01:43:40 001db01a drbd(p_drbd1)[18628]: ERROR: ha02_mysql: Called
> /usr/sbin/crm_master -Q -l reboot -v 10000 Aug  2 01:43:40 001db01a
> drbd(p_drbd0)[18627]: ERROR: ha01_mysql: Called /usr/sbin/crm_master -Q -l
> reboot -v 10000 Aug  2 01:43:40 001db01a drbd(p_drbd0)[18627]: ERROR:
> ha01_mysql: Exit code 107 Aug  2 01:43:40 001db01a drbd(p_drbd1)[18628]:
> ERROR: ha02_mysql: Exit code 107 Aug  2 01:43:40 001db01a
> drbd(p_drbd0)[18627]: ERROR: ha01_mysql: Command output:
> Aug  2 01:43:40 001db01a drbd(p_drbd1)[18628]: ERROR: ha02_mysql:
> Command output:
> Aug  2 01:43:40 001db01a lrmd[2025]:  notice:
> p_drbd0_monitor_60000:18627:stderr [ Error signing on to the CIB service:
> Transport endpoint is not connected ] Aug  2 01:43:40 001db01a lrmd[2025]:
> notice: p_drbd1_monitor_60000:18628:stderr [ Error signing on to the CIB
> service: Transport endpoint is not connected ]
> 
> 

Ken, 

Ironically, while researching this problem, I ran across the same question being asked back in November of 2017, and you made the same comment back then.

https://lists.clusterlabs.org/pipermail/users/2017-November/013975.html

And the solution turned out to be the same for me as it was for that guy. On the node where I was getting the errors, SELINUX was enforcing. I set it to permissive and the errors went away. 😉

--Eric