VMware Cloud Community
SebastianGrugel
Hot Shot
Hot Shot
Jump to solution

vMA 5.5 Error: Failed to add users /

Hi.

I need add 3 hosts to vMA.I dont have domain controller.

1. I deploy fresh vMA from OVF and configure IP and password for vi-admin.

2. Add first ESX01 host with success. ( vifp addserver esx02 --authpolicy fpauth )

3. Added second and third ESXi finish with fail.(commands bellow)

vi-admin@vma02:~> vifp addserver esx02 --authpolicy fpauth

root@esx02's password:

vi-admin@vma02:~> vifp listservers

esx02.localdomain       ESXi

vi-admin@vma02:~> vifp addserver esx03 --authpolicy fpauth

root@esx03's password:

Error: Failed to add users

in vSphere client we can see something that:

vma01.png

During above tasks is creating vi-user and next vi-admin. After several seconds vi-admin is removed(i dont know why...)

/var/log/vmware/vma/vifpd.log on vMA

[2016-04-07 19:51:07.186 7F220CD47700 info 'App'] command-> 1

[2016-04-07 19:51:07.187 7F220AEC7700 info 'App'] ADDSERVER

[2016-04-07 19:51:07.197 7F220CD47700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-04-07 19:51:07.595 7F220AEC7700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-04-07 19:51:12.144 7F220CD47700 info 'App'] command-> 1

[2016-04-07 19:51:12.145 7F220CD47700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-04-07 19:51:12.145 7F220AE45700 info 'App'] ADDSERVER

[2016-04-07 19:51:12.504 7F220AE45700 info 'App'] Already connected.

[2016-04-07 19:51:12.509 7F220AE45700 info 'App'] Already connected.

[2016-04-07 19:51:30.308 7F220AE45700 info 'App'] permissions set for vi-admin00@esx03.localdomain

[2016-04-07 19:51:30.345 7F220AE45700 info 'App'] credstore: added user vi-admin00@esx03.localdomain to credstore of vi-admin

[2016-04-07 19:51:30.361 7F220AE45700 info 'App'] can take ownership of user vi-user01@esx03.localdomain.

[2016-04-07 19:51:30.361 7F220AE45700 warning 'App'] taking ownership of vi-user01@esx03.localdomain as it seems to be created by us.

[2016-04-07 19:51:52.534 7F220AE45700 error 'App'] addserver: Error occured while adding users for esx03.localdomain ..rolling back. Error in Vma

core.

[2016-04-07 19:51:52.582 7F220AE45700 info 'App'] user vi-admin00@esx03.localdomain is created by vifp. Removing it...

[2016-04-07 19:51:52.703 7F220AE45700 info 'App'] failed to remove permissions for vi-admin00@esx03.localdomain.

[2016-04-07 19:51:52.704 7F220AE45700 info 'App'] removed user vi-admin00@esx03.localdomain.

[2016-04-07 19:51:52.733 7F220AE45700 info 'App'] user vi-admin00@esx03.localdomain is removed from credstore of vi-admin.

[2016-04-07 19:51:52.768 7F220AE45700 error 'App'] Failed to add users

[2016-04-07 19:51:52.768 7F220AE45700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-04-07 19:51:52.772 7F220AE45700 info 'App'] MessageQueue::SendMessage - Queue id is 0

In which logs can i find something more ?

var/log/vmkernel.log on host is not clear for me... but if somebody will ask i will paste.

What should i do more ? i want only add 3 esxi servers to vMA and next login to those esxi without puting passwords.

Interesting is when i deployed next vMA02 and VM03 i can only add one esxi to vMA. During adding Second and third esxi generate that same errors... Now i have 1 vMA for each host :smileygrin:.....

Please about suggestion and help.... because my adventure with vMA is not good... last time i was problem with this vMA 5.5 The session is not authenticated after connect to target ESXi and dont resolved this in my second lab...

Sebastian

vExpert VSAN/NSX/CLOUD | VCAP5-DCA | VCP6-DCV/CMA/NV ==> akademiadatacenter.pl
Tags (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
SebastianGrugel
Hot Shot
Hot Shot
Jump to solution

Update:

I use this time only simple command without authpolicy:

Screenshot_13.png

Logs:

[2016-05-11 04:15:20.216 7F7A93D87700 info 'App'] command-> 1

[2016-05-11 04:15:20.219 7F7A91E85700 info 'App'] ADDSERVER

[2016-05-11 04:15:20.223 7F7A93D87700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-05-11 04:15:20.362 7F7A91E85700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-05-11 04:15:24.144 7F7A93D87700 info 'App'] command-> 1

[2016-05-11 04:15:24.144 7F7A93D87700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-05-11 04:15:24.144 7F7A91EC6700 info 'App'] ADDSERVER

[2016-05-11 04:15:24.196 7F7A91EC6700 info 'App'] Already connected.

[2016-05-11 04:15:24.198 7F7A91EC6700 info 'App'] Already connected.

[2016-05-11 04:15:24.732 7F7A91EC6700 info 'App'] permissions set for vi-admin00@esx03.localdomain

[2016-05-11 04:15:24.777 7F7A91EC6700 info 'App'] credstore: added user vi-admin00@esx03.localdomain to credstore of vi-admin

[2016-05-11 04:15:24.791 7F7A91EC6700 info 'App'] can take ownership of user vi-user00@esx03.localdomain.

[2016-05-11 04:15:24.793 7F7A91EC6700 warning 'App'] taking ownership of vi-user00@esx03.localdomain as it seems to be created by us.

[2016-05-11 04:15:26.943 7F7A91EC6700 info 'App'] permissions set for vi-user00@esx03.localdomain

[2016-05-11 04:15:26.980 7F7A91EC6700 info 'App'] credstore: added user vi-user00@esx03.localdomain to credstore of vi-user

[2016-05-11 04:15:27.052 7F7A91EC6700 info 'App'] MessageQueue::SendMessage - Queue id is 0

Screenshot_4.png

Screenshot_3.png

Test:

vi-admin@localhost:/var/log/vmware/vma> vifp listservers

esx01.localdomain       ESXi

esx02.localdomain       ESXi

esx03.localdomain       ESXi

vi-admin@localhost:/var/log/vmware/vma> vifptarget -s esx03.localdomain

vi-admin@localhost:/var/log/vmware/vma[esx03.localdomain]> esxcli vm process list

vMA02

   World ID: 35859

   Process ID: 0

   VMX Cartel ID: 35856

   UUID: 42 37 c3 61 b6 11 29 95-30 98 9f c1 b3 ba 44 95

   Display Name: vMA02

   Config File: /vmfs/volumes/56edd79c-9225dbd5-c1a2-2cc260319711/vSphere Management Assistant (vMA)/vSphere Management Assistant (vMA).vmx

vMA03

   World ID: 39084

   Process ID: 0

   VMX Cartel ID: 39081

   UUID: 42 37 be 3e 4b 98 8b f9-f0 cf 0c ec e6 f2 f9 0c

   Display Name: vMA03

   Config File: /vmfs/volumes/56edd87a-e0640a1a-0842-2cc260319711/vMA03/vMA03.vmx

Correct on esx03 i have vMA03 and vMA02.

Screenshot_5.png

Then looks OK.

Case resolved.

vExpert VSAN/NSX/CLOUD | VCAP5-DCA | VCP6-DCV/CMA/NV ==> akademiadatacenter.pl

View solution in original post

Reply
0 Kudos
1 Reply
SebastianGrugel
Hot Shot
Hot Shot
Jump to solution

Update:

I use this time only simple command without authpolicy:

Screenshot_13.png

Logs:

[2016-05-11 04:15:20.216 7F7A93D87700 info 'App'] command-> 1

[2016-05-11 04:15:20.219 7F7A91E85700 info 'App'] ADDSERVER

[2016-05-11 04:15:20.223 7F7A93D87700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-05-11 04:15:20.362 7F7A91E85700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-05-11 04:15:24.144 7F7A93D87700 info 'App'] command-> 1

[2016-05-11 04:15:24.144 7F7A93D87700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-05-11 04:15:24.144 7F7A91EC6700 info 'App'] ADDSERVER

[2016-05-11 04:15:24.196 7F7A91EC6700 info 'App'] Already connected.

[2016-05-11 04:15:24.198 7F7A91EC6700 info 'App'] Already connected.

[2016-05-11 04:15:24.732 7F7A91EC6700 info 'App'] permissions set for vi-admin00@esx03.localdomain

[2016-05-11 04:15:24.777 7F7A91EC6700 info 'App'] credstore: added user vi-admin00@esx03.localdomain to credstore of vi-admin

[2016-05-11 04:15:24.791 7F7A91EC6700 info 'App'] can take ownership of user vi-user00@esx03.localdomain.

[2016-05-11 04:15:24.793 7F7A91EC6700 warning 'App'] taking ownership of vi-user00@esx03.localdomain as it seems to be created by us.

[2016-05-11 04:15:26.943 7F7A91EC6700 info 'App'] permissions set for vi-user00@esx03.localdomain

[2016-05-11 04:15:26.980 7F7A91EC6700 info 'App'] credstore: added user vi-user00@esx03.localdomain to credstore of vi-user

[2016-05-11 04:15:27.052 7F7A91EC6700 info 'App'] MessageQueue::SendMessage - Queue id is 0

Screenshot_4.png

Screenshot_3.png

Test:

vi-admin@localhost:/var/log/vmware/vma> vifp listservers

esx01.localdomain       ESXi

esx02.localdomain       ESXi

esx03.localdomain       ESXi

vi-admin@localhost:/var/log/vmware/vma> vifptarget -s esx03.localdomain

vi-admin@localhost:/var/log/vmware/vma[esx03.localdomain]> esxcli vm process list

vMA02

   World ID: 35859

   Process ID: 0

   VMX Cartel ID: 35856

   UUID: 42 37 c3 61 b6 11 29 95-30 98 9f c1 b3 ba 44 95

   Display Name: vMA02

   Config File: /vmfs/volumes/56edd79c-9225dbd5-c1a2-2cc260319711/vSphere Management Assistant (vMA)/vSphere Management Assistant (vMA).vmx

vMA03

   World ID: 39084

   Process ID: 0

   VMX Cartel ID: 39081

   UUID: 42 37 be 3e 4b 98 8b f9-f0 cf 0c ec e6 f2 f9 0c

   Display Name: vMA03

   Config File: /vmfs/volumes/56edd87a-e0640a1a-0842-2cc260319711/vMA03/vMA03.vmx

Correct on esx03 i have vMA03 and vMA02.

Screenshot_5.png

Then looks OK.

Case resolved.

vExpert VSAN/NSX/CLOUD | VCAP5-DCA | VCP6-DCV/CMA/NV ==> akademiadatacenter.pl
Reply
0 Kudos