Performing a vMotion using vCenter Appliance 5.1 or 5.5 fails with the error: pbm.fault.pdm.fault.summary

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Cannot vMotion a virtual machine using vCenter Server Appliance 5.1 or 5.5
  
  
• You are unable to clone the virtual machine.
  
  
• Performing a vMotion using vCenter Server Appliance 5.1 or 5.5 fails
  
  
• You see the error:
  
  pbm.fault.pdm.fault.summary
  
  
• In the /var/log/vmware/vpx/vpxd.log file, you see entries similar to:

mem> <YYYY-MM-DD>T<time>Z [7FA60BAF5700 error 'commonvpxLro' opID=2601768D-00000B2F-bd-3c] [VpxLRO] Unexpected Exception: pbm.fault.PBMFault</time>
mem> 2013-10-14T18:45:32.536Z [7FA60BAF5700 verbose 'commonvpxLro' opID=2601768D-00000B2F-bd-3c] [VpxLRO] Backtrace:
mem> --> backtrace[00] rip 00007fa6e0b47344 Vmacore::System::Stacktrace::CaptureWork(unsigned int)
mem> --> backtrace[01] rip 00007fa6e0a30082 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
mem> --> backtrace[02] rip 00007fa6e09917f5 Vmacore::Throwable::Throwable(std::string const&)
mem> --> backtrace[03] rip 00007fa6e1c3d583 Pbm::Fault::PBMFault::Throw()

mem> <YYYY-MM-DD>T<time></time>Z [7FA60BAF5700 info 'commonvpxLro' opID=2601768D-00000B2F-bd-3c] [VpxLRO] -- FINISH task-internal-844249 -- -- VmprovWorkflow --
mem> <YYYY-MM-DD>T<time></time>Z [7FA60BAF5700 info 'Default' opID=2601768D-00000B2F-bd-3c] [VpxLRO] -- ERROR task-internal-844249 -- -- VmprovWorkflow: pbm.fault.PBMFault:
mem> --> Result:
mem> --> (pbm.fault.PBMFault) {
mem> --> dynamicType = <unset>,
mem> --> faultCause = (vmodl.MethodFault) null,
mem> --> msg = "Received SOAP response fault from [<cs p:00007fa660be95e0, TCP:localhost:443>]: queryAssociatedProfiles
mem> --> com.vmware.vim.query.client.exception.ClientException: org.apache.http.conn.HttpHostConnectException: Connection to https://192.168.15.20:10443 refused",
mem> --> }
mem> --> Args:
mem> -->
mem> <YYYY-MM-DD>T<time></time>Z [7FA60BAF5700 error 'Default' opID=2601768D-00000B2F-bd] (Log recursion level 2) pbm.fault.PBMFault

• In the /var/log/vmware/vpx/inventoryservice/ds.log file, you see entries indicating that the inventory service has failed:
  
  [<YYYY-MM-DD>T<time> WrapperListener_start_runner INFO com.vmware.vim.vmomi.server.http.impl.TcServer] Starting server on [HTTP:0.0.0.0:10080, HTTPS:0.0.0.0:10443]
  [<YYYY-MM-DD>T<time> WrapperListener_start_runner FATAL com.vmware.vim.dataservices.WrapperListenerImpl] Error starting service:
  org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataservice' defined in class path resource [server/config/server-config.xml]: Invocation
  of init method failed; nested exception is java.lang.OutOfMemoryError: unable to create new native thread
  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1336)
  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:471)
  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
  at java.security.AccessController.doPrivileged(Native Method)</time></time>

Cause

This issue occurs if the inventory service fails to start because of an incorrect DNS entry.

Note: Running the service vmware-inventoryservice status command may show the inventory service as started.

Resolution

To resolve this issue, start the inventory service on the vCenter Server Appliance.

To start the inventory service on the vCenter Server Appliance:

1. Connect to the vCenter Server Appliance server console and log in as root
2. Run this command to start the Inventory Service:
   
   service vmware-inventoryservice start

Additional Information

vCenter Appliance 5.1 を使用した vMotion の実行が失敗し、次のエラーが表示される： pbm.fault.pdm.fault.summary
使用 vCenter Appliance 5.1 执行 vMotion 失败并出现错误：pbm.fault.pdm.fault.summary