Java Console fails to launch with Status 539

Java Console fails to launch with Status 539

Article: 100031556
Last Published: 2015-11-19
Ratings: 0 1
Product(s): NetBackup

Problem

Starting in NetBackup 7.7, the only available console is the NetBackup Java Administration Console.

This error has been observed when attempting to connect to a Master Server while using NetBackup Java Console
User-added image

Unable to login, status: 539
Verification of X.509 certificate failed when connecting to the bpjava user service on <master server>

 

Cause

In NetBackup 7.7, the NetBackup Authentication service attempts to provide secure connectivity via certificate based authentication.

If the certificate is compromised or missing, the Status 539 may occur.

Solution

Identify if the machine your are connecting to has a certificate.  If you are connecting to the Master Server, check the Master Server.  If you are connecting to a Media Server, check the Media Server, etc....

Certificate Location on Windows and Unix
On Windows:
C:\Program Files\Veritas\NetBackup\var\VxSS\credentials

On Unix:
/usr/openv/var/vxss/credentials


The certificate will look like this on Windows and Unix
On Windows:
09/26/2015  03:35 PM             2,159 MyMaster.lab.symc

On Unix:
-rw------- 1 root root 2064 2015-06-29 16:13 MyMaster
-rw------- 1 root root 2085 2015-06-29 16:13 MyMaster.lab.symc


If the certificate is missing or possibly corrupt, a new certificate can be created.

On the command prompt of the Master Server, use the following command to create a new certificate
On Windows:
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpnbaz -ProvisionCert <hostname>

On Unix:
/usr/openv/netbackup/bin/admincmd/ ./bpnbaz -ProvisionCert <hostname>


Example:
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpnbaz -ProvisionCert MyMaster
Setting up security on target host: MyMaster
Certificate deployed successfully
Operation completed successfully.


The above command will place a certificate into the above directory on the named host.

Once done, the Java Console should no longer encounter the Status 539 error on launch.

Was this content helpful?