Hello together,
at a customers site we are running a vcenter Server Appliance (Version 6.7.0.41000, Build 14836122). Since today in the morning I have the Problem, that my monitoring solution cannot query information about the connected ESXi hosts any more. After logging into vCenter Web Ui i received the Error message: "Could not connect to one or more vCenter Server systems https://v-center:443/sdk".
I found this thread, where user bleuze had the same problem: SOLVED: Could not connect to one or more vCenter Server systems: .
I followed the instructions and found out that vmware-vpxd is not running. After restarting the service everything seems to work fine for a few seconds, until vmware-vpxd crashes again.
I did some further investigation on the /storage/log/vmware/vpxd/vpxd.log (find attached in next posting). I am not really clear, what the cause for the crash is. Maybe there is a faulty package installed or downloaded by update manager? Find errors from Line 3292 in the log file.
2019-10-29T10:37:00.981+01:00 error vpxd[05017] [Originator@6876 sub=[SSO] opID=a048760] [UserDirectorySso] GetUserInfo exception: N7Vmacore9Authorize25AuthUserNotFoundExceptionE(User localos\com.vmware.vim.eam)
--> [context]zKq7AVECAAAAAGC34QAVdnB4ZAAA4AArbGlidm1hY29yZS5zbwAAWCUbAIyfGAHcNvV2cHhkAAFLaPUBemv1AQhx9QGiXPUBY131AZKdngGaoZ+CIbEBAWxpYnZpbS10eXBlcy5zbwABA9JyAUzWcQH943EBpD5yAHFvIwA6ciMAnVYrA9RzAGxpYnB0aHJlYWQuc28uMAAE3Y4ObGliYy5zby42AA==[/context]
2019-10-29T10:37:00.983+01:00 error vpxd[05017] [Originator@6876 sub=[SSO] opID=a048760] [UserDirectorySso] NormalizeUserName(com.vmware.vim.eam, false) exception: N7Vmacore9Authorize25AuthUserNotFoundExceptionE(User localos\com.vmware.vim.eam)
--> [context]zKq7AVECAAAAAGC34QAVdnB4ZAAA4AArbGlidm1hY29yZS5zbwAAWCUbAIyfGAHcNvV2cHhkAAFLaPUBemv1AQhx9QGiXPUBY131AZKdngGaoZ+CIbEBAWxpYnZpbS10eXBlcy5zbwABA9JyAUzWcQH943EBpD5yAHFvIwA6ciMAnVYrA9RzAGxpYnB0aHJlYWQuc28uMAAE3Y4ObGliYy5zby42AA==[/context]
2019-10-29T10:37:00.998+01:00 info vpxd[05017] [Originator@6876 sub=vpxLro opID=a048760] [VpxLRO] -- FINISH lro-233
2019-10-29T10:37:02.244+01:00 info vpxd[05007] [Originator@6876 sub=DAS] [FdmManager::MonitorVmHostStateCallback] All VMs and hosts have been protected.
2019-10-29T10:37:02.665+01:00 info vpxd[04985] [Originator@6876 sub=vpxLro opID=5c421eb3] [VpxLRO] -- BEGIN lro-238 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition -- 52c75802-dce2-4af1-9514-2c6831594611(5232e022-9e06-f146-e2fb-3654948be4fa)
2019-10-29T10:37:02.666+01:00 info vpxd[04985] [Originator@6876 sub=vpxLro opID=5c421eb3] [VpxLRO] -- FINISH lro-238
2019-10-29T10:37:02.666+01:00 info vpxd[04985] [Originator@6876 sub=Default opID=5c421eb3] [VpxLRO] -- ERROR lro-238 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition: vim.fault.DuplicateName:
--> Result:
--> (vim.fault.DuplicateName) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> name = "com.vmware.vsan.clusterstate",
--> object = 'vim.CustomFieldsManager:9334614a-3cb3-4a53-b975-2fce444bafc1:CustomFieldsManager'
--> msg = ""
--> }
--> Args:
-->
--> Arg name:
--> "com.vmware.vsan.clusterstate"
--> Arg moType:
--> "vim.ClusterComputeResource"
--> Arg fieldDefPolicy:
-->
--> Arg fieldPolicy:
-->
Opening the Update Manager on vSphere Web Client displays "An unexpected error occured".
I am a little bit confused on how to continue to solve the Problem. I'd be very gratefull, if somebody had an idea on how to continue and fix this problem.
Thank you in advance!
Accepted Solutions
Correct. I just found out a few minutes we are affected from the excessive Hardware health alarms described here: VMware Knowledge Base
vCenter got tons of Events that filled up the seat partition:
Thank you KocPawel for the hint. I was able to resize the vCenter partition by help of this article: https://vm.knutsson.it/2018/07/10fb-does-not-support-flow-control-autoneg/#more-749 .
For the first step I'll limit Event log to 14 days which should be enough to keep SEAT partition free.
