<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cannot Start vCenter Server Appliance - &amp;quot;Waiting for vpxd to initialize: ....failed&amp;quot; in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349420#M43307</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;fresh install only option.&amp;nbsp; vmware support takes 3 days to even come up with anything.. even for a sev1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Mar 2013 04:21:27 GMT</pubDate>
    <dc:creator>lubela</dc:creator>
    <dc:date>2013-03-05T04:21:27Z</dc:date>
    <item>
      <title>Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349411#M43298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am stumped. At first, I was able to at least login to vsphere and do operations. The client would close like every 15 minutes so it got really annoying. Now I am stuck with no launch to vsphere. I must log into each host individually. ESXi hosts without a vsphere is so limited. Please advise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the /var/log/messages&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;vsphere-fmrif:~ # tail -f /var/log/messages&lt;BR /&gt;May 31 09:50:32&amp;nbsp; vsphere-fmrif watchdog-vpxd: [4773] Begin '/usr/sbin/vpxd', min-uptime =&amp;nbsp; 30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file =&amp;nbsp; ''&lt;BR /&gt;May 31 09:50:32 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May&amp;nbsp; 31 09:50:34 vsphere-fmrif kernel: [&amp;nbsp;&amp;nbsp; 59.780777] warning: process&amp;nbsp; `vpxd-worker' used the deprecated sysctl system call with 1.1.&lt;BR /&gt;May 31 09:50:40 vsphere-fmrif sshd[4944]: Accepted password for root from 128.231.212.117 port 51160 ssh2&lt;BR /&gt;May 31 09:50:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 12 seconds (quick failure 1) 134&lt;BR /&gt;May 31 09:50:44 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May 31 09:50:45 vsphere-fmrif kernel: [&amp;nbsp;&amp;nbsp; 70.438974] warning: process `vpxd' used the deprecated sysctl system call with 1.1.&lt;BR /&gt;May 31 09:50:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 2) 134&lt;BR /&gt;May 31 09:50:51 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May 31 09:50:52 vsphere-fmrif kernel: [&amp;nbsp;&amp;nbsp; 77.370397] warning: process `vpxd' used the deprecated sysctl system call with 1.1.&lt;BR /&gt;May 31 09:50:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 3) 134&lt;BR /&gt;May 31 09:50:58 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May 31 09:50:58 vsphere-fmrif kernel: [&amp;nbsp;&amp;nbsp; 83.923261] warning: process `vpxd' used the deprecated sysctl system call with 1.1.&lt;BR /&gt;May 31 09:51:05 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 7 seconds (quick failure 4) 134&lt;BR /&gt;May 31 09:51:05 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May&amp;nbsp; 31 09:51:06 vsphere-fmrif kernel: [&amp;nbsp;&amp;nbsp; 91.720959] warning: process&amp;nbsp; `vpxd-worker' used the deprecated sysctl system call with 1.1.&lt;BR /&gt;May 31 09:51:12 vsphere-fmrif auditd[3012]: Audit daemon rotating log files&lt;BR /&gt;May 31 09:51:13 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 8 seconds (quick failure 5) 134&lt;BR /&gt;May 31 09:51:13 vsphere-fmrif watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;BR /&gt;May 31 09:51:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 6 seconds (quick failure 6) 134&lt;BR /&gt;May 31 09:51:19 vsphere-fmrif watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/var/log/warn&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;May 31 02:40:23 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:41:26 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:42:28 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:43:31 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:44:33 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:45:36 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:46:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:47:41 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:48:44 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:49:46 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:50:49 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:51:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:52:54 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:53:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:54:59 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:56:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:57:04 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 02:58:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 02:59:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:00:12 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:01:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:01:52 vsphere-fmrif portmap[25177]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:01:52 vsphere-fmrif portmap[25178]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:01:53 vsphere-fmrif portmap[25179]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:02:17 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:03:07 vsphere-fmrif portmap[25275]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:03:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:04:04 vsphere-fmrif portmap[25358]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:04:19 vsphere-fmrif portmap[25368]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:04:22 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:05:25 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:06:01 vsphere-fmrif portmap[25531]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:06:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:06:31 vsphere-fmrif portmap[25603]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:07:00 vsphere-fmrif portmap[25618]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:07:30 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:08:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:09:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:10:38 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:11:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:12:20 vsphere-fmrif portmap[26072]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:12:43 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:12:54 vsphere-fmrif portmap[26144]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:13:45 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:13:48 vsphere-fmrif portmap[26227]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:14:17 vsphere-fmrif portmap[26242]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:14:48 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:15:09 vsphere-fmrif portmap[26348]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:15:17 vsphere-fmrif portmap[26354]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:15:51 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:16:03 vsphere-fmrif portmap[26435]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:16:53 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:16:53 vsphere-fmrif portmap[26472]: connect from 128.231.212.177 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:16:59 vsphere-fmrif portmap[26519]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:17:56 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:18:30 vsphere-fmrif portmap[26621]: connect from 128.231.212.121 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:18:58 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:20:01 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:21:03 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:21:37 vsphere-fmrif portmap[26897]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:22:06 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:23:09 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:24:11 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:24:22 vsphere-fmrif portmap[27146]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:25:14 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:26:16 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:26:40 vsphere-fmrif portmap[27330]: connect from 128.231.212.168 to callit(390109): request from unauthorized host&lt;BR /&gt;May 31 03:27:19 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:28:21 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:29:24 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:30:27 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:31:29 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:32:32 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:33:35 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;BR /&gt;May 31 03:34:37 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 62 seconds 1&lt;BR /&gt;May 31 03:35:40 vsphere-fmrif watchdog-vpxd: '/usr/sbin/vpxd' exited after 63 seconds 1&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/var/log/vmware/vpx/vpxd.log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;
&lt;P&gt;From earlier:&lt;/P&gt;
&lt;P&gt;vsphere-fmrif:~ # tail -f -n 100 /var/log/vmware/vpx/vpxd.log&lt;/P&gt;
&lt;P&gt;Section for VMware VirtualCenter, pid=25488, version=5.0.0, build=build-455964, option=Release&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;------ In-memory logs start --------&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.623-04:00 [7FFFF3B09700 info 'Hooks'] Hooks Initialized&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;------ In-memory logs end&amp;nbsp;&amp;nbsp; --------&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.633-04:00 [7FFFF3B09700 info 'Default'] Initialized channel manager&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.641-04:00 [7FFFF3B09700 info 'Default'] Current working directory: /storage/log/vmware/vpx&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Log path: /var/log/vmware/vpx&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.642-04:00 [7FFFF3B09700 info 'Default'] Initializing SSL&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.645-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] Vmacore::InitSSL: doVersionCheck = true,&amp;nbsp; handshakeTimeoutUs = 120000000&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.646-04:00 [7FFFF3B09700 info 'Default'] Changed working directory to /var/log/vmware/vpx&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Starting VMware VirtualCenter 5.0.0 build-455964&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.666-04:00 [7FFFF3B09700 info 'Default'] Log directory: /var/log/vmware/vpx.&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] Account name: root&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:835] Calling: InfoDeclSchema(gDB)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [Init:837] Calling:&amp;nbsp; VpxCallbackDesc::Init(MakeFunctor(this,&amp;nbsp; &amp;amp;ServerApp::RequestShutdown))&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:838] Calling: VpxCryptInit()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:839] Calling: VpxLRO::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:840] Calling: VpxLroList::Init(ltud)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 640 max LROs&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved internal LROs&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved blocker LROs&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 12 reserved short LROs&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 8 reserved long LROs&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second completed task lifetime&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 60-second minimum completed task lifetime&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 200 maximum completed tasks&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [VpxLRO] 600-second unregistered task lifetime&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:841] Calling: VpxdCharacterizeThreadpool(ltud)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00&amp;nbsp; [7FFFF3B09700 info 'ThreadPool'] [SetConfig] Thread info: IoMin: 2,&amp;nbsp; IoMax: 1990, TaskMin: 59, TaskMax: 1990, Max Thread: 3980, Keepalive:&amp;nbsp; 61, thread kill: 600, max fds: -1&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.667-04:00 [7FFFF3B09700 info 'Default'] [Init:842] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.668-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [Init:843] Calling:&amp;nbsp; VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:29.668-04:00 [7FFFF3B09700 info 'Default'] Registry Item DB 5 value is ''&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.078-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB]&amp;nbsp; Loaded schema and index information from DB&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.099-04:00 [7FFFF3B09700 info 'Default'] [Init:844] Calling: VpxdDbSchemaHash::CheckSchema()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.100-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [VpxdDbSchemaHash::CheckSchema]: schema&amp;nbsp; file: /usr/lib/vmware-vpx/VCDB_db2.sql&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.104-04:00 [7FFFF3B09700 info 'Default'] [Init:845] Calling: VpxdDbMonitoring::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.120-04:00 [7FFFF3B09700 info 'Default'] [Init:848] Calling: VpxdLdap::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.121-04:00 [7FFFF3B09700 info 'Default'] [LdapBackup] Checking service ldap for running&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.179-04:00 [7FFFF3B09700 info 'Default'] [Init:849] Calling: VpxResultFilter::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.179-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] Looking for vpx result filter at&amp;nbsp; /usr/lib/vmware-vpx/vpxResultFilter.xml&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:853] Calling: VpxdLock::Init(gDB)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:854] Calling: VpxdMoLock::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:855] Calling: VpxdStateLock::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:856] Calling: VpxdMoDataTable::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [Init:858] Calling:&amp;nbsp; VpxdHeartbeat::Init(MakeFunctor(this, &amp;amp;ServerApp::RequestShutdown))&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.184-04:00 [7FFFF3B09700 info 'Default'] [Init:859] Calling: VpxdHostCnx::Init(gDB)&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.189-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Pre-loading symbols...&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.190-04:00 [7FFFEAA06710 info 'Default' opID=SWI-75fe915a] Done pre-loading symbols.&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.196-04:00 [7FFFF3B09700 info 'Default'] [Init:861] Calling: VpxdVmomi::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.198-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] Looking for vpx result filter at&amp;nbsp; /usr/lib/vmware-vpx/vpxResultFilter.xml&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.200-04:00 [7FFFF3B09700 info 'Default'] [Init:862] Calling: QueryServiceProviderHelper::Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.201-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Initializing QueryServiceProviderHelperImpl&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'QueryServiceProvider'] Starting with generation number: 5230290&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.240-04:00 [7FFFF3B09700 info 'Default'] [Init:863] Calling: ServiceDirectory_Init()&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.240-04:00&amp;nbsp; [7FFFF3B09700 info 'Default'] [ServiceDirectory] Local instance UUID:&amp;nbsp; DB25B17D-3703-4779-BAFB-845B64AC33AA&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.245-04:00 [7FFFF3B09700 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 2578 ms&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] [VpxdMain] Failed to initialize: Name or service not known&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...&lt;/P&gt;
&lt;P&gt;2012-05-31T09:11:32.246-04:00 [7FFFF3B09700 info 'Default'] Wrote uptime information&lt;/P&gt;
&lt;P&gt;2012-05-31T09:12:32.701-04:00 [7FFFF3B09700 info 'Default'] Forcing shutdown of VMware VirtualCenter now&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and the process itself&lt;/P&gt;&lt;BLOCKQUOTE&gt;vsphere-fmrif:~ # service vmware-vpxd status&lt;BR /&gt;vmware-vpxd is stopped&lt;BR /&gt;tomcat is stopped&lt;BR /&gt;vsphere-fmrif:~ # service vmware-vpxd start&lt;BR /&gt;Waiting for embedded DB2 database to startup: .success&lt;BR /&gt;Cleaning session lock table: success&lt;BR /&gt;Verifying EULA acceptance: success&lt;BR /&gt;Shutting down ldap-server..done&lt;BR /&gt;Starting ldap-server..done&lt;BR /&gt;Starting vmware-vpxd: success&lt;BR /&gt;Waiting for vpxd to initialize: ....failed&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 14:06:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349411#M43298</guid>
      <dc:creator>edmandsj</dc:creator>
      <dc:date>2012-05-31T14:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349412#M43299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sometimes this happens if you are using the built in DB and you configure your timezone.&amp;nbsp; the appliance will use UTC and if it is changed the local DB will not know how to access records in the future.&amp;nbsp; Did you change the timezone?&amp;nbsp; If so, you may try importing the appliance again and this time don't change the timezone.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 14:13:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349412#M43299</guid>
      <dc:creator>Troy_Clavell</dc:creator>
      <dc:date>2012-05-31T14:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349413#M43300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well the appliance has worked for the past 4-6 months. I'm not sure what would have changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are my options? Just thinking out loud below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fix Time zone settings or time settings on exisiting vCenter Appliance&lt;/P&gt;&lt;P&gt;Sync time somehow?&lt;/P&gt;&lt;P&gt;"Reset DB Contents" --&amp;gt; How disruptive is this? What will I lose?&lt;/P&gt;&lt;P&gt;Deploy new vCenter Appliance and Import old embedded database&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If all else fails and I need to use VDR to recover my vcenter server (to get the database), what will I need to do to put the database back in place?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 14:22:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349413#M43300</guid>
      <dc:creator>edmandsj</dc:creator>
      <dc:date>2012-05-31T14:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349414#M43301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;oh, may have found the culprit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vsphere-fmrif:~ # df -h&lt;BR /&gt;Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Size&amp;nbsp; Used Avail Use% Mounted on&lt;BR /&gt;/dev/sda3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 9.8G&amp;nbsp; 4.2G&amp;nbsp; 5.1G&amp;nbsp; 46% /&lt;BR /&gt;devtmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.0G&amp;nbsp; 104K&amp;nbsp; 2.0G&amp;nbsp;&amp;nbsp; 1% /dev&lt;BR /&gt;tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.0G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 2.0G&amp;nbsp;&amp;nbsp; 0% /dev/shm&lt;BR /&gt;/dev/sda1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 130M&amp;nbsp;&amp;nbsp; 18M&amp;nbsp; 105M&amp;nbsp; 15% /boot&lt;BR /&gt;&lt;STRONG&gt;/dev/sdb1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20G&amp;nbsp;&amp;nbsp; 20G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 100% /storage/core&lt;/STRONG&gt;&lt;BR /&gt;/dev/sdb2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20G&amp;nbsp; 892M&amp;nbsp;&amp;nbsp; 18G&amp;nbsp;&amp;nbsp; 5% /storage/log&lt;BR /&gt;/dev/sdb3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20G&amp;nbsp; 2.7G&amp;nbsp;&amp;nbsp; 17G&amp;nbsp; 14% /storage/db&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://vmwire.com/category/vcsa-2/"&gt;http://vmwire.com/category/vcsa-2/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 14:40:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349414#M43301</guid>
      <dc:creator>edmandsj</dc:creator>
      <dc:date>2012-05-31T14:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349415#M43302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So I cleared out the /storage/core mount point. It quickly fills up again, though. It's already at 25% again. Either way I still cannot login. It is most likely the time thing. If I change it back to the original time(not sure what it was at this point) what will happen?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you think rebuilding a new VCSA VM is the best possible way, just say so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;side note: backup database from /storage/db ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 16:40:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349415#M43302</guid>
      <dc:creator>edmandsj</dc:creator>
      <dc:date>2012-05-31T16:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349416#M43303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;a fresh start is always an option, but you'll have to add all your ESX Hosts back in, create any new Clusters, Resource Pools, etc.&amp;nbsp; My initial response was thinking you were just bringing the appliance on-line for the first time. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since this environment has been online for quite sometime, it may be worth your while to contact VMware Support to see if they can help in fixing the existing issue. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 16:43:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349416#M43303</guid>
      <dc:creator>Troy_Clavell</dc:creator>
      <dc:date>2012-05-31T16:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349417#M43304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Did you manage to resolve this without a fresh install? A month ago my friend came along and suggested that I should change the time to UTC, at that time vCenter and vpxd were working fine. I changed it. Now I am doing negative tests in my environment, and one of the tests was to restart the vpxd service and it is failing with the same error as you saw. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Even rebooting the vCenter vApp does not help. I get the same error failied to initialize vpxd.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Let me know how you resolved this issue. I can initialize the contents of the DB, but what I dont want to lose is the customized alarms and some defualt alarms that I modified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 14:39:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349417#M43304</guid>
      <dc:creator>roddam</dc:creator>
      <dc:date>2012-11-12T14:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349418#M43305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fresh install is the only remedy from what I could tell. Take it as an opportunity to check your settings and so on. Sorry man.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Justin Edmands&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 15:13:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349418#M43305</guid>
      <dc:creator>edmandsj</dc:creator>
      <dc:date>2012-11-12T15:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349419#M43306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this is going to be such a pain. I guess I will try a few things before I did that.&lt;/P&gt;&lt;P&gt;Yup, I will try to see the positive side of it! will be hard though &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 15:17:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349419#M43306</guid>
      <dc:creator>roddam</dc:creator>
      <dc:date>2012-11-12T15:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349420#M43307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;fresh install only option.&amp;nbsp; vmware support takes 3 days to even come up with anything.. even for a sev1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Mar 2013 04:21:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349420#M43307</guid>
      <dc:creator>lubela</dc:creator>
      <dc:date>2013-03-05T04:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349421#M43308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My lab instance, a vSphere 5.1 vCenter Server Appliance with 2 clusters, 8 hosts (all vSphere 5.1), 80 VMs, exhibits these exact same symptoms.&amp;nbsp; It is using the built in database, no external.&amp;nbsp;&amp;nbsp;&amp;nbsp; I can say for certain that the VCSA time zone has not been touched since initial install, so that is not the issue.&amp;nbsp;&amp;nbsp;&amp;nbsp; My issues started a couple of weeks ago or more.&amp;nbsp; The&amp;nbsp; vSphere Client would just crash every 15 minutes or so, but then I could log back in so I just did that and worked on other more pressing matters, the lab is important, but it would have to wait.&amp;nbsp; It progessed to much worse this week and vSphere client or Web Client not being able to stay logged for more than a couple of seconds.&amp;nbsp;&amp;nbsp;&amp;nbsp; I haven't had time to deal with this until now, so here we go.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You know you are in trouble when on the VCSA management page, vCenter Server &amp;gt; Summary &amp;gt; Storage &amp;gt; Coredumps = 100%!&amp;nbsp;&amp;nbsp; The core dumps or "coredumps" are stored on the VCSA in &lt;STRONG&gt;/storage/core&lt;/STRONG&gt; with files named core.vpxd-worker.xxxx &lt;EM&gt;where 'x' is a number&lt;/EM&gt;.&amp;nbsp; I emptied that via SSH with the &lt;STRONG&gt;rm&lt;/STRONG&gt; command, but of course it just started filling up again with the same files.&amp;nbsp;&amp;nbsp;&amp;nbsp; Time to break out the toolbox.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;After 20 minutes of research and an easy fix, I made a change that has let me login and perform operations in the vSphere Client.&lt;/STRONG&gt;&amp;nbsp; So far, so good, no more core dump files 2 hours later.&amp;nbsp; It may be best to perform a basic, surface-level health check (or use LucD's)&amp;nbsp; before rebuilding a VCSA from scratch.&amp;nbsp; That can be a lot of work and will have consequences for VDS, Clusters, policies, etc.&amp;nbsp; Did you document everything?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are the steps and actions I took to get the lab back online: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;From the VCSA management page, stop and started vCenter and Inventory services, but no effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;From the VCSA management page, reboot the appliance, but no effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Stopped vCenter Server and Inventory Services to keep them off during troubleshooting&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Logged into each host with vSphere Client first to check all the basics, DNS name, time, verify that IPV6 is disabled &lt;/SPAN&gt;&lt;EM style="font-size: 10pt;"&gt;(I had problems with that enabled before even though it wasn't in use),&lt;/EM&gt;&lt;SPAN style="font-size: 10pt;"&gt; etc&lt;/SPAN&gt;&lt;EM style="font-size: 10pt;"&gt;.&lt;/EM&gt;&lt;SPAN style="font-size: 10pt;"&gt;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Then (still in vSphere client) check the host logs Home &amp;gt; Administration &amp;gt; &lt;/SPAN&gt;&lt;STRONG style="font-size: 10pt;"&gt;System Logs&lt;/STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt; for odd patterns or excessive errors in any of the logs (there are several, click the drop-down).&amp;nbsp;&amp;nbsp;&amp;nbsp; The first 4 hosts I check all looked normal, &lt;SPAN style="color: #0000ff;"&gt;but one was having what looked like an excessive amount of errors related to snapshot delta disks from snapshots&lt;/SPAN&gt;.&amp;nbsp;&amp;nbsp; The problem rang a bell, there was a VM I noticed I had trouble with recently that has a bunch of snapshots and delta disks from some failed backups.&amp;nbsp;&amp;nbsp; I didn't have time to look into it a month or so when I first saw that (it is lab and we never have the time do we?). &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;The VM was already shut down, so I removed it from the host inventory, then SSH'd to the host and ran &lt;STRONG&gt;/sbin/services.sh restart&lt;/STRONG&gt; to restart the management agents --but you can also use the DCUI to accomplish same.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;Started &lt;/SPAN&gt;vCenter Server and Inventory Services and voila, I could log in and manage my lab again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Side notes: &lt;BR /&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;I got this message on all of the VMs that were running on the host.&amp;nbsp;&amp;nbsp; The VMs never went down, but HA was attempted:&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;vSphere HA virtual machine failover failed&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;I have to work on the snapshot problem which I think was caused during backups by the VMware Data Recovery Appliance, but I don't know the cause.&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV id="_mcePaste"&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-size: 10pt;"&gt;A number of different issues could be causing this behavior with your vCenter services, but if you can isolate it down to a particular host or even VM as was my case, you can save yourself a lot of trouble.&amp;nbsp; Always have a plan or you may need your resume.&amp;nbsp;&amp;nbsp; Good luck!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Cheers!&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: aSmoot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Apr 2013 18:24:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349421#M43308</guid>
      <dc:creator>aSmoot</dc:creator>
      <dc:date>2013-04-15T18:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349422#M43309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your message. I am currently out of the office and will return Apr 16, 2013. I will respond upon my return.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For support related issues please contact the IT Service Desk servicedesk@camhydro.com or x2700.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Heath&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Apr 2013 18:25:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349422#M43309</guid>
      <dc:creator>doubleH</dc:creator>
      <dc:date>2013-04-15T18:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349423#M43310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Hi there,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;I have exact same problem on the linux- based vCenter server appliance 5.5 installed with OVA on the ESXi host 5.5.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;I used:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="NameLabel" style="font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; font-weight: bold; color: #666666; background-color: #e6e6e6;"&gt;Name: &lt;/SPAN&gt;&lt;SPAN class="fileNameHolder" style="font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; color: #666666; background-color: #e6e6e6;"&gt;VMware-vCenter-Server-Appliance-5.5.0.20200-2183109_OVF10.ova &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="releaseDate label" style="font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; font-weight: bold; color: #666666; background-color: #e6e6e6;"&gt;Release Date&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; background-color: #e6e6e6;"&gt;: 2014-10-09&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="label build" style="font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; font-weight: bold; color: #666666; background-color: #e6e6e6;"&gt;Build Number&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, ​, Arial, ​sans-serif; font-size: 14px; background-color: #e6e6e6;"&gt;: 2183109&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;All services can start except the vCenter.&amp;nbsp; It always says :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;EM&gt;Starting vmware-vpxd: success&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;EM&gt;"Waiting for vpxd to initialized: .failed'.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;I have checked the time on ESXi host and the vCenter and they matched since both the ESXi host and vCenter sync to same ntp server.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;My DataBase is embedded and SSO is also embedded.&amp;nbsp; "Test Settings" is successful.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;in /var/log/messages:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:19+00:00 localhost vami-sfcbd: pam_succeed_if(vami-sfcb:auth): requirement "uid eq 0" was met by user "root"&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:23+00:00 localhost lsassd[3997]: 0x7f57668fa700:Failed to run provider specific request (request code = 12, provider = 'lsa-activedirectory-provider') -&amp;gt; error = 2692, symbol = NERR_SetupNotJoined, client pid = 1815&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:23+00:00 localhost lwsmd: Stopping service: eventlog&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:24+00:00 localhost lwsmd: Starting service: eventlog&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:24+00:00 localhost lsassd[3997]: 0x7f57668fa700:Failed to run provider specific request (request code = 12, provider = 'lsa-activedirectory-provider') -&amp;gt; error = 2692, symbol = NERR_SetupNotJoined, client pid = 1967&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:50+00:00 localhost lsassd[3997]: 0x7f57668fa700:Failed to run provider specific request (request code = 12, provider = 'lsa-activedirectory-provider') -&amp;gt; error = 2692, symbol = NERR_SetupNotJoined, client pid = 2305&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:53+00:00 localhost lsassd[3997]: 0x7f57668fa700:Failed to run provider specific request (request code = 12, provider = 'lsa-activedirectory-provider') -&amp;gt; error = 2692, symbol = NERR_SetupNotJoined, client pid = 2609&lt;/P&gt;&lt;P&gt;2014-10-31T21:16:53+00:00 localhost lwsmd: Stopping service: eventlog&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: [3080] Begin '/usr/sbin/vpxd', min-uptime = 30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file = ''&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 1) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 2) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:07+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 3) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 4) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 5) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:08+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:09+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 6) 134&lt;/P&gt;&lt;P&gt;2014-10-31T21:17:09+00:00 localhost watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached&lt;/P&gt;&lt;P&gt;2014-10-31T21:19:19+00:00 localhost syslog-ng[1289]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=1704', processed='center(received)=1169', processed='destination(messages)=469', processed='destination(mailinfo)=2', processed='destination(mailwarn)=4', processed='destination(authlog)=38', processed='destination(localmessages)=10', processed='destination(cron)=25', processed='destination(mailerr)=0', processed='destination(ldapmessages)=694', processed='destination(netmgm)=0', processed='destination(warn)=156', processed='destination(console)=150', processed='destination(mail)=6', processed='destination(null)=0', processed='destination(xconsole)=150', processed='destination(firewall)=0', processed='destination(acpid)=0', processed='source(src)=1169'&lt;/P&gt;&lt;P&gt;2014-10-31T21:20:01+00:00 localhost /usr/sbin/cron[3432]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] &amp;amp;&amp;amp; exec /usr/lib64/sa/sa1 -S ALL 1 1)&lt;/P&gt;&lt;P&gt;2014-10-31T21:20:01+00:00 localhost /usr/sbin/cron[3435]: (root) CMD ( test -x /usr/sbin/vpxd_periodic &amp;amp;&amp;amp; /usr/sbin/vpxd_periodic &amp;gt;/dev/null 2&amp;gt;&amp;amp;1)&lt;/P&gt;&lt;P&gt;2014-10-31T21:30:01+00:00 localhost /usr/sbin/cron[3733]: (root) CMD ( test -x /usr/sbin/vpxd_periodic &amp;amp;&amp;amp; /usr/sbin/vpxd_periodic &amp;gt;/dev/null 2&amp;gt;&amp;amp;1)&lt;/P&gt;&lt;P&gt;2014-10-31T21:30:01+00:00 localhost /usr/sbin/cron[3735]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] &amp;amp;&amp;amp; exec /usr/lib64/sa/sa1 -S ALL 1 1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;I followed instruction on &lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2012167&amp;amp;sliceId=2&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=413762600&amp;amp;stateId=0%200%20426598848" title="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2012167&amp;amp;sliceId=2&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=413762600&amp;amp;stateId=0%200%20426598848"&gt;VMware KB: vpxd process on the vCenter Server Appliance 5.x fails with the error: Signal 11 received&lt;/A&gt;&lt;/SPAN&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2012167&amp;amp;sliceId=2&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=413762600&amp;amp;stateId=0%200%20426598848" style="font-size: 12pt; line-height: 1.5em;" title="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;amp;docType=kc&amp;amp;externalId=2012167&amp;amp;sliceId=2&amp;amp;docTypeID=DT_KB_1_1&amp;amp;dialogID=413762600&amp;amp;stateId=0%200%20426598848"&gt; &lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;and modified /etc/vmware-vpx/vpx.cfg file as sugggested by adding the ThreadStackSizedKb line.&amp;nbsp; See below.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12px; color: #666666; font-family: 'Courier New';"&gt;&amp;lt;threadPool&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12px; color: #666666; font-family: 'Courier New';"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 10pt; color: #666666;"&gt;&lt;SPAN style="font-size: 12px !important;"&gt;&amp;lt;TaskMax&amp;gt;90&amp;lt;/TaskMax&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="font-family: inherit; font-size: inherit; font-style: inherit; font-weight: inherit; color: #ff0000;"&gt;&amp;lt;ThreadStackSizeKb&amp;gt;512&amp;lt;/ThreadStackSizeKb&amp;gt;&lt;BR /&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;threadNamePrefix&amp;gt;vpxd&amp;lt;/threadNamePrefix&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 12px; color: #666666; font-family: 'Courier New';"&gt;&amp;lt;/threadPool&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, it doesn't work.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Anyone knows about this problem please help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 21:52:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349423#M43310</guid>
      <dc:creator>Lynn123</dc:creator>
      <dc:date>2014-10-31T21:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349424#M43311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had an issue with the vpxd failing to initialize (vpxd service started succesfully), and found that there was a message in the var/log/vmware/vpx/vpxd.log that it was unable to open the file var/log/vmware/journal/1414758110.0.lck - no such file exists. I looked in the location and a directory of that name had been created. Once I removed this directory and restarted the vpxd service I got back my vCenter server and was able to log in using both the vsphere client and web client. I have not seen anyone mention this error in their logs posted - but this resolved the service failing to initialise issue on my setup. I am on ESXi 5.5 with a Single vCenter and 3 hosts&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Nov 2014 15:58:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349424#M43311</guid>
      <dc:creator>bhanekom</dc:creator>
      <dc:date>2014-11-20T15:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349425#M43312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same issue and it turned out the /storage/db drive was out of space.&amp;nbsp; I followed WMware's article: &lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2056764" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2056764"&gt;VMware KB: Increasing the disk space in vCenter Server Appliance 5.x&lt;/A&gt; and I'm good.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Sep 2015 22:46:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349425#M43312</guid>
      <dc:creator>brokentwig</dc:creator>
      <dc:date>2015-09-22T22:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349426#M43313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you must increase space of hard drive from the vsphere &lt;SPAN style="font-size: 13.3333px;"&gt; console&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Снимоккуцкуцк.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/63968i5DA9B4ECF6B99BE4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Снимоккуцкуцк.PNG" alt="Снимоккуцкуцк.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Feb 2016 07:00:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349426#M43313</guid>
      <dc:creator>Shneider82</dc:creator>
      <dc:date>2016-02-02T07:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349427#M43314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My datastore ran out of space, the vcenter froze, I cleared space on the datastore, resumed the vcsa but it was unresponsive. &lt;/P&gt;&lt;P&gt;Restarted vcenter and got the "Waiting for vpxd to initialize failed".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What solved it was running these instructions I found here:&lt;/P&gt;&lt;P&gt;From: &lt;A href="http://www.colabug.com/thread-1093735-1-1.html" title="http://www.colabug.com/thread-1093735-1-1.html"&gt;http://www.colabug.com/thread-1093735-1-1.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;To get over this, log on to the VCVA using SSH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Run the command “ /usr/sbin/vpxd_odbcconfig ” &lt;/P&gt;&lt;P&gt; You see output similar to:&lt;/P&gt;&lt;P&gt; VMware vCenter Server Appliance ODBC Configuration&lt;/P&gt;&lt;P&gt; Choose a database to use with VMware vCenter Server&lt;/P&gt;&lt;P&gt; 1) oracle&lt;/P&gt;&lt;P&gt; 2) embedded&lt;/P&gt;&lt;P&gt; Enter 2 (should the DB be the embedded PostgresSQL&lt;/P&gt;&lt;P&gt; You see output similar to:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Configuring ODBC for embedded &lt;/P&gt;&lt;P&gt; Operation was successful. &lt;/P&gt;&lt;P&gt; Database already populated with version VirtualCenter Database 5.5 &lt;/P&gt;&lt;P&gt; Reinitialize database? (WARNING: WILL DELETE ALL RECORDS) [y(es)|N(O)]: OK, preserving the database. (select No to preserve the database) &lt;/P&gt;&lt;P&gt; Restart vCenter Server now to activate the database changes [y/N]:y &lt;/P&gt;&lt;P&gt; Successfully restarted vCenter Server &lt;/P&gt;&lt;P&gt; This should start the vpxd service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's my output:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Starting vmware-vpxd: success&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;SPAN style="color: #e23d39; text-decoration: underline;"&gt;Waiting for vpxd to initialize: ............................................................failed&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;vcsa:~ # &lt;STRONG style="color: #2873ee;"&gt;/usr/sbin/vpxd_odbcconfig&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;WARNING - Use of this command is not supported unless you are doing this&lt;/P&gt;&lt;P&gt;with the consultation of VMware Technical Support or a VMware published&lt;/P&gt;&lt;P&gt;technical article.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VMware vCenter Server Appliance ODBC Configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose a database to use with VMware vCenter Server&lt;/P&gt;&lt;P&gt;1) oracle&lt;/P&gt;&lt;P&gt;2) embedded&lt;/P&gt;&lt;P&gt;#? &lt;STRONG style="color: #2873ee;"&gt;2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring ODBC for embedded&lt;/P&gt;&lt;P&gt;Error: VPXD must be stopped to perform this operation.&lt;/P&gt;&lt;P&gt;Database&amp;nbsp; configuration has failed.&lt;/P&gt;&lt;P&gt;Would you like to try again or modify the settings manually?&lt;/P&gt;&lt;P&gt; [A]gain/[m]anually : &lt;SPAN style="color: #2873ee;"&gt;&lt;STRONG&gt;m&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;vcsa:~ # &lt;STRONG style="color: #2873ee;"&gt;service vmware-vpxd stop&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Stopping tomcat: success&lt;/P&gt;&lt;P&gt;Stopping vmware-vpxd: success&lt;/P&gt;&lt;P&gt;Shutting down ldap-server..done&lt;/P&gt;&lt;P&gt;vcsa:~ # &lt;STRONG style="color: #2873ee;"&gt;/usr/sbin/vpxd_odbcconfig&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;WARNING - Use of this command is not supported unless you are doing this&lt;/P&gt;&lt;P&gt;with the consultation of VMware Technical Support or a VMware published&lt;/P&gt;&lt;P&gt;technical article.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VMware vCenter Server Appliance ODBC Configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose a database to use with VMware vCenter Server&lt;/P&gt;&lt;P&gt;1) oracle&lt;/P&gt;&lt;P&gt;2) embedded&lt;/P&gt;&lt;P&gt;#? &lt;SPAN style="color: #2873ee;"&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuring ODBC for embedded&lt;/P&gt;&lt;P&gt;Operation was successful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Database already populated with version VirtualCenter Database 5.5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Reinitialize database? (WARNING: WILL DELETE ALL RECORDS) [y(es)|N(O)]: &lt;STRONG style="color: #2873ee;"&gt;n&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; OK, preserving the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Restart vCenter Server now to activate the database changes [y/N]:&lt;STRONG style="color: #2873ee;"&gt;y&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Successfully restarted vCenter Server&lt;/P&gt;&lt;P&gt;vcsa:~ #&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Success!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 May 2017 20:44:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349427#M43314</guid>
      <dc:creator>emorillo</dc:creator>
      <dc:date>2017-05-02T20:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349428#M43315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have setup VMware appliance in our setup but after changing some configuration in inventory.cfg , Vmware-vpxd services will not starting even after reverting the changes. Attaching logs below. kindly help us ASAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Waiting for the embedded database to start up: success&lt;/P&gt;&lt;P&gt;Verifying EULA acceptance: success&lt;/P&gt;&lt;P&gt;Executing pre-startup scripts...&lt;/P&gt;&lt;P&gt;Updating the vCenter endpoint in the Lookup Service.&lt;/P&gt;&lt;P&gt;Intializing registration provider...&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Getting SSL certificates for &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://192.168.20.100:7444/lookupservice/sdk" rel="nofollow"&gt;https://192.168.20.100:7444/lookupservice/sdk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Service with name 'vpxd-localhost.localdom-543843fd-d8da-4c7f-9bd7-8acd95edeb60' and ID 'local:9c27a9ee-0ca0-42e7-8767-7704f847d240' was updated.&lt;/P&gt;&lt;P&gt;Return code is: Success&lt;/P&gt;&lt;P&gt;Shutting down ldap-server..done&lt;/P&gt;&lt;P&gt;Starting ldap-server..done&lt;/P&gt;&lt;P&gt;Starting vmware-vpxd: success&lt;/P&gt;&lt;P&gt;Waiting for vpxd to initialize: .failed&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;-- this is going to be fail every time.&lt;/P&gt;&lt;P&gt;localhost:~ #&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On System log , We will get :-&lt;/P&gt;&lt;P&gt;localhost:~ # cat /var/log/messages&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:18+00:00 localhost watchdog-vpxd: PID file /var/run/vmware/watchdog-vpxd.PID does not exist&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:18+00:00 localhost watchdog-vpxd: Unable to terminate watchdog: No running watchdog process for vpxd&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:19+00:00 localhost watchdog-vpxd: PID file /var/run/vmware/watchdog-vpxd.PID does not exist&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:19+00:00 localhost watchdog-vpxd: Unable to terminate watchdog: No running watchdog process for vpxd&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:27+00:00 localhost watchdog-vpxd: [12418] Begin '/usr/sbin/vpxd', min-uptime = 30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file = ''&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:27+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:27+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 1) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:27+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 2) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 3) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 4) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:28+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:29+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 5) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:29+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:29+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 6) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:13:29+00:00 localhost watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached&lt;/P&gt;&lt;P&gt;2017-06-05T10:14:13+00:00 localhost watchdog-vpxd: PID file /var/run/vmware/watchdog-vpxd.PID does not exist&lt;/P&gt;&lt;P&gt;2017-06-05T10:14:13+00:00 localhost watchdog-vpxd: Unable to terminate watchdog: No running watchdog process for vpxd&lt;/P&gt;&lt;P&gt;2017-06-05T10:14:14+00:00 localhost watchdog-vpxd: PID file /var/run/vmware/watchdog-vpxd.PID does not exist&lt;/P&gt;&lt;P&gt;2017-06-05T10:14:14+00:00 localhost watchdog-vpxd: Unable to terminate watchdog: No running watchdog process for vpxd&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:56+00:00 localhost watchdog-vpxd: [4936] Begin '/usr/sbin/vpxd', min-uptime = 30, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file = ''&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:56+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:56+00:00 localhost kernel: [&amp;nbsp;&amp;nbsp; 82.191937] warning: process `vpxd' used the deprecated sysctl system call with 1.1.&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:56+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 1) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:56+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 2) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 3) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 4) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:57+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:58+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 1 seconds (quick failure 5) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:58+00:00 localhost watchdog-vpxd: Executing '/usr/sbin/vpxd'&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:58+00:00 localhost watchdog-vpxd: '/usr/sbin/vpxd' exited after 0 seconds (quick failure 6) 1&lt;/P&gt;&lt;P&gt;2017-06-05T10:15:58+00:00 localhost watchdog-vpxd: End '/usr/sbin/vpxd', failure limit reached&lt;/P&gt;&lt;P&gt;2017-06-05T10:20:01+00:00 localhost /usr/sbin/cron[5640]: (root) CMD ( test -x /usr/sbin/vpxd_periodic &amp;amp;&amp;amp; /usr/sbin/vpxd_periodic &amp;gt;/dev/null 2&amp;gt;&amp;amp;1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On vpxd.log, I also get some error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;localhost:/var/log/vmware/vpx # tailf -n 100 vpxd-171.log&lt;/P&gt;&lt;P&gt;Section for VMware VirtualCenter, pid=27456, version=5.5.0, build=2001466, option=Release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------ In-memory logs start --------&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2017-06-06T04:14:20.657Z [7F9131494740 verbose 'vpxdvpxdSignal'] Signal handler for signal 1 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2017-06-06T04:14:20.657Z [7F9131494740 verbose 'vpxdvpxdSignal'] Signal handler for signal 2 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2017-06-06T04:14:20.657Z [7F9131494740 verbose 'vpxdvpxdSignal'] Signal handler for signal 15 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2017-06-06T04:14:20.657Z [7F9131494740 verbose 'vpxdvpxdSignal'] Signal handler for signal 10 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2017-06-06T04:14:20.657Z [7F9131494740 info 'Hooks'] Hooks Initialized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------ In-memory logs end&amp;nbsp;&amp;nbsp; --------&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.660Z [7F9131494740 info 'Default'] Logging uses fast path: true&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.660Z [7F9131494740 info 'Default'] Handling bora/lib logs with VmaCore facilities&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.660Z [7F9131494740 info 'Default'] Initialized channel manager&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9131494740 info 'Default'] Current working directory: /storage/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9131494740 info 'ThreadPool'] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 200, 2, 90, 2147483647&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9131494740 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9131494740 info 'Default'] Log path: /var/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9131494740 info 'Default'] Initializing SSL&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F91278A4700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F91279A6700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9127823700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.663Z [7F9127925700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.664Z [7F9131494740 info 'Default'] Vmacore::InitSSL: handshakeTimeoutUs = 120000000&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.665Z [7F91277A2700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.665Z [7F9131494740 info 'vpxdvpxdDaemon'] Changed working directory to /var/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.666Z [7F9131494740 error 'vpxdvpxdDaemon'] Unhandled exception:&lt;/P&gt;&lt;P&gt;--&amp;gt; not well-formed (invalid token)&lt;/P&gt;&lt;P&gt;2017-06-06T04:14:20.667Z [7F9131494740 error 'vpxdvpxdDaemon'] Backtrace:&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[00] rip 00007f912b3f9014 Vmacore::System::Stacktrace::CaptureWork(unsigned int)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[01] rip 00007f912b2e3132 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref&amp;lt;Vmacore::System::Backtrace&amp;gt;&amp;amp;)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[02] rip 00007f912b2448a5 Vmacore::Throwable::Throwable(std::string const&amp;amp;)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[03] rip 00007f912b28b566 /usr/lib/vmware-vpx/libvmacore.so(+0x285566) [0x7f912b28b566]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[04] rip 00007f912b23e85d /usr/lib/vmware-vpx/libvmacore.so(+0x23885d) [0x7f912b23e85d]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[05] rip 00007f9132abfd07 /usr/lib/vmware-vpx/vpxd(+0x14aad07) [0x7f9132abfd07]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[06] rip 00007f9132a3f0c5 /usr/lib/vmware-vpx/vpxd(+0x142a0c5) [0x7f9132a3f0c5]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[07] rip 00007f91324c3ca3 /usr/lib/vmware-vpx/vpxd(+0xeaeca3) [0x7f91324c3ca3]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[08] rip 00007f91324a6c2e /usr/lib/vmware-vpx/vpxd(+0xe91c2e) [0x7f91324a6c2e]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[09] rip 00007f9129369c16 /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f9129369c16]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[10] rip 00007f91324a5e89 /usr/lib/vmware-vpx/vpxd(+0xe90e89) [0x7f91324a5e89]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have gone through the above solutions for storage space full but i checked on our setup its not there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;localhost:/var/log/vmware/vpx # df -h&lt;/P&gt;&lt;P&gt;Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Size&amp;nbsp; Used Avail Use% Mounted on&lt;/P&gt;&lt;P&gt;/dev/sda3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 9.8G&amp;nbsp; 3.7G&amp;nbsp; 5.6G&amp;nbsp; 40% /&lt;/P&gt;&lt;P&gt;udev&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4.0G&amp;nbsp; 104K&amp;nbsp; 4.0G&amp;nbsp;&amp;nbsp; 1% /dev&lt;/P&gt;&lt;P&gt;tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4.0G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 4.0G&amp;nbsp;&amp;nbsp; 0% /dev/shm&lt;/P&gt;&lt;P&gt;/dev/sda1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128M&amp;nbsp;&amp;nbsp; 21M&amp;nbsp; 101M&amp;nbsp; 18% /boot&lt;/P&gt;&lt;P&gt;/dev/sdb1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20G&amp;nbsp; 173M&amp;nbsp;&amp;nbsp; 19G&amp;nbsp;&amp;nbsp; 1% /storage/core&lt;/P&gt;&lt;P&gt;/dev/sdb2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20G&amp;nbsp; 305M&amp;nbsp;&amp;nbsp; 19G&amp;nbsp;&amp;nbsp; 2% /storage/log&lt;/P&gt;&lt;P&gt;/dev/sdb3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 60G&amp;nbsp; 1.7G&amp;nbsp;&amp;nbsp; 55G&amp;nbsp;&amp;nbsp; 4% /storage/db&lt;/P&gt;&lt;P&gt;localhost:/var/log/vmware/vpx # df -ih&lt;/P&gt;&lt;P&gt;Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inodes IUsed IFree IUse% Mounted on&lt;/P&gt;&lt;P&gt;/dev/sda3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 632K&amp;nbsp;&amp;nbsp; 60K&amp;nbsp; 573K&amp;nbsp;&amp;nbsp; 10% /&lt;/P&gt;&lt;P&gt;udev&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - /dev&lt;/P&gt;&lt;P&gt;tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1001K&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2 1001K&amp;nbsp;&amp;nbsp;&amp;nbsp; 1% /dev/shm&lt;/P&gt;&lt;P&gt;/dev/sda1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 34K&amp;nbsp;&amp;nbsp;&amp;nbsp; 40&amp;nbsp;&amp;nbsp; 34K&amp;nbsp;&amp;nbsp;&amp;nbsp; 1% /boot&lt;/P&gt;&lt;P&gt;/dev/sdb1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.3M&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&amp;nbsp; 1.3M&amp;nbsp;&amp;nbsp;&amp;nbsp; 1% /storage/core&lt;/P&gt;&lt;P&gt;/dev/sdb2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.3M&amp;nbsp;&amp;nbsp; 293&amp;nbsp; 1.3M&amp;nbsp;&amp;nbsp;&amp;nbsp; 1% /storage/log&lt;/P&gt;&lt;P&gt;/dev/sdb3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3.8M&amp;nbsp; 3.7K&amp;nbsp; 3.8M&amp;nbsp;&amp;nbsp;&amp;nbsp; 1% /storage/db&lt;/P&gt;&lt;P&gt;localhost:/var/log/vmware/vpx #&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jun 2017 04:40:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349428#M43315</guid>
      <dc:creator>rinku02bansal</dc:creator>
      <dc:date>2017-06-06T04:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349429#M43316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This absolutely worked for me. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case, I do not believe I had ran out of space first (&lt;SPAN style="color: #2873ee;"&gt;df -h&lt;/SPAN&gt; was reporting fine).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Feb 2018 16:19:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349429#M43316</guid>
      <dc:creator>citylights</dc:creator>
      <dc:date>2018-02-24T16:19:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349430#M43317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello I have same problem&lt;/P&gt;&lt;P&gt;after restarting I cannot connect to vcenter. This is a my log file. Please Help solve this problem&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Section for VMware VirtualCenter, pid=4819, version=5.5.0, build=2001466, option=Release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------ In-memory logs start --------&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2018-12-07T08:20:43.272Z [7FA96E132740 verbose 'vpxdvpxdSignal'] Signal handler for signal 1 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2018-12-07T08:20:43.272Z [7FA96E132740 verbose 'vpxdvpxdSignal'] Signal handler for signal 2 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2018-12-07T08:20:43.272Z [7FA96E132740 verbose 'vpxdvpxdSignal'] Signal handler for signal 15 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2018-12-07T08:20:43.272Z [7FA96E132740 verbose 'vpxdvpxdSignal'] Signal handler for signal 10 is installed&lt;/P&gt;&lt;P&gt;mem&amp;gt; 2018-12-07T08:20:43.272Z [7FA96E132740 info 'Hooks'] Hooks Initialized&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------ In-memory logs end&amp;nbsp;&amp;nbsp; --------&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.281Z [7FA96E132740 info 'Default'] Logging uses fast path: true&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.281Z [7FA96E132740 info 'Default'] Handling bora/lib logs with VmaCore facilities&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.281Z [7FA96E132740 info 'Default'] Initialized channel manager&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA96E132740 info 'Default'] Current working directory: /storage/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA964685700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA964502700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA96E132740 info 'ThreadPool'] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 200, 2, 90, 2147483647&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA96E132740 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA964604700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA964583700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA96E132740 info 'Default'] Log path: /var/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.288Z [7FA96E132740 info 'Default'] Initializing SSL&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.291Z [7FA96E132740 info 'Default'] Vmacore::InitSSL: handshakeTimeoutUs = 120000000&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.292Z [7FA964481700 info 'ThreadPool'] Thread enlisted&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.293Z [7FA96E132740 info 'vpxdvpxdDaemon'] Changed working directory to /var/log/vmware/vpx&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.306Z [7FA96E132740 info 'Default'] Starting VMware VirtualCenter 5.5.0 build-2001466&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.306Z [7FA96E132740 info 'Default'] Log directory: /var/log/vmware/vpx.&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'vpxdvpxdMain'] Account name: root&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 640 max LROs&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 12 reserved internal LROs&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 12 reserved blocker LROs&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 12 reserved short LROs&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 8 reserved long LROs&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 600-second completed task lifetime&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 60-second minimum completed task lifetime&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 200 maximum completed tasks&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.307Z [7FA96E132740 info 'commonvpxLro'] [VpxLRO] 600-second unregistered task lifetime&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.308Z [7FA96E132740 info 'utilvpxdVdb'] Registry Item DB 5 value is ''&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.308Z [7FA96E132740 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: VMware VirtualCenter with username vc&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.477Z [7FA96E132740 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.494Z [7FA96E132740 info 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::GetSchemaFilename]: sqlDir: /usr/lib/vmware-vpx/sql/&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.494Z [7FA96E132740 info 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::CheckSchema]: schema file: /usr/lib/vmware-vpx/sql/VCDB_PostgreSQL.sql&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.508Z [7FA96E132740 info 'linuxvpxLdap_linux'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.508Z [7FA96E132740 info 'linuxvpxLdap_linux'] [LdapBackup] Checking service ldap for running &lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.533Z [7FA96E132740 info 'Default'] Looking for vpx result filter at /usr/lib/vmware-vpx/vpxResultFilter.xml&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.538Z [7FA964604700 info 'vpxdvpxdMain' opID=SWI-6058ed8] Pre-loading symbols...&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.540Z [7FA964604700 info 'vpxdvpxdMain' opID=SWI-6058ed8] Done pre-loading symbols.&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.541Z [7FA96E132740 info 'MoLock'] LRO tracing: enabled: false&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.541Z [7FA96E132740 info 'MoLock'] LRO tracing: LRO name: &lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.556Z [7FA96E132740 info 'Default'] Looking for vpx result filter at /usr/lib/vmware-vpx/vpxResultFilter.xml&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.561Z [7FA96E132740 info 'QueryServiceProvider'] Initializing QueryServiceProviderHelperImpl&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.605Z [7FA96E132740 info 'QueryServiceProvider'] Starting with generation number: 7085462&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.605Z [7FA96E132740 info 'vpxservicesMoServiceDirectory'] [ServiceDirectory] Local instance UUID: 0FCF384F-1EEA-4A00-9424-673FC0F7F363&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.608Z [7FA96E132740 error 'linuxvpxLdap_linux'] [LDAP Client] Failed to modify LDAP entry cn=VIMAPI,cn=0FCF384F-1EEA-4A00-9424-673FC0F7F363,ou=Instances,dc=virtualcenter,dc=vmware,dc=int: 0x1 (Operations error)&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.608Z [7FA96E132740 error 'linuxvpxLdap_linux'] [LDAP Client] LdapApi::modify_s: key (vmw-vc-SSLThumbprint)&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.608Z [7FA96E132740 error 'vpxservicesMoServiceDirectory'] [ServiceDirectory::UpdateServiceInfo] Error while modifying service-endpoint SSL thumbprint cn=VIMAPI,cn=0FCF384F-1EEA-4A00-9424-673FC0F7F363,ou=Instances,dc=virtualcenter,dc=vmware,dc=int&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.608Z [7FA96E132740 error 'vpxdvpxdMain'] [Init] Init failed: Ldap error&lt;/P&gt;&lt;P&gt;--&amp;gt; Backtrace:&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[00] rip 00007fa968097014 Vmacore::System::Stacktrace::CaptureWork(unsigned int)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[01] rip 00007fa967f81132 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref&amp;lt;Vmacore::System::Backtrace&amp;gt;&amp;amp;)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[02] rip 00007fa967ee28a5 Vmacore::Throwable::Throwable(std::string const&amp;amp;)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[03] rip 00007fa96f16331f Vmomi::Fault::SystemError::Exception::Exception(std::string const&amp;amp;)&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[04] rip 00007fa97060c60b /usr/lib/vmware-vpx/vpxd(+0x235960b) [0x7fa97060c60b]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[05] rip 00007fa97060f0fd /usr/lib/vmware-vpx/vpxd(+0x235c0fd) [0x7fa97060f0fd]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[06] rip 00007fa97060f645 /usr/lib/vmware-vpx/vpxd(+0x235c645) [0x7fa97060f645]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[07] rip 00007fa96f14daaf /usr/lib/vmware-vpx/vpxd(+0xe9aaaf) [0x7fa96f14daaf]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[08] rip 00007fa96f161d43 /usr/lib/vmware-vpx/vpxd(+0xeaed43) [0x7fa96f161d43]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[09] rip 00007fa96f144c2e /usr/lib/vmware-vpx/vpxd(+0xe91c2e) [0x7fa96f144c2e]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[10] rip 00007fa966007c16 /lib64/libc.so.6(__libc_start_main+0xe6) [0x7fa966007c16]&lt;/P&gt;&lt;P&gt;--&amp;gt; backtrace[11] rip 00007fa96f143e89 /usr/lib/vmware-vpx/vpxd(+0xe90e89) [0x7fa96f143e89]&lt;/P&gt;&lt;P&gt;--&amp;gt; &lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.612Z [7FA96E132740 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...&lt;/P&gt;&lt;P&gt;2018-12-07T08:20:43.612Z [7FA96E132740 info 'vpxdvpxdSupportManager'] Wrote uptime information&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2018 08:33:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-Start-vCenter-Server-Appliance-quot-Waiting-for-vpxd-to/m-p/1349430#M43317</guid>
      <dc:creator>Smerchla</dc:creator>
      <dc:date>2018-12-07T08:33:26Z</dc:date>
    </item>
  </channel>
</rss>

