Maurizio71
Contributor
Contributor

vCenter 7.0.0c "vAPI Endpoint" service warning

After upgrade vCenter from version 7.0.0b to version 7.0.0c I got this warning on the service monitor:

Failed to connect to 7ae7cbaa-9164-47f7-a9f8-1d1da7e2746b\com.vmware.vcenter.nsxd.vapi vAPI provider.

Current vApi Endpoint health status is created between 2020-08-24T16:21:29UTC and 2020-08-24T16:21:30UTC.

I've these lines in the vapi/endpoint/endpoint.log:

2020-08-24T15:33:00.213Z | WARN  | state-manager1            | ApiInterfacesFactory           | Retrieving interfaces for service 7ae7cbaa-9164-47f7-a9f8-1d1da7e2746b\com.vmware.vcenter.nsxd.vapi has failed.

2020-08-24T15:33:00.214Z | WARN  | state-manager1            | ApiInterfacesFactory           | The cache does not contain entry for service 7ae7cbaa-9164-47f7-a9f8-1d1da7e2746b\com.vmware.vcenter.nsxd.vapi. The interfaces will be skipped.

2020-08-24T15:33:00.214Z | INFO  | state-manager1            | HealthStatusCollectorImpl      | HEALTH YELLOW Failed to connect to 7ae7cbaa-9164-47f7-a9f8-1d1da7e2746b\com.vmware.vcenter.nsxd.vapi vAPI provider.

Thanks

Maurizio

27 Replies
mattroslevich
Contributor
Contributor

Did restarting the vAPI Endpoint Service help it at all?

0 Kudos
Maurizio71
Contributor
Contributor

The service restarts correctly, but after some minutes the warning appears again.

0 Kudos
ThoDor
Contributor
Contributor

Hello,

I got the same issue.

In my case I did a new installation of vCenter 7c (Build 16620013) not upgrade.

Tried the "fix" for 6.5 (VMware Knowledge Base ) didn't work....

2020-08-25T07:37:07.677+02:00 | WARN  | state-manager1            | ApiInterfacesFactory           | The cache does not contain entry for service de7852f0-2ce4-40e7-b058-475f15dabdfe\com.vmware.vcenter.nsxd.vapi. The interfaces will be skipped.

2020-08-25T07:37:07.677+02:00 | INFO  | state-manager1            | HealthStatusCollectorImpl      | HEALTH YELLOW Failed to connect to de7852f0-2ce4-40e7-b058-475f15dabdfe\com.vmware.vcenter.nsxd.vapi vAPI provider.

2020-08-25T07:37:08.139+02:00 | INFO  | state-manager1            | HealthConfigurationEventListener | HEALTH Failed to connect to de7852f0-2ce4-40e7-b058-475f15dabdfe\com.vmware.vcenter.nsxd.vapi vAPI provider.

2020-08-25T07:37:08.139+02:00 | INFO  | state-manager1            | HealthConfigurationEventListener | HEALTH Current vApi Endpoint health status is created between 2020-08-25T07:37:07CEST and 2020-08-25T07:37:08CEST.

0 Kudos
alokpaul
Contributor
Contributor

I am also observing exactly the same issue after upgrading vCenter server to 7.0c.

0 Kudos
mattroslevich
Contributor
Contributor

Both my vSphere 7 clusters are on 7.0.0.c and both have this issue. I'm running the appliance-based vCenter 7.0.0.c, not the windows version. None of the previous versions fixes are helping.

0 Kudos
Maurizio71
Contributor
Contributor

I just re-installed from scratch, a new appliance-based VM with vCenter 7.0.0c (7.0.0.10600 build 16620007) and this issue is here again, so I think that it's a bug of this version.

0 Kudos
Maurizio71
Contributor
Contributor

vCenter 7.0.0d is out, I'll try if the upgrade solves the problem:

VMware-VCSA-all-7.0.0-16749653.iso

nachogonzalez
Commander
Commander

Last year we faced the same issue on VCSA 6.5, the problem was we were unable to upgrade due to bureaucracy and we were getting tons of tickets a day (and unable to delete them, also due to bureaucracy)

I figured out that if i ran this api call agains the VCSA i could know if VAPI endpoint was working or not.

GET https://{server}/rest/appliance/health/applmgmt

If you get any response from the api (not error 404 or 503) the vapi endpoint was working.

Just a manual way to test if the service was working

0 Kudos
Maurizio71
Contributor
Contributor

The VAPI endpoint is working, I got this response:

{"value":"green"}

0 Kudos
mattroslevich
Contributor
Contributor

Is that after you tried 7.0d? Or on 7.0c yet?

0 Kudos
nachogonzalez
Commander
Commander

I'm pretty sure this might be a bug.
Do you have the ability to create a SR?

0 Kudos
Maurizio71
Contributor
Contributor

It's on the 7.0c.

0 Kudos
Maurizio71
Contributor
Contributor

I don't think I can create a SR.

0 Kudos
mattroslevich
Contributor
Contributor

I created an SR a little bit ago. If I hear back from VMWare Support, I'll say something here.

0 Kudos
nachogonzalez
Commander
Commander

Thanks!

0 Kudos
ThoDor
Contributor
Contributor

Well yesterday I tried to "Update" my VCSA 7.0.0c with 7.0.0d UI-Installer.

Got the Message, that the installed Version can't be updated to 7.0.0d.

Since I didn't wanted to reinstall completly I waited.

This morning I got the notification, that I can update the VCSA with build in Update function.

Because my environment isn't productiv I gave it a try.

It took pretty long downtime (50MBit/s WAN Link) isn't the best ...

Likewise 45 Minutes.

The Update was successfully:

After the Update I still had the Error with vAPI Endpoint Service.

I used:

service-control --stop vmware-content-library;service-control --start vmware-content-library

And restarted vAPI-Endpoint too, after some minutes I got the same Error again.

I mean the patch notes told only to fix high CPU load, not our issue.

mattroslevich​ did you got an answer already?

0 Kudos
mariss35
Contributor
Contributor

i didnt had this error with 7.0.0c , but it came up after upgrade to 7.0.0d on 2 separate deployments.

Failed to connect to xxxxxxxxxxxxxxxxxxxxxx\com.vmware.vcenter.nsxd.vapi vAPI provider.

Current vApi Endpoint health status is created between xxxxxxxxxUTC and xxxxxxxxxUTC.

p.s. it does actually looks like VMware Knowledge Base

nachogonzalez
Commander
Commander

scott28tt​ people here are suspecting about a bug in a feature.
Do you know whom can we reach in the forum?

0 Kudos
mattroslevich
Contributor
Contributor

No, I didn't get a response yet. Though, it does look like what mariss35​ said in their post:

i didnt had this error with 7.0.0c , but it came up after upgrade to 7.0.0d on 2 separate deployments.

Failed to connect to xxxxxxxxxxxxxxxxxxxxxx\com.vmware.vcenter.nsxd.vapi vAPI provider.

Current vApi Endpoint health status is created between xxxxxxxxxUTC and xxxxxxxxxUTC.

p.s. it does actually looks like VMware Knowledge Base

Hopefully it is something ignorable, but one would think it'd be something they want to squash quickly...

Once I hear from VMware, I'll let you all know.

0 Kudos