-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pcs cluster auth does not work #109
Comments
Thank you for reporting the issue. I am not able to reproduce it however, so I would like to know more about your setup. |
Thank you for your reply.
Installed directly from GitHub with compilation of both pcs and pcsd
I try to run a cluster archiclust with two nodes archie and archicomble corosync.conf :
I have problems with corosync.conf too because
Stopping the same on other node archicomble. Same result as previously :
Humm sorry last line points that pcsd is not running on archie
Same as previously with pacemaker and corosync stopped on both nodes :
|
Any idea ?
Are gems missing ? |
Corosync.conf changed to :
and this makes corosync run on archie. Set the same on archicomble. corosync stopped on archie and archicomble corosync.conf same on both archie and archicomble and like above but still same error message with
|
I'm sorry I'm still unable to reproduce this. It looks like your pcsd is not running or is crashing upon processing the auth request. I think so because of:
and Please make sure that:
This is to reduce possibility of other errors. You normally don't need to do that but it simplifies debugging. It looks like you're missing rubygem rpam-ruby19 (1.2.1). This is essential for authentication to work. Once all of the above is fixed, start pcsd and make sure it is running on all your nodes. Try running You can ignore "Unable to connect to node archicomble, no token available" messages when running |
I did what you said and still no success :
And also :
Result of the command :
Contents of pcsd.log on archie :
Maybe a problem ? Contents of pcsd.log on archicomble : Nothing special. Seems not have been contacted. My gem list of the moment :
I have rpam-ruby19 (1.2.1) |
Can you try it again with this patch e5347d3 included? |
Patch seems to work. Setting it on archicomble made me see that rpam-ruby19 (1.2.1) was not installed. It was installed on archie but not on archicomble. (With this patch pcsd could not be restarted on archicomble) Result of the command on archie :
So i can see tokens have been written now 👍
Effectively i have : rpam (1.0.1) both installed. Thank you for time and for help ! |
This makes it is impossible to create any cluster basically.
Without --force option
In the last report (without --force option) we can notice : no token available
There is no tokens file in /var/lib/pcsd
The text was updated successfully, but these errors were encountered: