After upgrading to 7.7.2 or later from an earlier version of NetBackup, the Java Administration Console is unable to connect to NetBackup Service Layer (nbsl).

After upgrading to 7.7.2 or later from an earlier version of NetBackup, the Java Administration Console is unable to connect to NetBackup Service Layer (nbsl).

Article: 100031979
Last Published: 2020-04-13
Ratings: 2 6
Product(s): NetBackup

Problem

After upgrading to 7.7.2 or later from an earlier version of NetBackup, the Java Administration Console is unable to connect to  NetBackup Service Layer ( nbsl).  The result is the Backup, Archive and Restore (BAR) GUI is always displayed.

The behavior will be triggered when the REQUIRED_INTERFACE setting is an interface IP address versus the interface name.
 

Error Message

When this issue occurs, the GUI will hang for several minutes with the status in the lower left hand side of the screen stating "Connecting NetBackup Service Layer":


  User-added image


NetBackup 7.7.2 will eventually display a pop up similar to the following stating that NetBackup Service Layer ( nbsl) could not be connected to:
User-added image

At NetBackup Version 7.7.3 the popup that appears will be similar to the following:
User-added image
 
When this occurs, the jbp log file will show the following type of errors:

[10-02-2016 16:20:18:044] vxssiop.connection:INFO: Created bound socket 0.0.0.0/0.0.0.0:51070[10-02-2016 16:20:18:044] vxssiop.connection:INFO: createSocket - Trying to connect to nbmaster1.anydomain.com:1556:nbsl_secsvc[10-02-2016 16:20:18:044] vxssiop.connection:ERROR: [10-02-2016 16:20:18:044] vxssiop.connection:INFO: Failed on retry number: 0[10-02-2016 16:20:19:044] vxssiop.connection:INFO: Created bound socket 0.0.0.0/0.0.0.0:51071[10-02-2016 16:20:19:044] vxssiop.connection:INFO: createSocket - Trying to connect to nbmaster1.anydomain.com:1556:nbsl_secsvc[10-02-2016 16:20:19:044] vxssiop.connection:ERROR: [10-02-2016 16:20:19:044] vxssiop.connection:INFO: Failed on retry number: 1[10-02-2016 16:20:20:045] vxssiop.connection:INFO: Created bound socket 0.0.0.0/0.0.0.0:51072[10-02-2016 16:20:20:045] vxssiop.connection:INFO: createSocket - Trying to connect to nbmaster1.anydomain.com:1556:nbsl_secsvc[10-02-2016 16:20:20:045] vxssiop.connection:ERROR: [10-02-2016 16:20:20:045] vxssiop.connection:INFO: Failed on retry number: 2 --- This will repeat several times ---

Eventually it times out: [10-02-2016 16:21:19:077] vxssiop.connection:INFO:

Failed on retry number: 5(ObjSvc)org.jacorb.orb.Reference._non_existent,,6004 Request ID: 16 Server: nbmaster1.anydomain.com Time Taken: 6004ms Successful: Reply Status: Unknown SystemException: org.omg.CORBA.TRANSIENT[2/10/16 4:21:21 PM GMT {1455121281077}] [262144] ICACHE.ObjectService.CORBAImpl-> Could not connect to nbsl: class org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to null


When this is occurring, the pbx log files will show " No proxy found." for requests to nbsl_secsvc: [

Info] PBX_Client_Proxy::handle_close[Info] PBX_Manager:: handle_input with fd = 0x25c[Info] PBX_Client_Proxy::parse_line, line = ack=1 From 10.1.1.1[Info] PBX_Client_Proxy::parse_line, line = extension=nbsl_secsvc From 10.1.1.2[Info] hand_off looking for proxy for = nbsl_secsvc[Warning] No proxy found.

 

Cause

In 7.7.2 and 7.7.3, security enhancements to NetBackup login require certificate exchanges. Certificates are issued based on host names, not IP addresses, so the security service will reject any inquiry based on IP.

This will affect all versions of NetBackup later than 7.7.2.
 

Solution

Remove or correct the registry setting (Windows) or bp.conf file (UNIX) setting for REQUIRED_INTERFACE.

  • UNIX:  /usr/openv/netbackup/bp.conf 
  • Windows Registry:   HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config

Stop and restart NetBackup services after making any changes.

The Required Interface setting, if used, should specify a hostname that resolves to the IP address of a networking interface or sub-interface that is local to the host.  That IP address should reverse resolve back to the same hostname.

Note that there are other reasons this behavior might occur:

1. The nbsl service is not running. If a user account is specified, try changing it to Local System.

2. A missing or misconfigured auth.conf file.

  • On Windows NetBackup servers, a template file named auth.conf.win.template is present at NB_Install/Java. Use this template file to create an auth.conf file at the same location.
  • On UNIX NetBackup servers, the auth.conf file is located at NB_Install/Java.
  • This file can also be copied from a working system.

 

Note: This issue is not the same issue as ET3867824 which was fixed in 7.7.3.

ET3867824 has a downloadable hotfix for NetBackup 7.7.2 which resolves an issue where the Java GUI on a Windows server fails to connect and some NetBackup services fail to start. See:

https://www.veritas.com/content/support/en_US/downloads/update.UPD833699

 

References

Etrack : 3868358

Was this content helpful?