The vRealize Operations Manager custom UI is inaccessible after starting or restarting the services
search cancel

The vRealize Operations Manager custom UI is inaccessible after starting or restarting the services

book

Article ID: 340546

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • After a start or restart of the VMware vRealize Operations (formerly known as vCenter Operations Manager) services, the Custom UI is not accessible.
  • The vcopswebenterprise service does not start automatically.
  • The vcopswebenterprise service has to be started manually and the Custom UI is accessible.


Cause

This issue occurs when the vcops-admin script attempts to start the vcopsweb service (vSphere UI) and then start the vcopswebenterprise service (Custom UI) after the vcopsweb service starts successfully. In very large environments, the vcopsweb service may take too long to start and the vcsop-admin command does not attempt to start the vcopswebenterprise service.

Resolution

This issue is resolved in vRealize Operations Manager (formerly known as vCenter Operations Manager) 5.6.

To resolve this issue, you have to set correct ownership and permissions to vcops-admin.pl file and CIQDisk.pm file in UI VM.

To set correct ownership and permissions to vcops-admin.pl file and CIQDisk.pm file in UI VM:

  1. Download the attached vcopswebenterprise_startup.zip file.
  2. If the version of vRealize Operations Manager (formerly known as vCenter Operations Manager) is 5.0.3, build 818421 or lower then:
    • Extract the vcops-admin.pl file from the vcopswebenterprise_startup.zip file and copy it to the /tmp folder on the UI VM.
    • Log in to the UI VM as the root user.
    • Make a copy of the /usr/lib/ciq/vcops-admin.pl file:

      cp -rfp /usr/lib/ciq/vcops-admin.pl /usr/lib/ciq/vcops-admin.pl.orig


    • Copy the new vcops-admin.pl file from the /tmp folder to the /usr/lib/ciq/ folder:

      cp -f /tmp/vcops-admin.pl /usr/lib/ciq/vcops-admin.pl


    • Ensure that the ownership and permissions are set correctly on the new vcops-admin.pl file:
chown admin:admin /usr/lib/ciq/vcops-admin.pl
chmod 777 /usr/lib/ciq/vcops-admin.pl
  1. If the version of vRealize Operations Manager (formerly known as vCenter Operations Manager) is 5.0.3, build 977932 or higher:

    • Extract the CIQDisk.pm file from the vcopswebenterprise_startup.zip file and copy it to the /tmp folder on the UI VM.
    • Log in to the UI VM as the root user.
    • Make a copy of the /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm file:

      cp -rfp /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm.orig


    • Copy the new CIQDisk.pm file from the /tmp folder to the /usr/lib/perl5/5.10.0/VMware/CIQAdmin/ folder:

      cp -f /tmp/CIQDisk.pm
      /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm


    • Ensure that the ownership and permissions are set correctly on the new CIQDisk.pm file:
chown admin:root /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm
chmod 777 /usr/lib/perl5/5.10.0/VMware/CIQAdmin/CIQDisk.pm


Additional Information

This issue is corrected in vRealize Operations Manager (formerly known as vCenter Operations Manager) 5.6.

Attachments

vcopswebenterprise_startup.zip get_app