Failed to start LSB: Vmware PSC CLient

[Chekan]

I have installed latest ESXi 6.5u1 and deployed vcenter appliance using fqdn. Its starts okey and i can use it. But if i power it off, reboot host, and try to power it back on it boots directly to shell and services dont start. I maanged to catch a screenshot during boot. What is the problem?

Also other question, i have enabled EVC with ivy bridge on host. I am trying to add host with 2x 2620v4 CPUs and it says that CPU lacks some stuff (like AES, PCLMDQ etc)... All the features are enabled in bios ofcourse. Please help me with these 2 issues.

Сообщение отредактировано: Ivan Karmyshin

[rsk007]

Have you tried to reboot the PSC?

[Chekan]

I reinstalled using ip address instead of fqdn - same issue.

What do you mean reboot? How?

[Chekan]

I've just installed vCenter on completely other server. Same issue. Also when i try to enter web client it show a famous error:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00005614c65b3880] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Also i forgot to mention that hypervisor and vcenter are not in the same network as DNS server (but ofcourse all traffic is allowed so DNS resolves ok)

[daphnissov]

Do you have the following in place:

1. DNS (forward and reverse)
2. NTP (synced with ESXi host, vCSA during installer, and workstation where you're launching the installer)
3. FQDN used during installer

If you do, please post screenshots of the entire installation phase so we can see the values you're using.

[Chekan]

I reinstalled vcenter like 8 times during past 2 days.. Answer to all of your questions is yes (before i didnt meet these requirements i couldnt even install vcenter). Ive searched tons of info and cannot find anything useful. I am searching vpxd logs but i dont know what to look for...

[daphnissov]

Let's start at the top. If you're restarting the PSC and getting this failure, something is probably wrong in the deployment. Would you mind going through the process again but screenshotting every phase?

Also, all these ESXi hosts you have, are you making sure to have forward and reverse DNS records for each? I see in your screenshot that you're referencing one by its IP address rather than its FQDN.

[Chekan]

Ok, i did super clean install. Same problem.

[daphnissov]

Third screenshot: Don't use "vCenter Server" as the VM name. Use something else without a space.

Fifth screenshot: Use an external NTP server, don't synchronize with ESXi. If you do, ensure NTP is started on ESXi and it's pointed at a valid, internal NTP sever.

Sixth screenshot: Don't use opera.loc as your SSO domain. The SSO domain should either be left at the default of vsphere.local or something else which does not conflict with any sort of external identity source.

Also, in these screenshots you're deploying an embedded PSC model. What size are you choosing? If you using "Tiny", do not change the resource allocation from the defaults.

[Chekan]

Did as you said and couldnt even install. -> Firstboot error. Really strange issue :smileysad:((

[daphnissov]

Post another round of screenshots showing your new values. Also, are you by chance lowering the resources on the vCSA after it gets deployed?

[daphnissov]

And what is the exact build you're trying to install?

[Chekan]

I am not lowering resources ofcourse. I think NTP has something to do with that, atleast i repeated your instructions, just made NTP sync with host and it installed successfuly. But after reboot again:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x0000555aef6694d0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Host:      VMware-VMvisor-Installer-6.5.0.update01-5969303.x86_64

VC:        VMware-VCSA-all-6.5.0-7515524

[daphnissov]

So you're using the latest vCSA, which is good because it fixes an issue with the root password expiring.

NTP is very important to a successful installation. If you're selecting an external NTP source (which is inside your LAN) and it's failing, then something is wrong with NTP. It's critical that the ESXi destination host, vCSA (through installer wizard), and the workstation from which you're running this wizard all have their times closely in sync using the same source. So if you can take a new round of screenshots it would be helpful to see where you stand.

[Chekan]

Hosts successfulyl sync with NTP server (on mikrotik router). All times align to second (on host, on vcsa, on deployment machine)... TO be honest, by now  i think i've tried all the installations options.. Maybe i should install using ip address?? I have vcenter 6.0 which is working on ip address.

[daphnissov]

No, you should never install vCenter using the IP address. There is something going on in your case and I think it has to do with your installation process.

[Chekan]

By the way, thanks a lot for helping!

You know what is strange... After i install vcsa, i go to 5480 management page and check NTP - its perfect. Then, i reboot and get that error. I just tried to acccess 5480 port  page and noticed that NTP is completely wrong there! I changed setting in appliance management and rebooted vcenter again - no success.

You know what is strange... I have another installation of vcenter 6.5 (same version) in another firm. Network topology there is completely same, and vcsa reboots w/o issues with NTP pointing to Mikrotik router. The strangest part is when i log there on Appliance Management page, Last Health check reports correct time, but when i press on a "Time" page, its shows wrong default Timezone (-3 hours from what i am in). But still Everything works there.

[daphnissov]

The only thing I can think is that device isn't providing NTP services correctly. I've never seen that behavior anywhere as you have noted. Can you try another NTP source, even if it's external to your network? Use the IP if you can, not the FQDN.

[Chekan]

Jesus christ! I did it. Thank you man! Its really stupid to be honest, but using external ip address of NTP server worked.

To be honest i dont get it why vcenter is so demanding...

[daphnissov]

This is proof that the internal NTP server you thought was functioning correctly actually is not. vCenter, like so many other enterprise applications, depends on correct time keeping within the datacenter to function properly. This isn't a case of vCenter being any more demanding than other appliances--time keeping is extremely important, and when you don't keep good time or your time source is tainted, bad things begin to happen.