使用 vCenter Appliance 5.1 执行 vMotion 失败并出现错误:pbm.fault.pdm.fault.summary
search cancel

使用 vCenter Appliance 5.1 执行 vMotion 失败并出现错误:pbm.fault.pdm.fault.summary

book

Article ID: 338100

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
免责声明:本文为 Performing a vMotion using vCenter Appliance 5.1 fails with the error: pbm.fault.pdm.fault.summary (2062112) 的翻译版本。尽管我们会不断努力为本文提供最佳翻译版本,但本地化的内容可能会过时。有关最新内容,请参见英文版本。


  • 无法使用 vCenter Server Appliance 5.1 对虚拟机执行 vMotion
  • 使用 vCenter Server Appliance 5.1 执行 vMotion 失败
  • 您会看到以下错误:

    pbm.fault.pdm.fault.summary

  • vpxd.log 文件(位于 C:\Documents and Settings\All Users\Application Data\VMware\VirtualCenter\logs)中,您会看到类似于以下内容的条目:

mem> <YYYY-MM-DD>T<time>Z [7FA60BAF5700 error 'commonvpxLro' opID=2601768D-00000B2F-bd-3c] [VpxLRO] Unexpected Exception: pbm.fault.PBMFault
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()

</time>

mem><YYYY-MM-DD>T<time>Z [7FA60BAF5700 info 'commonvpxLro' opID=2601768D-00000B2F-bd-3c] [VpxLRO] -- FINISH task-internal-844249 -- -- VmprovWorkflow --
mem><YYYY-MM-DD>T<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>Z [7FA60BAF5700 error 'Default' opID=2601768D-00000B2F-bd] (Log recursion level 2) pbm.fault.PBMFault</time></time></time>

<?xml:namespace prefix = vmacore /><vmacore::system::backtrace>
  • ds.log 文件(位于 /var/log/vmware/vpx/inventoryservice)中,您会看到以下指示 Inventory Service 已失败的条目:

    [<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>
</vmacore::system::backtrace>

Environment

VMware vCenter Server Appliance 5.1.x

Cause

如果 Inventory Service 无法启动(可能是由于 DNS 条目不正确),则会出现此问题。
注意:运行 chkconfig 命令可能会将 Inventory Service 显示为已启动。

Resolution

要解决此问题,请在 vCenter Server Appliance 上启动 Inventory Service。
要在 vCenter Server Appliance 上启动 Inventory Service,请执行以下操作:
  1. 连接到 vCenter Server Appliance 服务器控制台并以 root 身份登录
  2. 运行以下命令以启动 Inventory Service:

    service vmware-inventoryservice start


Additional Information

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