The nbproxy, nbjm and nbpem daemons are failing to start.

Overview:

The nbproxy , nbjm and nbpem daemons will not start when thecorresponding /usr/openv/var/*.ior files are zero bytes insize.  These *.ior files are interoperable object reference (IOR)files and store, among other things, information on where to find a givenservice.  If this file is empty, the information needed to start theservice will be unavailable and the daemon won'tstart.

Troubleshooting:

The bpps -x command was showing no entriesfor nbproxy , nbjm or nbpem .  Other Veritas NetBackup(tm) daemons and Media Manager daemons can be running.

The nbpemreq command will return thefollowing error since the nbpem daemonis not running:
# nbpemreq-updatepolicies
Could not narrowobject

The .ior files in the /usr/openv/vardirectory will show zero bytes in size:
# ls -la*.ior
-rw-rw-rw- 1root  other   0 Jan 5 17:21nbproxy_jm.ior
-rw-rw-rw- 1root  other   0 Jan 5 17:21nbproxy_pem.ior
-rw-rw-rw- 1root  other   0 Jan 5 17:21nbproxy_pem_email.ior

Log Files:

The unifiedlog files for the nbjm and nbpem originators will show thefollowing errors.  No error messages will be generated in the /usr/openv/netbackup/logs/nbproxy directory since the daemon will neveractually start:

# vxlogview -p 51216 -o 116-t 00:05:00 -d all

01/05/06 17:00:21.927 [NBPClient::Resolve] unable to narrow the servant object. Throwingexception.(../../proxy/nbpclient.h:264)

01/05/06 17:00:21.927[NBPClient::Resolve] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:256)

01/05/06 17:00:21.927[NBPClient::KillNBP] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:101)

01/05/06 17:00:21.928[NBPClient::CreateNBPWithKill] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:66)

01/05/06 17:00:21.928 [Critical] V-117-74 nbjm terminating - failed to start nbproxy,nbproxy_path = /usr/openv/netbackup/bin/nbproxy, client_exception =1027

# vxlogview -p 51216 -o 116-t 00:05:00 -d all

01/05/06 17:00:23.517 [NBPClient::Resolve] unable to narrow the servant object. Throwingexception.(../../proxy/nbpclient.h:264)

01/05/06 17:00:23.518[NBPClient::Resolve] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:256)

01/05/06 17:00:23.518[NBPClient::KillNBP] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:101)

01/05/06 17:00:23.518[NBPClient::CreateNBPWithKill] --- EXITING --- : obj = 0(../../proxy/nbpclient.h:66)

01/05/06 17:00:23.519[JobScheduler::startNBProxy] client_exception:1027(JobScheduler.cpp:289)

01/05/06 17:00:23.519 [Critical] V-116-16 nbpem terminating - failed to start nbproxyemailFlag:yes, nbproxy path: /usr/openv/netbackup/bin/nbproxy

Resolution:

It will be necessary to movethe zero byte *.ior files out of the way and let NetBackup recreate themwith the correct IOR information.

1. Stop the NetBackupdaemons:
#/usr/openv/netbackup/bin/goodies/netbackup stop

2. Move the /usr/openv/var/*.ior files out of the way, or simply delete them sincethey are zero bytes in size.  These files will be automatically recreatedwith the proper contents when NetBackup starts:
#cd /usr/openv/var
# mv nbproxy_jm.iornbproxy_jm.ior.old
# mvnbproxy_pem.ior nbproxy_pem.ior.old
#mv nbproxy_pem_email.ior nbproxy_pem_email.ior.old

3. Restartthe NetBackup daemons:
#/usr/openv/netbackup/bin/goodies/netbackup start

4. Run the bpps command and this should now listthe nbproxy , nbjm and nbpem daemons.
# /usr/openv/netbackup/bin/bpps-x