cancel
Showing results for 
Search instead for 
Did you mean: 

Can't initiate bpjobd after upgrade to NB 7.0.1

Alexis_Gonzalo_
Level 4

Server is a RedHat Linux, originally with NetBackup Enterprise Server 6.5.5.

Today we upgraded from NB 6.5.5 to 7.0, without problems. Some minutes later we upgraded to 7.0.1 (we need 7.0.1 for some Hyper-V features) and then we lost the functionality with the Activity Monitor. We got an error, "Operation in progress". Also, the command "bpdbjobs" didn't showed any output (got back to prompt after some seconds).

We found out that after the upgrade to 7.0.1, the daemon bpjobd was no longer up. We tried initiating it manually, but it stopped after some seconds.

With VERBOSITY = 1 we created the following logs in the bpjobd directory:

(hostname is "veritas").

15:01:37.333 [27024] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1140: 0: connect in progress: 1 0x00000001
15:01:37.334 [27024] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.656: pbxSetAddrEx/pbxConnectEx return error 104:Connection reset by peer
15:01:37.334 [27024] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1658: 0:vnet_pbxConnect() failed: 18 0x00000012
15:01:37.334 [27024] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1659: 0:save_errno: 104 0x00000068
15:01:37.334 [27024] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1660: 0:use_vnetd: 0 0x00000000
15:01:37.334 [27024] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1661: 0:cr->vcr_service: bpdbm
15:01:37.334 [27024] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1293: 0: do_service failed: 18 0x00000012
15:01:37.334 [27024] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1140: 0: connect in progress: 1 0x00000001
15:01:37.335 [27024] <2> vnet_vnetd_pbx_c_supported: ../../libvlibs/vnet_vnetd.c.4867: 0: VN_REQUEST_PBX_C_SUPPORTED: 13 0x0000000d
15:01:37.414 [27024] <2> do_vnetd_service: ../../libvlibs/vnet_connect.c.1581: 0: remote host supports PBX, but PBX is not running: 0 0x00000000
15:01:37.414 [27024] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2196: 0: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
15:01:37.414 [27024] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2210: 0: service: bpdbm
15:01:37.456 [27024] <2> do_vnetd_service: ../../libvlibs/vnet_connect.c.1618: 0: via VNETD: bpdbm CONNECT FROM 10.255.253.72.58774 TO 10.255.253.72.13724 fd =
11
15:01:37.456 [27024] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1307: 0: connect: async CONNECT FROM 10.255.253.72.58774 TO 10.255.253.72.13724 fd =
11
15:01:37.456 [27024] <2> vnet_cached_getaddrinfo: ../../libvlibs/vnet_addrinfo.c.1121: 0: found in cache name: veritas
15:01:37.456 [27024] <2> vnet_cached_getaddrinfo: ../../libvlibs/vnet_addrinfo.c.1122: 0: found in cache service: NULL
15:01:37.456 [27024] <2> logconnections: BPDBM CONNECT FROM 10.255.253.72.58774 TO 10.255.253.72.13724 fd = 11
15:01:37.456 [27024] <2> vnet_check_vxss_client_magic_with_info: ../../libvlibs/vnet_vxss_helper.c.878: 0: Ignoring VxSS authentication: 2 0x00000002
15:01:37.459 [27024] <2> db_end: Need to collect reply
15:01:37.462 [27024] <2> getsockbound: service=bpjobd protocol=tcp port=13723
15:01:37.504 [27024] <2> vnet_registerPBXServer: ../../libvlibs/vnet_pbx.c.118:pbxRegisterEx failed with error 0:Success
15:01:37.504 [27024] <16> main: Can't setup pbx socket for accept
15:01:37.505 [27024] <2> doexit: Exiting....

 

The PBX service was up; we restarted it anyway to no avail. As I said, we downgraded to NetBackup 7.0 and everything's fine now. I don't know if I can upgrade PBX; it's in version 1.4.6.0 now.

Any ideas would be appreciated.

2 REPLIES 2

thesanman
Level 6

Not sure if there's any relevance here but check http://www.symantec.com/business/support/index?page=content&id=TECH139092 for v7.0.1 late breaking news.

There's a reference to an issue if you have IPv6 enabled ... might be of relevance.  I'd log a support call.

I saw no issues when upgrading by test environment from v6.5.5 to v7.0.1 (Linux).

Alexis_Gonzalo_
Level 4

The Hotfix looked promising, but IPv6 is disabled.

I opened a support call...