Originator ID 486

The NetBackup proxy helper log files are useful when there are issues with communication due to SSL/TSL errors or other secure communication issues. You can start the processes by using the vnetd - standalone command. If there are startup and shutdown issues, examine the vnetd log file.

The following are examples of the expected minimum number of vnetd processes:

/usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0

/usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0

/usr/openv/netbackup/bin/vnetd  - standalone

The inbound and outbound proxy processes send logs to the nbpxyhelper log files. The communication between them can be followed through the job details; it locates the :INBOUND or :OUTBOUND connection ID and searches for them in the nbpxyhelper log files. The :INBOUND and :OUTBOUND connections are only displayed if there is an error. See the following example:

Aug 5, 2018 5:13:14 PM - Info nbjm (pid=3442) starting backup job (jobid=268) for 
  client nbclient1, policy ANY_nbclient1, schedule Full-EXPIRE_IMMEDIATELY
Aug 5, 2018 5:13:14 PM - Info nbjm (pid=3442) requesting STANDARD_RESOURCE resources from RB
  for backup job (jobid=268, request id:{5DD92BD0-98F4-11E8-AEE4-55B66A58DDB2})
Aug 5, 2018 5:13:14 PM - requesting resource  __ANY__
Aug 5, 2018 5:13:14 PM - requesting resource  nbmaster2.NBU_CLIENT.MAXJOBS.nbclient1
Aug 5, 2018 5:13:14 PM - requesting resource  nbmaster2.NBU_POLICY.MAXJOBS.ANY_nbclient1
Aug 5, 2018 5:13:15 PM - Error bpbrm (pid=21177) [PROXY] Connecting host: nbmaster2
Aug 5, 2018 5:13:15 PM - Error bpbrm (pid=21177) [PROXY] ConnectionId: 
  {5E0FBBD2-98F4-11E8-804A-EC7198374CC6}:OUTBOUND

By default, OID 486 is set to DebugLevel=0 due to the potential to create many log files. Do not leave the logging enabled for long periods of time at DebugLevel=6.

The logging level can be changed by using the vxlogcfg command. See the following examples:

To add logging, use the following command:

vxlogcfg -a -p NB -o 486 -s DebugLevel=6

To remove logging, use the following command:

vxlogcfg -a -p NB -o 486 -s DebugLevel=0