wallnerryan
commented
8 years ago @akamalov thanks, strange, testing this out myself today.
Closed akamalov closed 8 years ago
wallnerryan
commented
8 years ago @akamalov thanks, strange, testing this out myself today.
wallnerryan
commented
8 years ago @akamalov i got this working without issues.
/usr/local/bin/flockerctl --control-service ip-10-167-144-195 --user plugin list-nodes
SERVER ADDRESS
5bf2fa29 10.63.55.92 34 mkdir /etc/flocker
35 cd /etc/flocker/
36 flocker-ca initialize my-cluster
37 ls
38 flocker-ca create-control-certificate ip-10-167-144-195
39 ls
40 mv control-ip-10-167-144-195.crt control-service.crt
41 mv control-ip-10-167-144-195.key control-service.key
42 ls
43 chmod 0600 control-service.*
44 chmod 0700 /etc/flocker
45 flocker-ca create-node-certificate
46 ls
47 mv 5bf2fa29-2cc0-402b-8e4b-981a706d43cf.crt node.crt
48 mv 5bf2fa29-2cc0-402b-8e4b-981a706d43cf.key node.key
49 flocker-ca create-api-certificate plugin
50 ls
52 cd /etc/flocker/
55 scp node.* ec2-user@ip-10-63-55-92:/home/ec2-user/
56 scp cluster.crt* ec2-user@ip-10-63-55-92:/home/ec2-user/
57 scp plugin.* ec2-user@ip-10-63-55-92:/home/ec2-user/
58 systemctl enable flocker-control
59 systemctl start flocker-control
79 /usr/local/bin/flockerctl --control-service ip-10-167-144-195 --user plugin list-nodesLet's compare envs.
yum list installed | grep ssl
openssl.x86_64 1:1.0.1e-42.el7_1.9 @anaconda/7.2
openssl-libs.x86_64 1:1.0.1e-42.el7_1.9 @anaconda/7.2 cat /etc/os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.2 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.2 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.2"
akamalov
commented
8 years ago Here you go:
SSL:
openssl.x86_64 1:1.0.1e-51.el7_2.5 @rhel-x86_64-server-7
openssl-devel.x86_64 1:1.0.1e-51.el7_2.5 @rhel-x86_64-server-7
openssl-libs.x86_64 1:1.0.1e-51.el7_2.5 @rhel-x86_64-server-7OS:
NAME="Red Hat Enterprise Linux Server"
VERSION="7.2 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.2 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.2"$ rpm -Uvh openssl-libs-1.0.1e-51.el7_2.5.x86_64.rpm openssl-1.0.1e-51.el7_2.5.x86_64.rpm
warning: openssl-libs-1.0.1e-51.el7_2.5.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:openssl-libs-1:1.0.1e-51.el7_2.5 ################################# [ 25%]
2:openssl-1:1.0.1e-51.el7_2.5 ################################# [ 50%]
Cleaning up / removing...
3:openssl-1:1.0.1e-42.el7_1.9 ################################# [ 75%]
4:openssl-libs-1:1.0.1e-42.el7_1.9 ################################# [100%]installed the same versions. I can't seem to reproduce your issues..
akamalov
commented
8 years ago Ok, then all of my systems have been possessed with demons...
wallnerryan
commented
8 years ago @akamalov i just noticed your agent.yml uses 4523
my agent.yml and control service used 4524
control-service:
hostname: ip-10-167-144-195
port: 4524Ok, then all of my systems have been possessed with demons...
hahaha, try the above port change in your agent.yml
UPDATE: if i change it to 4523 i can reproduce your issues. Looks like a misconfig, i should have noticed earlier :|
akamalov
commented
8 years ago Wow!! that did the trick!!
[root@mmaster1 new.cert]# /usr/local/bin/flockerctl --control-service 192.168.120.156 --user user list-nodes
SERVER ADDRESS
1b8bd056 192.168.120.162
4d35f998 192.168.120.163
06978551 192.168.120.161
701fdaad 192.168.120.164
fb2b98cd 192.168.120.165
[root@mmaster1 new.cert]# @wallnerryan ...just wondering what will happen to CluserHQ if...you...quit ?
wallnerryan
commented
8 years ago :sadface: on my part, our logs don'y say what port its trying and I totally did not pay attention to that
akamalov
commented
8 years ago @wallnerryan Thank you very, very much!!!
wallnerryan
commented
8 years ago @wallnerryan ...just wondering what will happen to CluserHQ if...you...quit ?
hopefully we won't have to find out :)
wallnerryan
commented
8 years ago closing. open any new issues you might have, hopefully can resolve it quicker!
Greetings,
I am having a problem with trying to start flocker-dataset-agent service. Brief background: the environment consists of RHEL7.2 attempting to access PureStorage backend via iSCSI. PureStorage drivers have been installed and test (which I will go further below). Let me first display environmentals:
Operating System:
Flocker environment:
/etc/flocker/agent.yml
PureStorage Driver:
PureStorage Driver GitHub link - https://github.com/PureStorage-OpenConnect/purestorage-flocker-driver
Restart Flocker services, display current status:
Trying to get more information on flocker-dataset-agent service:
Tested PureStorage driver manually:
As you can see above, connectivity is there. We were able to connect, authenticate using a token and were able to retrieve PureStorage basic info (i.e., version, name, etc)..
Verified the sanity of /etc/flocker/node.crt:
Tried to run
flocker-diagnostics, but it exited:I am trying at least configure one node correctly. Once configured and visible from
flockerctlcommand, I will proceed with the rest of the nodes (i.e., using node 1 as a template). Any pointers or suggestions ?Thanks so much!!