4 Replies Latest reply on May 22, 2020 12:29 AM by PeterCr

    vapi-endpoint status changed from green to yellow

    Speccyfan Lurker

      Hello All!

      I have a problem.I get the following message:

      Target: Datacenters

      Stateless event alarm

       

      Alarm Definition:

      ([Event alarm expression: Status change])

       

      Event details:

      vapi-endpoint status changed from green to yellow

      The status changes from green to yellow, and then back again, this takes place several times a day.

      I read it, but did not find the answer

      VMware Validated Design for Software-Defined Data Center 3.0


      That's what I see in the

      /var/log/vmware/vapi/endpoint/endpoint.log

      2016-10-11T17:18:56.052+03:00 | WARN | state-manager1 | ApiInterfacesFactory | Retrieving interfaces for service f7fb8c35-4220-4ba8-ad0b-7639dd20cdf4\com.vmware.cis.ds has failed.

      com.vmware.vapi.internal.core.abort.RequestAbortedException: Http request aborted.

      at com.vmware.vapi.internal.protocol.common.Util$1.onAbort(Util.java:68)

              at com.vmware.vapi.internal.core.abort.AbortHandleImpl.abort(AbortHandleImpl.java:39)

              at com.vmware.vapi.endpoint.api.TimedApiProvider$1.run(TimedApiProvider.java:58)

              at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

              at java.util.concurrent.FutureTask.run(Unknown Source)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

              at java.lang.Thread.run(Unknown Source)

       

      I tried to restart the vmware-vapi-endpoint, but it does not help


      I use vCenter Server Appliance 6.0.0  Build 3634794.

       

      Please help solve the problem.

        • 1. Re: vapi-endpoint status changed from green to yellow
          Terminatorthree Lurker

          Hi,

           

          I'm currently running into the exact same problem. It did not occur a while ago and only affects one of our vCenters.

          Additionally it does not happen with every refresh cycle so the error comes and goes.

           

          Have you found any cause for the problem?

          • 2. Re: vapi-endpoint status changed from green to yellow
            Terminatorthree Lurker

            Hi,

             

            quick update: This is a known issue covered in KB 2144715. The fix will be included in 6.0u3

             

            This has been confirmed by VMware support.

            • 3. Re: vapi-endpoint status changed from green to yellow
              theonion Lurker

              I still have this issue even after u3.  As mentioned, the issue comes and goes.  Does anyone else still have the issue after applying u3?

               

              Restarting the vAPIendpoint service also does not fix the issue.  Usually I need to restart the webservice as well.

              • 4. Re: vapi-endpoint status changed from green to yellow
                PeterCr Novice
                vExpert

                Yes, I'm seeing same error as the original poster but on 6.7.
                Happens once per day and clears after 5 minutes.

                 

                2020-05-20T23:00:20.276+12:00 | WARN  | state-manager1            | ApiInterfacesFactory           | Retrieving interfaces for service xxxxxxxxxxxxxxxxxxxxxxxxxxxx\com.vmware.applmgmt has failed.

                com.vmware.vapi.internal.core.abort.RequestAbortedException: Http request aborted.

                at com.vmware.vapi.internal.protocol.common.Util$1.onAbort(Util.java:68)

                at com.vmware.vapi.internal.core.abort.AbortHandleImpl.abort(AbortHandleImpl.java:39)

                at com.vmware.vapi.endpoint.api.TimedApiProvider$1.run(TimedApiProvider.java:58)

                at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

                at java.util.concurrent.FutureTask.run(FutureTask.java:266)

                at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

                at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                at java.lang.Thread.run(Thread.java:748)