Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

vCenter Server 5.0 fails with the error: Panic: Not Reached (2033163)

Symptoms

  • vCenter Server starts, but the service fails almost immediately
  • In the vpxd.log file, you see entries similar to:

    2012-03-26T00:05:37.236Z [07844 panic 'Default' opID=task-117493-81bb3a7f-a8] Duplicate key 'key-vim.host.PlugStoreTopology.Target-fc.500a09808799afb8:500a09859799afb8' in linkable vim.host.PlugStoreTopology.Target referenced by field target (wsdl name target)

    2012-03-26T00:08:35.154Z [07844 info 'Default' opID=task-117493-81bb3a7f-a8] CoreDump: Writing minidump

    2012-03-26T00:08:54.951Z [07844 panic 'Default' opID=task-117493-81bb3a7f-a8]
-->
--> Panic: Not Reached: @ d:/build/ob/bora-623373/bora/vim/lib/vmomi/link.cpp:105

Resolution

This is a known issue in vCenter Server 5.0, and is currently being reviewed by VMware. This article will be updated as information becomes available.
 
To work around this issue:
  1. Open a Windows Explorer window and navigate to the location of the vCenter Server configuration data:

    Windows Server 2008 – C:\ProgramData\VMware\VMware VirtualCenter
    Windows Server 2003 – C:\Documents and Settings\All Users\VMware\Application Data\VMware\VMware VirtualCenter

  2. Take a backup of the vpxd.cfg file.
  3. Open the vpxd.cfg file using a text editor.
  4. Add this entry within the <vmomi> and </vmomi> tags:

    <panicOnLinkErrors>false</panicOnLinkErrors>

  5. Add these entries within the <vpxd> and </vpxd> tags.

    <orm>
    <verifyLinksOnLoad>false</verifyLinksOnLoad>
    </orm>


    Notes:
    • The <vmomi> and </vmomi> tags must be located before the <vpxd> and </vpxd> tags.
    • If the <vmomi> and </vmomi> tags do not exist, add them before the <vpxd> and </vpxd> tags.

      Here is an example of the vpxd.cfg  with fields added:

      <vmomi>
      <panicOnLinkErrors>false</panicOnLinkErrors>
      </vmomi>
      <vpxd>
      <das>
      <serializeadds>true</serializeadds>
      <slotMemMinMB>256</slotMemMinMB>
      <slotCpuMinMHz>256</slotCpuMinMHz>
      </das>
      <filterOverheadLimitIssues>true</filterOverheadLimitIssues>
      <orm>
      <verifyLinksOnLoad>false</verifyLinksOnLoad>
      </orm>
      </vpxd>
      <vmacore>
      <threadPool>
      <TaskMax>30</TaskMax>
      <IoMax>200</IoMax>
      </threadPool>
      </vmacore>
      </config>


  6. Restart vCenter Server services.

Note: If you need assistance in making these configuration changes, contact VMware Technical Support.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 13 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 13 Ratings
Actions
KB: