<?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: vRO 7.5 HTTP Status 503 - Service Unavailable in VMware Aria Automation Orchestrator Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524775#M4602</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check if you can open vRO ControlCenter at &lt;A href="https://&amp;lt;vro-address&amp;gt;:8283/vco-controlcenter/config"&gt;https://&amp;lt;vro-address&amp;gt;:8283/vco-controlcenter/config&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it opens normally, then you can go to Manage &amp;gt; Configure Authentication Provider page and reconfigure the authentication, pointing it to your new PSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Feb 2020 13:35:39 GMT</pubDate>
    <dc:creator>iiliev</dc:creator>
    <dc:date>2020-02-18T13:35:39Z</dc:date>
    <item>
      <title>vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524774#M4601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;IP address&amp;gt;:8281/vco returns a 503.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;We stood up a new one with a new name and IP&lt;/P&gt;&lt;P&gt;I haven't tried vRO&amp;nbsp; since, but now I get the 503.&lt;/P&gt;&lt;P&gt;Rebooted.&lt;/P&gt;&lt;P&gt;Console screen looks OK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could the "missing" PSC be the problem with vRO?&lt;/P&gt;&lt;P&gt;How can I check / change the PSC that vRO uses - I'd need to do it either from the console or SSH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a case open, but seeing if I get an answer here sooner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 13:18:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524774#M4601</guid>
      <dc:creator>TBKing</dc:creator>
      <dc:date>2020-02-18T13:18:33Z</dc:date>
    </item>
    <item>
      <title>Re: vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524775#M4602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check if you can open vRO ControlCenter at &lt;A href="https://&amp;lt;vro-address&amp;gt;:8283/vco-controlcenter/config"&gt;https://&amp;lt;vro-address&amp;gt;:8283/vco-controlcenter/config&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it opens normally, then you can go to Manage &amp;gt; Configure Authentication Provider page and reconfigure the authentication, pointing it to your new PSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 13:35:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524775#M4602</guid>
      <dc:creator>iiliev</dc:creator>
      <dc:date>2020-02-18T13:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524776#M4603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;look at this post which has the same error:&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/608349"&gt;vRO 7.5 / HTTP Status 503 - Service Unavailable during initial configuratin&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ARomeo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 13:37:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524776#M4603</guid>
      <dc:creator>Alex_Romeo</dc:creator>
      <dc:date>2020-02-18T13:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524777#M4604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Control Center - Page not found&amp;nbsp; (404)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can only get to the :5480 page&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 13:46:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524777#M4604</guid>
      <dc:creator>TBKing</dc:creator>
      <dc:date>2020-02-18T13:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524778#M4605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check if the ControlCenter service is up and running. To do so, open an SSH connection to the appliance and run the command:&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="_jivemacro_uid_15820356194864726 jive_macro_code jive_text_macro" data-renderedposition="29_8_1232_16" jivemacro_uid="_15820356194864726"&gt;&lt;P&gt;service vco-configurator status&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the status should be RUNNING. If needed, you can start / restart the service with the following commands, respectively:&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="_jivemacro_uid_15820356261529401 jive_macro_code jive_text_macro" data-renderedposition="87_8_1232_32" jivemacro_uid="_15820356261529401"&gt;&lt;P&gt;service vco-configurator start&lt;/P&gt;&lt;P&gt;service vco-configurator restart&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also try to reset the authentication with the following command:&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_macro_code _jivemacro_uid_15820356327424508 jive_text_macro" data-renderedposition="161_8_1232_16" jivemacro_uid="_15820356327424508"&gt;&lt;P&gt;/usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_macro_code _jivemacro_uid_15820359070814174 jive_text_macro" data-renderedposition="240_8_1232_16" jivemacro_uid="_15820359070814174"&gt;&lt;P&gt;ch.dunes.authentication.provider = vsphere&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;to&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="_jivemacro_uid_15820359144522266 jive_macro_code jive_text_macro" data-renderedposition="277_8_1232_16" jivemacro_uid="_15820359144522266"&gt;&lt;P&gt;ch.dunes.authentication.provider = ldap&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;saving the file, and then restarting ControlCenter service.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 14:25:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524778#M4605</guid>
      <dc:creator>iiliev</dc:creator>
      <dc:date>2020-02-18T14:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: vRO 7.5 HTTP Status 503 - Service Unavailable</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524779#M4606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A restart didn't do it, neither did the "reset-authentication" ... HOWEVER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got an email from support.&lt;/P&gt;&lt;P&gt;The process that did fix it was:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stop configurator&lt;/P&gt;&lt;P&gt;Reset-authentication &lt;/P&gt;&lt;P&gt;Start configurator&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That got me into the Configurator GUI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the steps were correct, just a bit out of order (or not clarified)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From there I was able to verify that the authentication was pointing to the PSC we took down.&lt;/P&gt;&lt;P&gt;And of course I couldn't "Unregister" because it was down, but a RESET allowed me to enter the new PSC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2020 19:55:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/vRO-7-5-HTTP-Status-503-Service-Unavailable/m-p/524779#M4606</guid>
      <dc:creator>TBKing</dc:creator>
      <dc:date>2020-02-18T19:55:58Z</dc:date>
    </item>
  </channel>
</rss>

