I'm sorry I missed that.
The log after deleting corosync.conf states:
"I, [2018-04-19T23:59:15.690007 #19357] INFO -- : Running:
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-04-19T23:59:15.690021 #19357] INFO -- : CIB USER:
hacluster, groups: \n",
"D, [2018-04-19T23:59:15.695076 #19357] DEBUG -- :
[\"totem.cluster_name (str) = debian\\n\"]\n",
That looks like corosync has been started and it loaded the default
/etc/corosync.corosync.conf with an empty nodelist. Then you deleted the
file. However the running corosync still has the configuration loaded
and it provides it to pcs. Stopping corosync should do the trick.
Regards,
Tomas
Dne 23.4.2018 v 19:09 Casey & Gina napsal(a):
As I said in the E-mail you're replying to, I did try removing
/etc/corosync.conf and retrying (I also included a link to the bug report). I
pasted the output of pcs cluster auth after that in my last E-mail as well. Is
there some other fix I'm missing? Because that's the only step I saw to try...
Thanks,
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
