vRO 7.5 HTTP Status 503 - Service Unavailable

[TBKing]

<IP address>:8281/vco returns a 503.

Earlier in the year we had an issue with a PSC and had to remove it from our environment, and it won't be replaced.

We stood up a new one with a new name and IP

I haven't tried vRO  since, but now I get the 503.

Rebooted.

Console screen looks OK

Could the "missing" PSC be the problem with vRO?

How can I check / change the PSC that vRO uses - I'd need to do it either from the console or SSH

I have a case open, but seeing if I get an answer here sooner.

Thx

[iiliev]

Check if you can open vRO ControlCenter at https://<vro-address>:8283/vco-controlcenter/config

If it opens normally, then you can go to Manage > Configure Authentication Provider page and reconfigure the authentication, pointing it to your new PSC.

You can also check the vRO logs (for example, /var/log/vco/app-server/server.log) to see if there any errors / exceptions showing why the vRO server isn't starting normally.

[Alex_Romeo]

Hi,

look at this post which has the same error:

vRO 7.5 / HTTP Status 503 - Service Unavailable during initial configuratin

ARomeo

[TBKing]

Control Center - Page not found  (404)

I can only get to the :5480 page

[iiliev · Accepted solution]

Check if the ControlCenter service is up and running. To do so, open an SSH connection to the appliance and run the command:

service vco-configurator status

the status should be RUNNING. If needed, you can start / restart the service with the following commands, respectively:

service vco-configurator start
service vco-configurator restart

You can also try to reset the authentication with the following command:

/usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication

Let's check if you'll be able to open ControlCenter UI at this point. If not, then you can try to manually change the authentication provider configuration, stored in the file /etc/vco/app-server/vmo.properties, by changing the line

ch.dunes.authentication.provider = vsphere

to

ch.dunes.authentication.provider = ldap

saving the file, and then restarting ControlCenter service.

[TBKing]

A restart didn't do it, neither did the "reset-authentication" ... HOWEVER

I got an email from support.

The process that did fix it was:

Stop configurator

Reset-authentication

Start configurator

That got me into the Configurator GUI

So the steps were correct, just a bit out of order (or not clarified)

From there I was able to verify that the authentication was pointing to the PSC we took down.

And of course I couldn't "Unregister" because it was down, but a RESET allowed me to enter the new PSC

Thanks