Solved

Vcenter server appliance 6.0 (503 service unabvailable)

Posted on 2016-10-25
6
110 Views
Last Modified: 2016-10-29
Hi Guys,

I have deployed a vcenter server appliance vm, which gave me an IP address to logon to the webclient.
Ip:192.xxx.xxx.xxx
When I go to the IP adress provided, the page loads and then shows the following error:
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7f894c05cda0] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Can anyone be so kind and try to help on how to resolve?
I have an ESXIHost6.0 and my Vcenter server appliance vm 6.0 compatible, is under the the ESXI host IP.
Should you need additional details, do not hesitate to revert back.

thank you
0
Comment
Question by:Maniman man
  • 3
  • 3
6 Comments
 
LVL 118
ID: 41859315
How long have you left it to initialise, if often takes 15-20 minutes to get ready!

You should also use FQDN, and DNS names, if after waiting an hour, it's still non-responsive, I would re-install.
1
 

Author Comment

by:Maniman man
ID: 41861828
So i have tried to reinstall, took a long time, and now on y VCSA screen in Vmwareworkstation it says:
Failed to start services, Firstboot error. And I cannot access the webclient as well.
Any idea what could be the issue?

Thanks
0
 
LVL 118
ID: 41861886
did you setup the appliance with a valid FQDN and DNS hostname which could be resolved in DNS.

if not started again, and make sure you have a FQDN registered in DNS
1
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 

Author Comment

by:Maniman man
ID: 41861908
Yes I have on the vcsa screen the folowing:
https://fdqn.vsphere.local:443/appliance/support-bundle
https://192.xxx.xxx.xxx (Static)
Failed to start services. First boot error.

The static Vcsa IP is pointing to the ESXIhost Default gateway, where the DNS there is 192.168.1.1
0
 
LVL 118

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE) earned 500 total points
ID: 41861933
can you resolve this FQDN ?

have you tested this on another computer on your network ?
0
 

Author Closing Comment

by:Maniman man
ID: 41865452
Thanks. I have reinstall again. Gave a FQDN instead of an IPadress in the FQDN field during the install process.
Thanks again and sorry for the late reply.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is an issue that we can get adding / removing permissions in the vCSA 6.0. We can also have issues searching for users / groups in the AD (using your identify sources). This is how one of the ways to handle this issues and fix it.
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now