Frank
asked on
cannot login vpxuser@127.0.0.1
Hi ,
after upgrading the vsphere from version 4 to 5 I am getting this error on the hosts:
cannot login vpxuser@127.0.0.1
I tried to apply https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005759
but when it comes down to do the user del I get the error:
userdel: can't find the vpxuser in /etc/group
userdel: /etc/gshadow/:no such file or directory
I can not delete the vpxa user
I reconnect the host hoping that he will recreate a new one.
I still have the error cannot login vpxuser@127.0.0.1
the error is on the host and not in vcenter
Please advise :)
vpxuser-error.JPG
vpxuser-not-deleting.png
after upgrading the vsphere from version 4 to 5 I am getting this error on the hosts:
cannot login vpxuser@127.0.0.1
I tried to apply https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005759
but when it comes down to do the user del I get the error:
userdel: can't find the vpxuser in /etc/group
userdel: /etc/gshadow/:no such file or directory
I can not delete the vpxa user
I reconnect the host hoping that he will recreate a new one.
I still have the error cannot login vpxuser@127.0.0.1
the error is on the host and not in vcenter
Please advise :)
vpxuser-error.JPG
vpxuser-not-deleting.png
ASKER
sorry copy and paste issue
I did this procedure
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919
I did this procedure
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919
ASKER
I used the vsphere client to removed the users now
1) disconnected the host
2) delete the vpx user with the vsphere client
3) delete the vpxa agent by command line with putty on the host (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919)
4) reconnect the host
5) I have seen that the vcenter reinstalled the vpxa agent
6) still have the error on vpx user on the hosts
1) disconnected the host
2) delete the vpx user with the vsphere client
3) delete the vpxa agent by command line with putty on the host (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919)
4) reconnect the host
5) I have seen that the vcenter reinstalled the vpxa agent
6) still have the error on vpx user on the hosts
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
WHAT does not work?
vpxuser is automatically given random password when initialising from vcenter.
vpxuser is automatically given random password when initialising from vcenter.
ASKER
1) nothing is not working
2) I am receiving this error but everthing is working
3) I need to suppress the error or found the cause because is keeping sending alert to the monitoring system
4) I found this in the hostd.log
017-02-07T10:14:20.921Z [3E544B90 verbose 'ResourcePool ha-root-pool'] Root pool capacity changed from 19936MHz/73204MB to 19936MHz/73205MB
2017-02-07T10:14:20.921Z [3E481B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.001Z [3E8E2B90 verbose 'Proxysvc Req00520'] New proxy client SSL(TCP(local=172.18.74.41 :443, peer=172.18.74.55:19864))
2017-02-07T10:14:21.010Z [3E860B90 verbose 'Proxysvc Req00521'] New proxy client SSL(TCP(local=127.0.0.1:44 3, peer=127.0.0.1:63484))
pam_per_user: create_subrequest_handle() : doing map lookup for user "vpxuser"
pam_per_user: create_subrequest_handle() : creating new subrequest (user="vpxuser", service="system-auth-local ")
2017-02-07T10:14:21.019Z [3E544B90 verbose 'Proxysvc Req00522'] New proxy client SSL(TCP(local=127.0.0.1:44 3, peer=127.0.0.1:61575))
2017-02-07T10:14:21.021Z [3E8E2B90 verbose 'SoapAdapter'] Responded to service state request
2017-02-07T10:14:21.051Z [3E240B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
pam_unix(system-auth-local :auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=vpxuser
2017-02-07T10:14:21.191Z [3E923B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.213Z [3E8E2B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.791Z [3E544B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:23.221Z [FFD60A90 verbose 'SoapAdapter'] Responded to service state request
2017-02-07T10:14:23.420Z [3E481B90 info 'ha-eventmgr' opID=462e0c5d] Event 56670 : Cannot login vpxuser@127.0.0.1
Rejected password for user vpxuser from 127.0.0.1
2017-02-07T10:14:23.421Z [3E481B90 info 'Default' opID=462e0c5d] AdapterServer caught exception: vim.fault.InvalidLogin
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Activation [N5Vmomi10ActivationE:0x8e df080] : Invoke done [login] on [vim.SessionManager:ha-ses sionmgr]
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg userName:
--> "vpxuser"
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg password:
--> (not shown)
-->
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg locale:
--> ""
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Throw vim.fault.InvalidLogin
2017-02-07T10:14:23.421Z [3E240B90 verbose 'Default'] CloseSession called for session id=527b440d-054e-264e-31ac -e01e41056 3ec
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Result:
--> (vim.fault.InvalidLogin) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
5) unfortunately I can not upgrade the host and I reset the vpxa user 3 times by using this procedure https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919)
I can not find out ..for now the cause of this error ..
2) I am receiving this error but everthing is working
3) I need to suppress the error or found the cause because is keeping sending alert to the monitoring system
4) I found this in the hostd.log
017-02-07T10:14:20.921Z [3E544B90 verbose 'ResourcePool ha-root-pool'] Root pool capacity changed from 19936MHz/73204MB to 19936MHz/73205MB
2017-02-07T10:14:20.921Z [3E481B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.001Z [3E8E2B90 verbose 'Proxysvc Req00520'] New proxy client SSL(TCP(local=172.18.74.41
2017-02-07T10:14:21.010Z [3E860B90 verbose 'Proxysvc Req00521'] New proxy client SSL(TCP(local=127.0.0.1:44
pam_per_user: create_subrequest_handle()
pam_per_user: create_subrequest_handle()
2017-02-07T10:14:21.019Z [3E544B90 verbose 'Proxysvc Req00522'] New proxy client SSL(TCP(local=127.0.0.1:44
2017-02-07T10:14:21.021Z [3E8E2B90 verbose 'SoapAdapter'] Responded to service state request
2017-02-07T10:14:21.051Z [3E240B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
pam_unix(system-auth-local
2017-02-07T10:14:21.191Z [3E923B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.213Z [3E8E2B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:21.791Z [3E544B90 verbose 'SoapAdapter'] Unrecognized version URI "urn:vim25/5.5"; using default handler for "urn:vim25/5.0"
2017-02-07T10:14:23.221Z [FFD60A90 verbose 'SoapAdapter'] Responded to service state request
2017-02-07T10:14:23.420Z [3E481B90 info 'ha-eventmgr' opID=462e0c5d] Event 56670 : Cannot login vpxuser@127.0.0.1
Rejected password for user vpxuser from 127.0.0.1
2017-02-07T10:14:23.421Z [3E481B90 info 'Default' opID=462e0c5d] AdapterServer caught exception: vim.fault.InvalidLogin
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Activation [N5Vmomi10ActivationE:0x8e
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg userName:
--> "vpxuser"
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg password:
--> (not shown)
-->
2017-02-07T10:14:23.421Z [3E481B90 verbose 'Vmomi' opID=462e0c5d] Arg locale:
--> ""
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Throw vim.fault.InvalidLogin
2017-02-07T10:14:23.421Z [3E240B90 verbose 'Default'] CloseSession called for session id=527b440d-054e-264e-31ac
2017-02-07T10:14:23.421Z [3E481B90 info 'Vmomi' opID=462e0c5d] Result:
--> (vim.fault.InvalidLogin) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
5) unfortunately I can not upgrade the host and I reset the vpxa user 3 times by using this procedure https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031919)
I can not find out ..for now the cause of this error ..
You can complain to vmware.
I can run ahead of events but in few months you will filter events yourself for peace of mind.
I can run ahead of events but in few months you will filter events yourself for peace of mind.
ASKER
we decide to upgrade all infrastructure to version 5.5 u3
It still is there at times with 6.0.
ASKER
I can not due to the hardware dl380 g6
vpxuser is created by vcenter connecting ESXi