vcsa6.5u2b Services won't start after appliance restart

[bsnvmw]

After the restart of vcsa 6.5u2b, the services cannot be started. I plan to manually start it according to the profit and loss sequence. Do you have any other Suggestions?

What is the order in which services are started manually?

Do you have the same problem?

The vcenter HA  has installed, but both the primary and the standby vcsa cannot start the services

[a_p_ · Accepted solution]

It's hard to help without knowing any details.

Please take a look at the log files, to see whether they contain useful details (e.g. the vpxd logs).

André

[bsnvmw]

hellow,

Some log information is described below.

2019-04-12T06:36:56.512Z info vpxd[7F0D8A74C700] [Originator@6876 sub=vpxLro opID=3da2aec4] [VpxLRO] -- BEGIN lro-15124403 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.512Z info vpxd[7F0D8A74C700] [Originator@6876 sub=vpxLro opID=3da2aec4] [VpxLRO] -- FINISH lro-15124403

2019-04-12T06:36:56.513Z info vpxd[7F0CCF878700] [Originator@6876 sub=vpxLro opID=37fe579] [VpxLRO] -- BEGIN lro-15124404 -- PerfMgr -- vim.PerformanceManager.queryStats -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.518Z info vpxd[7F0EDD03C700] [Originator@6876 sub=vpxLro opID=41b26cba] [VpxLRO] -- BEGIN lro-15124405 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.518Z info vpxd[7F0EDD03C700] [Originator@6876 sub=vpxLro opID=41b26cba] [VpxLRO] -- FINISH lro-15124405

2019-04-12T06:36:56.520Z info vpxd[7F0CD5AB5700] [Originator@6876 sub=vpxLro opID=29004908] [VpxLRO] -- BEGIN lro-15124406 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.520Z info vpxd[7F0CD5AB5700] [Originator@6876 sub=vpxLro opID=29004908] [VpxLRO] -- FINISH lro-15124406

2019-04-12T06:36:56.523Z info vpxd[7F0ED6CD9700] [Originator@6876 sub=vpxLro opID=51bac13f] [VpxLRO] -- BEGIN lro-15124407 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.523Z info vpxd[7F0ED6CD9700] [Originator@6876 sub=vpxLro opID=51bac13f] [VpxLRO] -- FINISH lro-15124407

2019-04-12T06:36:56.526Z info vpxd[7F0CD664C700] [Originator@6876 sub=vpxLro opID=3be53904] [VpxLRO] -- BEGIN lro-15124408 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52dce1c6-1aa0-6872-38ab-7408457233fa(521d318c-6564-1e61-635a-cd1e5e05b607)

2019-04-12T06:36:56.526Z info vpxd[7F0CD664C700] [Originator@6876 sub=vpxLro opID=3be53904] [VpxLRO] -- FINISH lro-15124408

2019-04-12T06:36:56.545Z error vpxd[7F0ED7E7C700] [Originator@6876 sub=MoHost] Response from host host-271 is null, even though no error received

2019-04-12T06:36:56.545Z error vpxd[7F0ED7E7C700] [Originator@6876 sub=MoHost] [HandleAsyncQueryPerfResultsDoFinally] The RPC for host host-271 completed with status code 3

2019-04-12T06:36:56.546Z error vpxd[7F0D88202700] [Originator@6876 sub=MoHost] Response from host host-1758 is null, even though no error received

2019-04-12T06:36:56.546Z error vpxd[7F0D88202700] [Originator@6876 sub=MoHost] [HandleAsyncQueryPerfResultsDoFinally] The RPC for host host-1758 completed with status code 3

2019-04-12T06:36:56.555Z info vpxd[7F0CCF878700] [Originator@6876 sub=vpxLro opID=37fe579] [VpxLRO] -- FINISH lro-15124404

2019-04-12T06:36:56.853Z info vpxd[7F0D8B66A700] [Originator@6876 sub=vpxLro opID=LVM Relevance add :200238:01-b7] [VpxLRO] -- BEGIN lro-15124410 -- ResourceModel -- cis.data.provider.ResourceModel.query -- 52a870f2-4406-6b32-1175-0865dde2f339(52dec021-41d2-e276-3289-a04aa7d714fe)

2019-04-12T06:36:56.853Z info vpxd[7F0D8B66A700] [Originator@6876 sub=vpxLro opID=LVM Relevance add :200238:01-b7] [VpxLRO] -- FINISH lro-15124410

2019-04-12T06:36:56.868Z info vpxd[7F0CD5A34700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213030-h5c-d7] [VpxLRO] -- BEGIN lro-15124411 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 525489ec-21e6-2fe0-3a4d-f9ead54ef50b(52433bac-bcec-bc12-1223-fbf3b7c32ccf)

2019-04-12T06:36:56.869Z info vpxd[7F0CD5A34700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213030-h5c-d7] [VpxLRO] -- FINISH lro-15124411

2019-04-12T06:36:56.869Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213033-h5c-ea] [VpxLRO] -- BEGIN lro-15124414 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 52ef08e7-7a40-07ad-17ad-ee4bfc3a1d8a(521e0bbd-c77b-5e78-5acc-1f24381508e4)

2019-04-12T06:36:56.869Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213034-h5c-a0] [VpxLRO] -- BEGIN lro-15124417 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 521053d9-2d1c-cb89-b039-d6887f94838b(52502c8c-b58e-7d2a-9684-7154095bd599)

2019-04-12T06:36:56.869Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213033-h5c-ea] [VpxLRO] -- FINISH lro-15124414

2019-04-12T06:36:56.869Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213031-h5c-0] [VpxLRO] -- BEGIN lro-15124415 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 5248c635-1f16-4245-91e4-c4c8e4313259(52fc3638-dcc0-d400-debe-15cfee311311)

2019-04-12T06:36:56.869Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213034-h5c-a0] [VpxLRO] -- FINISH lro-15124417

2019-04-12T06:36:56.869Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=a5a906de-ff9d-4f61-884f-402e821796d0-420045-ngc-4] [VpxLRO] -- BEGIN lro-15124416 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 5265c9e3-28c4-8fd6-02f2-fb1f0db3d093(525bb486-531e-632b-1ca3-0a3e26b53a11)

2019-04-12T06:36:56.869Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213031-h5c-0] [VpxLRO] -- FINISH lro-15124415

2019-04-12T06:36:56.869Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213032-h5c-a2] [VpxLRO] -- BEGIN lro-15124413 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 52015a6d-40f4-4c14-d982-66a59300a2f5(5237d3cc-eb78-9875-75fd-4285f64f8f61)

2019-04-12T06:36:56.870Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=a5a906de-ff9d-4f61-884f-402e821796d0-420045-ngc-4] [VpxLRO] -- FINISH lro-15124416

2019-04-12T06:36:56.870Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=a5a906de-ff9d-4f61-884f-402e821796d0-420044-ngc-b] [VpxLRO] -- BEGIN lro-15124412 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 527d751c-c4b5-e139-8101-bcb593a8eef8(52ee78c3-92e2-f6f0-effd-f69f1042b5de)

2019-04-12T06:36:56.870Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=270ce947-80e6-40c2-9e0a-0bf4462a9af3-1213032-h5c-a2] [VpxLRO] -- FINISH lro-15124413

2019-04-12T06:36:56.870Z info vpxd[7F0D88A93700] [Originator@6876 sub=vpxLro opID=a5a906de-ff9d-4f61-884f-402e821796d0-420046-ngc-9c] [VpxLRO] -- BEGIN lro-15124418 -- ChangeLogCollector -- vim.cdc.ChangeLogCollector.waitForChanges -- 52baab95-687e-d718-54d6-62b3bf586bfb(524649f9-e0e6-b7fd-f2e5-6048cc5e15d1)

2019-04-12T06:36:56.870Z info vpxd[7F0EDC2A1700] [Originator@6876 sub=vpxLro opID=a5a906de-ff9d-4f61-884f-402e821796d0-420044-ngc-b] [VpxLRO] -- FINISH lro-15124412

[bsnvmw]

Hello, can you check the log information to find the root cause of the failure and give a solution？

thanks very much!

[a_p_]

The log contains many network, name resolution, and user authentication errors.

Can you confirm that the network is configured properly, and name resolution works?

What happened prior to this? Did this happen right after setting up vCenter HA?

In case this is a lab/test environment you may try to destroy vCenter HA, and set it up again.

In case of a production system, I suggest that you open a support case with VMware.

André

[bsnvmw]

thanks!

The problem has been solved

The problem is that the vcsa is sent a connection request by a monitoring application through a disabled account (h-xxx) and always fails to verify, occupying the maximum sesion of the vcsa and causing the service access to fail.

If vcsa cannot be restored, you can also refer to the following KB for recovery;

https://kb.vmware.com/s/article/2091961?lang=zh_CN