Your first issue is a something that's already been patched; you can fix it either by downloading the latest release, executing "git pull" from your repository directory (if you obtained ECSCE via "git clone"), or by adding the line "DockerCommandLineFlags=[]" below the two lines beginning with "logging" and "logger" near the top of the script (if you just want a quick fix).
The authentication phase may take quite some time to come up, but if it's consistent, one of the first things to try (as listed here) is to edit your firewall settings (or remove your firewall entirely if you feel so inclined).
I'm not entirely sure about the CAS/.pea issue at the moment, but I get the feeling that it may similarly be related to your port settings - is 3218 open on both UDP and TCP? If not, you may need to add those (e.g. "firewall-cmd --permanent --add-port=3218/udp") to authenticate properly against CAS.
Honestly not sure what Calo is seeing if his environment is working fine with single-node but failing authentication on multi-node for the same host; there shouldn't be additional setup necessary by comparison. Other developers with possible insight would be welcomed here.
Aaron_Peterson
1 Rookie
•
26 Posts
0
April 22nd, 2016 09:00
Your first issue is a something that's already been patched; you can fix it either by downloading the latest release, executing "git pull" from your repository directory (if you obtained ECSCE via "git clone"), or by adding the line "DockerCommandLineFlags=[]" below the two lines beginning with "logging" and "logger" near the top of the script (if you just want a quick fix).
The authentication phase may take quite some time to come up, but if it's consistent, one of the first things to try (as listed here) is to edit your firewall settings (or remove your firewall entirely if you feel so inclined).
I'm not entirely sure about the CAS/.pea issue at the moment, but I get the feeling that it may similarly be related to your port settings - is 3218 open on both UDP and TCP? If not, you may need to add those (e.g. "firewall-cmd --permanent --add-port=3218/udp") to authenticate properly against CAS.
holgerjakob_c0722c
2 Intern
•
337 Posts
0
April 25th, 2016 05:00
Hi Aaron
step1 script worked. step2 failed with:
[ecs@ecsnode1 ecs-multi-node]$ sudo python step2_object_provisioning.py --ECSNodes=192.168.1.22 192.168.1.23 192.168.1.24 192.168.1.25 --Namespace=mnns1 --ObjectVArray=mnova1 --ObjectVPool=mnovp1 --UserName=emccode --DataStoreName=mnds1 --VDCName=mnvdc1 --MethodName=
[sudo] password for ecs:
Executing getAuthToken: curl -i -k https://192.168.1.22:4443/login -u root:ChangeMe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 93 100 93 0 0 169 0 --:--:-- --:--:-- --:--:-- 170
Auth Token BAAcZHFkRnRtaGlaNG1ocDlycHlxT2ZMdEZLbHo0PQMAjAQASHVybjpzdG9yYWdlb3M6VmlydHVhbERhdGFDZW50ZXJEYXRhOmJkM2NlMzNlLWM2NjYtNDM4Yi04ZjY3LTIzYzA4MGMxMmYzMQIADTE0NjE1ODg3NTQ0ODgDAC51cm46VG9rZW46OTQwYWQ3YzQtNWZhZS00ZTZlLWFjYmMtMDM0ODM4OWU0MDNlAgAC0A8=
ECSNodes: 192.168.1.22
Traceback (most recent call last):
File "step2_object_provisioning.py", line 360, in
main(sys.argv[1:])
File "step2_object_provisioning.py", line 279, in main
print("ObjectVArray: %s" %ObjectVArray)
UnboundLocalError: local variable 'ObjectVArray' referenced before assignment
[ecs@ecsnode1 ecs-multi-node]$
Thanks a lot, Holger
Aaron_Peterson
1 Rookie
•
26 Posts
1
April 25th, 2016 07:00
Holger,
I believe it's a result of your formatting; you should use a comma-delimited list rather than a space-delimited one for ECSNodes, e.g.
[ecs@ecsnode1 ecs-multi-node]$ sudo python step2_object_provisioning.py --ECSNodes=192.168.1.22,192.168.1.23,192.168.1.24,192.168.1.25 --Namespace=mnns1 --ObjectVArray=mnova1 --ObjectVPool=mnovp1 --UserName=emccode --DataStoreName=mnds1 --VDCName=mnvdc1 --MethodName=
Honestly not sure what Calo is seeing if his environment is working fine with single-node but failing authentication on multi-node for the same host; there shouldn't be additional setup necessary by comparison. Other developers with possible insight would be welcomed here.
holgerjakob_c0722c
2 Intern
•
337 Posts
0
April 25th, 2016 08:00
Hi Aaron
Thanks for the reply and correction. Sorry for the trouble.
I will retry, even on my ssd esx it will take a short while. Then I'll update you.
As for the failing authentication, this took a long while on my machine to complete. But it finished.
I will keep you posted, Holger