WCP crashed while starting

[luizitano]

Hi,

When i try to start the WCP service i have a error:

"crashed while starting"

i haved checked the wcp logs and i have:

root@vCSA-001 [ /var/log/vmware/wcp ]# tail -f /var/log/vmware/wcp/wcpsvc.log
2022-11-08T15:59:56.207Z info wcp [vchelper/extension_monitor.go:129] [opID=extmon] ExtMon will retry PC WFU loop; interval: 5s
2022-11-08T15:59:56.293Z error wcp [vcmonitor/view_monitor.go:145] [opID=ViewMon-ClusterComputeResource] WaitForUpdates for object ClusterComputeResource and view ContainerView:session[52f85300-fac0-4294-7062-95db17e0730f]520b8ff2-85a1-eb8d-27c9-56cc447f149a return error. Err Post "https://vCSA-001.vmware..com:443/sdk": dial tcp 127.0.0.1:443: connect: connection refused
2022-11-08T15:59:56.297Z info wcp [vcmonitor/view_monitor.go:118] [opID=ViewMon-HostSystem] ViewMonitor for HostSystem canceled.
2022-11-08T16:00:01.208Z error wcp [vchelper/extension_monitor.go:153] [opID=extmon] ExtMon failed to create PC; err: Post "https://vCSA-001.vmware..com:443/sdk": dial tcp 127.0.0.1:443: connect: connection refused
2022-11-08T16:00:01.208Z info wcp [vchelper/extension_monitor.go:129] [opID=extmon] ExtMon will retry PC WFU loop; interval: 5s
2022-11-08T16:00:01.293Z info wcp [vcmonitor/view_monitor.go:118] [opID=ViewMon-ClusterComputeResource] ViewMonitor for ClusterComputeResource canceled.
2022-11-08T16:00:01.293Z debug wcp [httpproxy/vc_proxy_monitor.go:86] [opID=vcProxyMonitor] Stopping VcProxyMonitor.
2022-11-08T16:00:01.294Z debug wcp [lshelper/keepalive_handler.go:51] error logout ls client: Post "https://vCSA-001.vmware..com:443/ls/sdk": dial tcp 127.0.0.1:443: connect: connection refused
2022-11-08T16:00:01.296Z info wcp [cmd/main.go:706] Exiting the process
2022-11-08T16:00:01.296Z info wcp [notifications/notifications.go:220] Notifier stopped.

can you help me? 

[imthiachulu]

I had a similar issue in my lab, after troubleshooting for a couple of days, I was unable to find the root cause and ended up re-deploying it.

Few things you could share/try

 - If it is NSX-T backed, try Disabling and Enabling the Trust

 - More logs/Status of SupervisorVMs etc

 - Open a ticket with VMware Support