vSphere Replication upgrade to 6.1.2.1 fails with an error "cannot stat /usr/java/jre1.7.0_101/bin/java: No such file or directory "
search cancel

vSphere Replication upgrade to 6.1.2.1 fails with an error "cannot stat /usr/java/jre1.7.0_101/bin/java: No such file or directory "

book

Article ID: 338450

calendar_today

Updated On:

Products

VMware Live Recovery VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Upgrade stops responding on the VAMI page when the appliance is upgraded from 6.1.1.x version to 6.1.2.1 after Replication.
  • The replication appliance console reports the error:
cannot stat /usr/java/jre1.7.0_101/bin/java: No such file or directory
  • After refresh of VAMI page, it returns to the login page. However, re-login reports an error:
invalid server response
  • In the /opt/vmware/var/log/vami/updatecli.log file, you see installation running in the background as last update which remains same even after the reboot.
03/01/2018 20:48:21 [INFO] Reboot required when installing kernel-default package03/01/2018 20:48:21 [INFO] Created reboot required file
03/01/2018 20:48:21 [INFO] Update 6.1.2.16016 manifest is set to be installed
03/01/2018 20:48:21 [INFO] Using update post-install script
03/01/2018 20:48:21 [INFO] Running updatecli to install update. command={ /opt/vmware/share/vami/update/
updatecli '/opt/vmware/var/lib/vami/update/data/job/4' '6.1.1.13216' '6.1.2.16016' ; /opt/vmware/bin/vam
icli version --appliance ; } >> /opt/vmware/var/log/vami/updatecli.log 2>&1 &
03/01/2018 20:48:22 [INFO] Installation running in the background

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vSphere Replication 6.x

Cause

This issue occurs when Replication appliance is directly upgraded from 6.1.1 to 6.1.2.1.

Resolution

To resolve this issue if you have recently upgraded the vCenter from 6.0u2 to 6.0u3c or 6.0u3d:
  1. Revert to the snapshot if there is a snapshot before the upgrade is performed.
  2. Upgrade the Replication appliance to 6.1.2 and then upgrade to 6.1.2.1 .

Note: If you do not have a snapshot before performing the upgrade, ensure to take the snapshot of the replication appliance and then complete the following steps. 

Step 1: Preparation before installing the missing or corrupted files
  1. Download the zip file VR 6.1.1-3849281.zip or VR 6.1.1.1-4595498.zip attached to this Knowledge Base article.
Note: The zip files contains the files needed for version 6.1.x build 3849281 and 4595498.
  1. Extract the zip file. You should see two files similar to:
jre-7u101-linux-x64.rpm
vmware-studio-vami-cimom_2.6.0.9-3609964_x86_64.rpm
  1. Enable SSH on appliance by running command:
/usr/bin/enable-sshd.sh
  1. Install winscp.
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.
  1. Connect to the appliance using winscp
  2. Use winscp to copy the two files to the /tmp folder of replication appliance.

Step 2: Install the java jre for vSphere Replication

Run the following commands:

  • mkdir /usr/java

Note: You might receive this message if directory already exists. Ignore this error and proceed with other commands.

mkdir: cannot create directory `/usr/java': File exists

rm -f /usr/java/latest /usr/java/default
ln -s /usr/java/jre-vmware /usr/java/latest
ln -s /usr/java/latest /usr/java/default
rm -f /usr/bin/java
ln -s /usr/java/default/bin/java /usr/bin/java

  • rpm -ivh /tmp/jre-7u101-linux-x64.rpm
  • Check the VAMI version by running the command:

rpm -qa | grep studio

You will notice the vmware-studio-vami-cimom_2.6.0.9-3609964_x86_64.rpm file missing from the output.

For the expected output, see the Related Information section of this article.

Step 3: Install the VAMI

Run this command to install the VAMI.

rpm -ivh /tmp/vmware-studio-vami-cimom_2.6.0.9-3609964_x86_64.rpm

Step 4: Reboot the appliance


Additional Information

Note: The jre files attached to zip file in this article can also be copied from ISO for respective build of vSphere Replication.

To browse the files, download the ISO for respective build, mount the ISO to windows machine, and then browse to the update > package-pool folder.

Expected output from each command:

  • mkdir /usr/java

mkdir: cannot create directory `/usr/java': File exists ( This is expected in case directory already exists )

Please ignore and move execute below command

rm -f /usr/java/latest /usr/java/default
ln -s /usr/java/jre-vmware /usr/java/latest
ln -s /usr/java/latest /usr/java/default
rm -f /usr/bin/java
ln -s /usr/java/default/bin/java /usr/bin/java

  • rpm -ivh /tmp/jre-7u101-linux-x64.rpm

Preparing...                ########################################### [100%]
   1:jre                    ########################################### [100%]
Unpacking JAR files...
        rt.jar...
        jsse.jar...
        charsets.jar...
        localedata.jar...
        jfxrt.jar...

Check the VAMI version by running the command:

rpm -qa | grep studio

Output:

​vmware-studio-vami-service-core-2.6.0.9-0
vmware-studio-vami-service-system-2.6.0.9-0
vmware-studio-vami-login-2.6.0.9-3609964
vmware-studio-vami-service-update-2.6.0.9-0
vmware-studio-init-2.6.0.9-160505024738
vmware-studio-vami-service-hms-6.1.1.13216-3849281
vmware-studio-appliance-config-2.6.0.9-160505024738
vmware-studio-vami-servicebase-2.6.0.9-3609964
vmware-studio-vami-service-network-2.6.0.9-0
vmware-studio-vami-tools-2.6.0.9-3609964
vmware-studio-vami-lighttpd-2.6.0.9-3609964

----------------------------------------------------------------------------------------------------------------------
rpm -ivh /tmp/vmware-studio-vami-cimom_2.6.0.9-3609964_x86_64.rpm

Output:

Preparing...                ########################################### [100%]
   1:vmware-studio-vami-cimo########################################### [100%]
Use existing /opt/vmware/lib/libssl.so.1.0.1
Use existing /opt/vmware/lib/libcrypto.so.1.0.1
insserv: Service syslog is missed in the runlevels 4 to use service cgconfig
insserv: Service network is missed in the runlevels 4 to use service hms-vpostgr
vami-sfcb                 0:off  1:off  2:off  3:on   4:off  5:on   6:off


Attachments

52329_3_VR 6.1.1.1-4595498 get_app
VR 6.1.1-3849281.zip get_app