java.lang.Exception: Failed to ping VSA service on VM 172.16.100.34

vjswami.com | 7 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Getting the VMware VSA running in a nested ESXi environment – VIJAY SWAMI

    vjswami.com | 1 year ago
    java.lang.Exception: Failed to ping VSA service on VM 172.16.100.34
  2. 0

    Getting the VMware VSA running in a nested ESXi environment – VIJAY SWAMI

    vjswami.com | 7 months ago
    java.lang.Exception: Failed to ping VSA service on VM 172.16.100.34

    Root Cause Analysis

    1. java.lang.Exception

      Failed to ping VSA service on VM 172.16.100.34

      at com.vmware.sva.manager.config.SVAVMConfigurator.connectToSVAService()
    2. com.vmware.sva
      SVAVMConfigurator.call
      1. com.vmware.sva.manager.config.SVAVMConfigurator.connectToSVAService(SVAVMConfigurator.java:392)
      2. com.vmware.sva.manager.config.SVAVMConfigurator.attemptSVAConnect(SVAVMConfigurator.java:240)
      3. com.vmware.sva.manager.config.SVAVMConfigurator.initializeVM(SVAVMConfigurator.java:175)
      4. com.vmware.sva.manager.config.SVAVMConfigurator.customizeSvaVM(SVAVMConfigurator.java:509)
      5. com.vmware.sva.manager.config.SVAVMConfigurator.call(SVAVMConfigurator.java:445)
      6. com.vmware.sva.manager.config.SVAVMConfigurator.call(SVAVMConfigurator.java:61)
      6 frames
    3. Java RT
      Thread.run
      1. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      2. java.util.concurrent.FutureTask.run(FutureTask.java:138)
      3. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      5. java.lang.Thread.run(Thread.java:662)
      5 frames