abundant amount of status 50 after MP4 install

[nathan_Schmidt]

Since we have installed MP4 on our master and 44 media servers, I see a large amount of status 50's popping. when searching the system event logs on the master server i see the following

The NetBackup Job Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.


The NetBackup Volume Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.


i suspect this is what is causing my jobs to peter out and would like to know if anyone else has seen these issues. I have the guys at datalink and veritas do the standard send us your logs and we will look at them but i am not getting any resolution...

any suggestions?

[nathan_Schmidt]

also this might be helpful-

when we installed 6.0 mp3 we had the issue that many others had that made it necessary to install

Windows:
nbpem.exe Install path/openv/netbackup/bin
nbjm.exe Install path/openv/netbackup/bin


supplied to us by veritas as a pre MP4 fix. by applying MP4 is see that the attributes on NBJM are still 6-30-2006

does anyone know if the NBJM supplied in MP4 has the same date?

[Dennis_Strom]

Not really a windows guy but I thought with Netbackup on Windows all previous hotfixes were supposed to be removed before doing an upgrade.

In-depth Troubleshooting Guide for Exit Status Code 50 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0
http://seer.support.veritas.com/docs/278503.htm

[Steve_Brach]

Ran into issue just like this with the status code 50's accompanied by status code 200's. Short term resolution was a hot fix of new binaries that are to be included in 6.0 MP5. Here are the bianries support had me replace with new one:

ISSUE: Parent - status 50 and 200 followed by a chain of hundreds of 200s
SOLUTION: NB_60_5_M.
TROUBLESHOOTING STEPS: Supplied EEB bundle containing solution for ET 860273 (status 50 and 200 followed by a chain of hundreds of 200s) on March 1.
File Name Destination cksum
---------- -------------- -----
(solaris)
nbpem /usr/openv/netbackup/bin 554378699
nbproxy /usr/openv/netbackup/bin 1694100249
nbproxyreq /usr/openv/netbackup/bin/admincmd 656492444
nbjm /usr/openv/netbackup/bin 2788220688
libnborb.so /usr/openv/lib 435738046
libnborbST.so /usr/openv/lib 93827828
libVcnbac.so /usr/openv/lib 3151698569
libVcnbacST.so /usr/openv/lib 2150479356

REFERENCE: defect ET 860844 6.0_MP5_Approved - Check if children are already running when a parent is to be started. If so, set due time to infinity. Recompute the due time when the child finishes.
PatchID 6.0_2550.

STATUS CODE: 50 200

[nathan_Schmidt]

thanks for the info... did the patches actaully take care of the 50's and 200's?

[Steve_Brach]

Yes, until last night when one client was experiencing the problem again. Im currently awaiting a call from support.

[nathan_Schmidt]

when searching throug the system event logs on your master server did you see anything like this?

The NetBackup Job Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

[nathan_Schmidt]

Ok we added

nbpem.exe \netbackup\bin\ 3486007163

nbproxy.exe \netbackup\bin\ 1282748167

nbproxyreq.exe \netbackup\bin\admincmd\ 1659948976

nbjm.exe \netbackup\bin\ 2988885938

libVcnbac.dll \netbackup\bin\ 945268661

libnborb.dll \netbackup\bin\ 3450950604

no problems last night but this morning i was running bpexpdate and nbjm crashed again and caused a couple of jobs to fail with 50 ....

what did support say when you applied that patches and still received a status 50?