Skip to main content
Solved

Cannot launch PE from PC after upgrade to 5.20.3.5 LTS?

  • Apr 20, 2022 7:20 PM UTC
  • 13 replies
  • 1080 views

Forum|alt.badge.img

We’ve noticed that after updating clusters to AOS 5.20.3.5 LTS, we’re unable to launch those clusters from PC. PE seems to still be fine. Anyone run into this?

Best answer by sdk404

Got it!

Poked around some today. The various version folders on the PC nodes were missing the ‘console’ folder. KB 11663 gives a command to run to manually extract this. Once I did that on all the PC nodes, was again able to launch PE from PC.

View original
This topic has been closed for replies.

13 replies

  • Adventurer
  • Apr 21, 2022 10:03 AM UTC

Hi, has the PC also been updated to the latest release?


Forum|alt.badge.img
  • Author
  • Adventurer
  • Apr 21, 2022 4:35 PM UTC

yes. It only appears to be affecting clusters that we’ve updated to 5.20.3.5. We have one newer one that shipped with 6.x, and it was ok after the update.


  • Voyager
  • Apr 21, 2022 8:13 PM UTC

I experienced similar issues to this after upgrading PC, and discovered the CVM was out of disk space. Maybe run a “df - h” command if you can get to the CVMs and check the usage on the /home dir.


Forum|alt.badge.img
  • Author
  • Adventurer
  • Apr 21, 2022 8:16 PM UTC

Nope, not seeing high disk usage on the CVMs.


  • Adventurer
  • Apr 22, 2022 8:15 AM UTC

Rather basic but have you tried rebooting the PC as well? If that doesn’t help I think you’ll need to reach out to support, see if it’s a known bug with the latest release of 5.20.x


Forum|alt.badge.img
  • Author
  • Adventurer
  • Apr 22, 2022 2:09 PM UTC

PC reboot unfortunately did not clear the issue. We have an SR open, but crickets so far. Uncharacteristically long response time on this one.


Michael.Manuele
Nutanix Employee
Forum|alt.badge.img+4

What version of PC and can you share the SR#?


  • Voyager
  • Apr 28, 2022 9:38 AM UTC

same issue here after upgrading the AOS to 5.20.3.5 LTS. It’s ok with other cluster with 5.20.3 LTS so it seems to be related to the prism element and not to PC pc.2022.1.0.2.


Forum|alt.badge.img
  • Author
  • Adventurer
  • Apr 28, 2022 12:36 PM UTC

so far, the SE was thinking something is going on with Mercury on the PC cluster. We see this issue with every cluster we move to 5.20.3.5 LTS. One cluster was newer and shipped with 6, an it’s unaffected. PC v. 2022.10.2. Still waiting for his further analysis.


Forum|alt.badge.img
  • Author
  • Adventurer
  • Apr 29, 2022 12:55 PM UTC

sorry, PC 2022.1.0.2.


ThomasD
Forum|alt.badge.img+10
  • Trailblazer
  • May 2, 2022 6:44 AM UTC

Forum|alt.badge.img
  • Author
  • Adventurer
  • May 2, 2022 12:42 PM UTC

The SE went through, that, and it didn’t help. He said he was seeing some logs that pointed him to an issue with the mercury service. Waiting on an update.

 


Forum|alt.badge.img
  • Author
  • Adventurer
  • Answer
  • May 2, 2022 7:13 PM UTC

Got it!

Poked around some today. The various version folders on the PC nodes were missing the ‘console’ folder. KB 11663 gives a command to run to manually extract this. Once I did that on all the PC nodes, was again able to launch PE from PC.