In NetBackup 8.0 or higher, the Java Console displays "Status Code: 130 System Error Occurred" when attempting connection to a host with an underscore in its hostname.

In NetBackup 8.0 or higher, the Java Console displays "Status Code: 130 System Error Occurred" when attempting connection to a host with an underscore in its hostname.

Article: 100033400
Last Published: 2020-02-21
Ratings: 7 10
Product(s): NetBackup

Problem

After upgrading / installing NetBackup 8.0 or higher, the Java Console can connect, but an error is visible in the "Login Activity" indicator.

The error reads as follows:
Status Code: 130System error occurred.

Example:
User-added image

Note: There is no space between "130" and "System error occurred."

Other portions of the GUI also produce similar errors.  These include:
  • Media and Device Management > Credentials > WebSocket Servers
  • Security Management > Security Events
  • Security Management > Certificate Management
  • Security Management > Certificate Management > Token Management

Example:
User-added image


 

Error Message

Get Tokens: Status Code: 130

System error occurred.

Messages similar to the following my appear in the Java Console log ( <install_path>\VERITAS\NetBackup\logs\user_ops\nbjlogs\jbp.<xxx>.log):
[12/13/16 1:13:42 PM PST {1481663622995}] [262144] RestLogger-> ===========================WEB REQUEST RESPONSE BEGIN===========================
[12/13/16 1:13:42 PM PST {1481663622995}] [262144] RestLogger-> Request Begins ...............
[12/13/16 1:13:42 PM PST {1481663622995}] [262144] RestLogger-> URI : https://jdhv2_2012R2_3:1556/netbackup/loginwithbpjavasessiontoken
[12/13/16 1:13:42 PM PST {1481663622995}] [262144] RestLogger-> Method : POST
[12/13/16 1:13:42 PM PST {1481663622995}] [262144] RestLogger-> Request Body : NOT logging request body.......
[12/13/16 1:13:43 PM PST {1481663623042}] [262144] SecureTransport-> atDataDir path isC:\Program Files\Veritas\NetBackup\var\vxss\at\systemprofile\systruststore
[12/13/16 1:13:43 PM PST {1481663623042}] [262144] SecureTransport-> Certificate location is: C:\Program Files\Veritas\NetBackup\var\vxss\at\systemprofile\systruststore\..\certstore\trusted\
[12/13/16 1:13:43 PM PST {1481663623042}] [262144] SecureTransport-> Total Number of certificate file in director is:1
[12/13/16 1:13:43 PM PST {1481663623089}] [262144] SecureTransport-> Sucessfully verified hostname jdhv2_2012R2_3
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> Response Begins for URI: https://jdhv2_2012R2_3:1556/netbackup/loginwithbpjavasessiontoken
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> status code: 500
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> status text: Internal Server Error
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> Response Body : NOT logging response body.......
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> Response Time: 141 ms
[12/13/16 1:13:43 PM PST {1481663623136}] [262144] RestLogger-> ============================WEB REQUEST RESPONSE END============================



From the nbwebservice log (<install_path>\VERITAS\NetBackup\logs\nbwebservice; OIDs 484, 485):
12/1/2016 07:47:12.193 [Application] NB 51216 nbgateway 484 PID:2572 TID:54 File ID:484 [No context] [Error]  No access token found for accessing the secured URI /netbackup/config/servers/wssendpoints
12/1/2016 07:47:12.443 [Debug] NB 51216 nbwss 485 PID:2572 TID:30 File ID:485 [No context] 1 [com.netbackup.nbwss.service.NetBackupRESTService] Response Code: 401
12/1/2016 07:47:12.459 [Debug] NB 51216 nbwss 485 PID:2572 TID:30 File ID:485 [No context] 1 [com.netbackup.nbwss.service.NetBackupRESTService] Response Payload: {"errorCode":117,"errorMessage":"access denied"}
12/1/2016 07:47:12.475 [Application] NB 51216 nbwss 485 PID:2572 TID:30 File ID:485 [No context] [Error] Failed to fetch list of server endpoints - com.netbackup.nbwss.exception.BadMessageException: {"errorCode":117,"errorMessage":"access denied"}    at com.netbackup.nbwss.service.NetBackupRESTService.getServerEndPoints(NetBackupRESTService.java:67)    at

(...truncated for clarity)
12/1/2016 07:47:16.146 [Application] NB 51216 nbgateway 484 PID:2572 TID:58 File ID:484 [No context] [Error] getHostSession->Null host session
12/1/2016 07:47:16.146 [Application] NB 51216 nbgateway 484 PID:2572 TID:58 File ID:484 [No context] [Error] getHostSession->Establishing connection with NBSL on host :jdhv2_2012r2_3
12/1/2016 07:47:17.303 [Application] NB 51216 nbgateway 484 PID:2572 TID:58 File ID:484 [No context] [Error] java.lang.IllegalStateException: Could not get HttpServletRequest URI: Illegal character in hostname at index 13: https://jdhv2_2012R2_3:1556/netbackup/loginwithbpjavasessiontoken


Notice the 13th character in the string "https:// jdhv2_2012R2_3:1556/netbackup/loginwithbpjavasessiontoken" is an underscore ("_").

Cause

This issue occurs because the hostname of the server to which the NetBackup Java Console connects contains one or more underscores.  The underscore is not supported by various language libraries in the JDK (Java Development Kit) as a valid character in a hostname.

There is a new Service in NetBackup 8.0 and higher, NetBackup Web Management Console, which relies on these new language libraries.

 

Solution

Starting in NetBackup 8.0, the NetBackup Java Administration Console is no longer able to function properly when the specified hostname contains an underscore character.

Please ensure all NetBackup hostnames comply with  RFC-952  and  RFC 1123

Temporary Workaround
In the event you encounter this issue upon upgrading to NetBackup 8.0 and higher, it may be possible to use the console without error by supplying the IP Address of the problematic host in the "Host name" field on the log in screen.

Example:
User-added image

In some environments not all functions and features are available when using the IP address.  In addition, the Java console is not the only consideration for correcting the hostname as quickly as possible.  NetBackup is utilizing web API's for additional functionality and features in newer versions.   The new features may not work and client backups may fail if the problem is not corrected. 

Note:  Using the IP address is meant to be a temporary workaround while seeking a solution to the underlying issue of not using an RFC compliant hostname.  Veritas Consulting Services should be engaged with any host name change.

 

Was this content helpful?