<?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 VCSA 6.5 - Multiple issues in Technical Community Resources and Help Discussions</title>
    <link>https://communities.vmware.com/t5/Technical-Community-Resources/VCSA-6-5-Multiple-issues/m-p/2850821#M2933</link>
    <description>&lt;P&gt;Ok,&amp;nbsp; lots of issues here with our VCSA 6.5 u3 build 14389939.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When http'ing into VCSA vCenter GUI, I get the&amp;nbsp;&lt;EM&gt;"503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055d802483b10] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)"&amp;nbsp;&amp;nbsp;&lt;/EM&gt;error and tried the fixes I fond but they didn't work. ( a. Root password had expired&amp;nbsp; &amp;nbsp;b. Partitions were filled over 95%&amp;nbsp; c.&amp;nbsp;Certificate regeneration)......although I must admit I didn't really know what to put in the prompts for the &lt;SPAN&gt;certool.cfg file configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;VAMI works ok through :5480, however it's kind of screwed up. I updated it with the latest security patch&amp;nbsp; (VMware-vCenter-Server-Appliance-6.5.0.35000-17994927-patch-FP) but the version remains old despite saying it's at the latest. (screenshot attached, and yes I rebooted after the initial upgrade)&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried standing up a new VCSA, but can't license it, as it seems to know the license has been allocated to the old one. So what I would really like to do is un-license the existing one and license the new one. Does anyone know how to do that from the command line? .....or have any other suggestions to fix all of this?&amp;nbsp; &amp;nbsp; Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jun 2021 16:36:26 GMT</pubDate>
    <dc:creator>GWOD1</dc:creator>
    <dc:date>2021-06-03T16:36:26Z</dc:date>
    <item>
      <title>VCSA 6.5 - Multiple issues</title>
      <link>https://communities.vmware.com/t5/Technical-Community-Resources/VCSA-6-5-Multiple-issues/m-p/2850821#M2933</link>
      <description>&lt;P&gt;Ok,&amp;nbsp; lots of issues here with our VCSA 6.5 u3 build 14389939.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When http'ing into VCSA vCenter GUI, I get the&amp;nbsp;&lt;EM&gt;"503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055d802483b10] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)"&amp;nbsp;&amp;nbsp;&lt;/EM&gt;error and tried the fixes I fond but they didn't work. ( a. Root password had expired&amp;nbsp; &amp;nbsp;b. Partitions were filled over 95%&amp;nbsp; c.&amp;nbsp;Certificate regeneration)......although I must admit I didn't really know what to put in the prompts for the &lt;SPAN&gt;certool.cfg file configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;VAMI works ok through :5480, however it's kind of screwed up. I updated it with the latest security patch&amp;nbsp; (VMware-vCenter-Server-Appliance-6.5.0.35000-17994927-patch-FP) but the version remains old despite saying it's at the latest. (screenshot attached, and yes I rebooted after the initial upgrade)&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried standing up a new VCSA, but can't license it, as it seems to know the license has been allocated to the old one. So what I would really like to do is un-license the existing one and license the new one. Does anyone know how to do that from the command line? .....or have any other suggestions to fix all of this?&amp;nbsp; &amp;nbsp; Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jun 2021 16:36:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Technical-Community-Resources/VCSA-6-5-Multiple-issues/m-p/2850821#M2933</guid>
      <dc:creator>GWOD1</dc:creator>
      <dc:date>2021-06-03T16:36:26Z</dc:date>
    </item>
  </channel>
</rss>

