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,
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
This is a known issue. Take a look at
https://github.com/ClusterLabs/pcs/issues/153#issuecomment-346849207
for more details and steps to fix it.
Regards,
Tomas
Dne 20.4.2018 v 02:06 Casey & Gina napsal(a):
On Apr 19, 2018, at 12:37 AM, Tomas Jelinek wrote:
Can you run
> On Apr 19, 2018, at 12:37 AM, Tomas Jelinek wrote:
>
> Also it would be nice to know what pcs version you have.
My apologies for omitting this from my previous E-mail... It's PCS version
0.9.149, and I'm running it on an updated Ubuntu 16.04 installation.
> On Apr 19, 2018, at 12:37 AM, Tomas Jelinek wrote:
>
> Can you run those two commands with the --debug flag and post the output?
> Also it would be nice to know what pcs version you have.
Sure thing. It looks like it's erroring because /var/lib/pcsd/tokens doesn't
Can you run those two commands with the --debug flag and post the
output? Also it would be nice to know what pcs version you have.
Regards,
Tomas
Dne 18.4.2018 v 23:25 Casey & Gina napsal(a):
What would cause this situation? I'm following the same process as I have
previously, and don't
What would cause this situation? I'm following the same process as I have
previously, and don't understand why I'm unable to create new clusters now...
root@d-gp2-dbpg1-1:~# pcs cluster auth d-gp2-dbpg1-1 d-gp2-dbpg1-2
d-gp2-dbpg1-3 -u hacluster -p 'mypassword'
d-gp2-dbpg1-1: Authorized