VMware Cloud Community
oliver_gao
Contributor
Contributor
‎07-05-2017 08:38 AM

VCSA 6.5 503 service unavailable

Hi all,

i met an issue which was about the "503 service unavailable". i looked up some other discussions in the vmware bbs and tried some guys' solutions, but still doesn't work with me.

actually, the vcsa ran normally the first time when i finished the new installation, but after i input some command lines to let the vcsa join domain and reboot. the vcsa web client was unaccessible.

bellowing is my error messages:

pastedImage_0.png

i also tried to lookup the postgre db log of my VCSA, it showed as bellow:

2017-07-05 21:58:02.395 UTC 595d60ae.51de 0   LOG:  Updating instance status...

2017-07-05 21:58:02.395 UTC 595d60ae.51de 0   LOG:  Memory check: flag = rss, mem_used = 5636 kB, mem_avail = 715776 kB

2017-07-05 21:58:02.395 UTC 595d60ae.51de 0   LOG:  Writing instance status...

2017-07-05 21:58:02.395 UTC 595d60ae.51de 0   LOG:  Wrote instance status successfully.

2017-07-05 21:58:02.395 UTC 595d60ae.51de 0   LOG:  Updated instance status successfully.

2017-07-05 21:59:02.443 UTC 595d60ae.51de 0   LOG:  Updating instance status...

2017-07-05 21:59:02.443 UTC 595d60ae.51de 0   LOG:  Memory check: flag = rss, mem_used = 18996 kB, mem_avail = 715776 kB

2017-07-05 21:59:02.443 UTC 595d60ae.51de 0   LOG:  Writing instance status...

2017-07-05 21:59:02.443 UTC 595d60ae.51de 0   LOG:  Wrote instance status successfully.

2017-07-05 21:59:02.443 UTC 595d60ae.51de 0   LOG:  Updated instance status successfully.

2017-07-05 21:59:14.287 UTC 595d60f7.59a1 0 VCDB vc WARNING:  there is no transaction in progress

2017-07-05 22:00:02.503 UTC 595d60ae.51de 0   LOG:  Updating instance status...

2017-07-05 22:00:02.503 UTC 595d60ae.51de 0   LOG:  Memory check: flag = rss, mem_used = 24824 kB, mem_avail = 715776 kB

2017-07-05 22:00:02.503 UTC 595d60ae.51de 0   LOG:  Writing instance status...

2017-07-05 22:00:02.503 UTC 595d60ae.51de 0   LOG:  Wrote instance status successfully.

2017-07-05 22:00:02.503 UTC 595d60ae.51de 0   LOG:  Updated instance status successfully.

2017-07-05 22:00:07.540 UTC 595d6167.6134 0 VCDB vc ERROR:  relation "cl_config" does not exist at character 16

2017-07-05 22:00:07.540 UTC 595d6167.6134 0 VCDB vc STATEMENT:   select * from cl_config

2017-07-05 22:00:07.566 UTC 595d6167.6134 0 VCDB vc ERROR:  relation "cl_dbversion" does not exist at character 16

2017-07-05 22:00:07.566 UTC 595d6167.6134 0 VCDB vc STATEMENT:   select * from cl_dbversion

2017-07-05 22:01:02.550 UTC 595d60ae.51de 0   LOG:  Updating instance status...

2017-07-05 22:01:02.551 UTC 595d60ae.51de 0   LOG:  Memory check: flag = rss, mem_used = 60472 kB, mem_avail = 715776 kB

2017-07-05 22:01:02.551 UTC 595d60ae.51de 0   LOG:  Writing instance status...

2017-07-05 22:01:02.551 UTC 595d60ae.51de 0   LOG:  Wrote instance status successfully.

2017-07-05 22:01:02.551 UTC 595d60ae.51de 0   LOG:  Updated instance status successfully.

i have no idea about the trouble shooting, can somebody help?

Tags (1)
0 Kudos
4 Replies
Sreejesh_D
Virtuoso
Virtuoso
‎07-05-2017 10:56 AM

I would suggest to reboot the VCSA and clear your browser cache and cookies. After this try accessing the URL

0 Kudos
vijayrana968
Virtuoso
Virtuoso
‎07-05-2017 11:36 AM

You need to check 4 things for this particular error, most of time this is due to vsphere webclient service:

  1. Verify that connectivity exists from the machine trying to access the vSphere Web Client to vCenter Server with telnet by running this command:

    telnet vcenter_fqdn 9443

  2. Ensure that vCenter Server services are running using this command (this can be ran on a Windows installation or Appliance):

    service-control --status --all

    Note: Before continuing, investigate if there are other services failing to start.


  3. Restart the vSphere Web Client manually from services.msc and set it to Automatic (delayed start)

Follow the steps in KB "503 service unavailable" error when connecting to vSphere Web Client (2121043) | VMware KB

0 Kudos
oliver_gao
Contributor
Contributor
‎07-05-2017 06:22 PM

I tried cleaning, but it still doesn't work.

0 Kudos
oliver_gao
Contributor
Contributor
‎07-05-2017 06:48 PM

hummm...unfortunately failed to connect with VCSA via telnet by port 9443, but i found that my VCSA is working now !!!

i am not sure about the reason, but i did something: i updated my VCSA from 6.5a to 6.5e.

PS: at first, the web client was not accessible either, according to your comments, i tried "service-control --start --all" then everything becomes normal.

Looks the new VCSA(VMware Photon based) is so stupid, not stable like the SUSE based VCSA previously.

Finally hoping VMware can release update ASAP to fix bugs.

0 Kudos