2 Replies Latest reply on May 17, 2019 1:44 AM by Nihal Naik

    Issues with CLM 4.6.07 Patch 001: No such source file: /lib/security/cacerts

    Vinnie Lima
      Share:|

      Hey There - anyone else run into issues with CLM 4.6.07 Patch 001 on Linux encountering, what it seems to be, a path issue?  This happens with both bundled and external Java JRE:

       

      (May 02 2019 10:07:21.011 PM -0500),SEVERE,com.bmc.install.product.clmpatchinstaller.CLMPatchInstallerPostInstallConfigUtilities,

        THROWABLE EVENT {Description=[Feature Pack Installer failed to complete],Detail=[No such source file: /lib/security/cacerts]},

        Throwable=[java.io.IOException: No such source file: /lib/security/cacerts

        com.bmc.install.utility.io.FileHelper.copyFileToDirectory(FileHelper.java:387)

        com.bmc.install.utility.io.FileHelper.copyFileToDirectory(FileHelper.java:360)

        com.bmc.install.product.clmpatchinstaller.tasks.CloudPortalConfigTask.backup(CloudPortalConfigTask.java:302)

        com.bmc.install.product.clmpatchinstaller.tasks.CloudPortalConfigTask.backupSSLConfigurations(CloudPortalConfigTask.java:164)

        com.bmc.install.product.clmpatchinstaller.tasks.CloudPortalConfigTask.execute(CloudPortalConfigTask.java:53)

        com.bmc.install.product.clmpatchinstaller.CLMPatchInstallerPostInstallConfigUtilities.applyHotFixtoEnterpriseAR(CLMPatchInstallerPostInstallConfigUtilities.java:644)

        com.bmc.install.product.clmpatchinstaller.CLMPatchInstallerPostInstallConfigUtilities.applyHotFixNew(CLMPatchInstallerPostInstallConfigUtilities.java:3940)

        com.bmc.install.product.clmpatchinstaller.CLMPatchInstallerPostInstallConfigUtilities.configure(CLMPatchInstallerPostInstallConfigUtilities.java:193)

        com.bmc.install.product.clmpatchinstaller.CLMPatchInstallerPostInstallInstallationTask.execute(CLMPatchInstallerPostInstallInstallationTask.java:47)

        com.bmc.install.task.InstallationTask.run(InstallationTask.java:93)

        java.lang.Thread.run(Thread.java:748)]

       

       

       

      It seems like its not referencing the path to the actual JRE HOME:

       

      # echo $JAVA_HOME

      /app/java/jre

       

      # ll /app/java/jre

      lrwxrwxrwx 1 root root 22 Apr  3 12:42 /app/java/jre -> /app/java/jre1.8.0_181

       

      Have a case opened with support, but curious for other fellow CLM-ers if someone has encountered this yet.