Problem
After upgrading NetBackup from 8.0 to 8.1 or later, the NetBackup Web Management Console service may fail to start properly. During the course of troubleshooting the startup issue, the configureWmc
command may be run by itself or as part of a sequence of troubleshooting steps. The command may produce errors similar to these:
The configureWmc
command resides within: /usr/openv/wmc/bin/install
[root@MyMaster install]# ./configureWmc
./configureWmc: line 169: [: /usr/openv/netbackup/web/bcprov-jdk15on-1.51.jar: binary operator expected
./configureWmc: line 169: [: /usr/openv/netbackup/web/c3p0-0.9.1.jar: binary operator expected
./configureWmc: line 169: [: /usr/openv/netbackup/web/jconn4-16.0.jar: binary operator expected
Error Message
If you see binary operator expected
, the command has failed to complete properly.
Note: NetBackup 8.2 and newer will proactively detect this problem during upgrade, and will fail the upgrade with the following message:
not ok wmc_jar_files_check: Multiple versions of file some-nn.n.jar found, possibly an uninstall of prior version failed
When you upgrade the NetBackup master server from 8.0 to 8.1 or later, the .jar files within NetBackup Web Management Console (WMC) installation folder should be replaced with newer versions. However,occasionally when the new files are added the old files are not removed.
Refer to the following article for more details:
https://www.veritas.com/support/en_US/article.100042889
Cause
This error suggests multiple copies of the named jar files exist within the /usr/openv/netbackup/web
folder. When you upgrade NetBackup from NetBackup 8.0 to 8.1 or later, the jar files within this folder should be replaced with later versions. Sometimes the new files are added, but the old files are not removed.
Solution
In this example, the following file duplicate files existed within the /usr/openv/netbackup/web
folder:
bcprov-jdk15on-1.51.jar <--- old
bcprov-jdk15on-1.57.jar
c3p0-0.9.1.jar <--- old
c3p0-0.9.5.2.jar
jconn4-16.0.jar
jconn4-7.07.20686.jar <--- old
The solution is to remove all old iterations of the problematic .jar
file duplicates listed on-screen by the configureWmc
command. Rerun the configureWmc
command and continue troubleshooting the issue.
NOTE: Although the on-screen message names specific jar file versions, those versions are not necessarily the newest or the oldest. Do not simply remove a file named in the command output. Ensure that you have identified the oldest of the file pairs and remove those.
NOTE: If you run "configureWmc" command after the HotFix of article.100044601 was installed, security.war or netbackup.war is replaced with the original file. Please refer to the following article for details and execute the steps described in the Solution section.
Tomcat and nbwebsvc certificates are not renewed after HotFix in article.100044601 was applied.