Symptoms
During an Avamar upgrade that includes the Security Rollup 2023-R2-V5, it fails on step "Generate mccipher security key and encrypt mc with BSafe 6.2.5 libraries (151 of 230) Failed."The workflow log contains the following errors:
2023-08-09 00:13:05 (+0800) 47258157136540 ERROR: ["/usr/local/avamar/bin/mccipher: line 342: /usr/java/default/bin/java: No such file or directory\n"] - operation failed
Cause
The default symlink is missing from the Java JRE directory in Security Rollup 2023-R2-V5.
root@avamar:/home/admin#: ls -ltr /usr/java
total 0
lrwxrwxrwx 1 root root 31 Aug 10 11:50 jre1.8.0-x64 -> /usr/lib/jvm/jre-1.8-oracle-x64
lrwxrwxrwx 1 root root 31 Aug 10 11:50 latest -> /usr/lib/jvm/jre-1.8-oracle-x64
In Security Rollup 2023-R2-V5, we install Oracle's Java JRE jre-8u371-linux-x64 which includes the issue from Oracle's build where Java's default symlink is missing.For details, see the Oracle document Oracle Release Notes Java 8 .We can see that in a later release Oracle has addressed this issue, and the fix is present in the 2023 R3 OS Security Rollup.
Figure 1: Screenshot showing that Oracle has corrected missing java_default_symlink.
Resolution
Method 1 (preferred)Install the latest OS Security RollupMethod 2 (manual)Re-create the default symlink for the JRE as root user.
ln -s /usr/java/latest /usr/java/default
Verify that the default symlink is created.
root@avamar:~/#: ls -ltr /usr/java/
total 0
lrwxrwxrwx 1 root root 31 Aug 10 11:50 jre1.8.0-x64 -> /usr/lib/jvm/jre-1.8-oracle-x64
lrwxrwxrwx 1 root root 31 Aug 10 11:50 latest -> /usr/lib/jvm/jre-1.8-oracle-x64
lrwxrwxrwx 1 root root 16 Aug 10 13:36 default -> /usr/java/latest
