Troubleshooting nbar

[Marco_Barragan]

Hi all,

I have a little problem.... again, I have rebooted my netbackup server and now i cannot access the advanced reporter web site... I have searched for the proccess that use nbar, like vnetd and the sql database and they are up and working, but the port 8885 of the nbar is not running, i even tried changing the port to 8880 but still, the nbar is not up...

Can anyone give me some ideas how to solve this problem or maybe some link or documentation about nbar cause i couldn't find much about it...

Thanks a lot.

[Stumpr2]

VERITAS NetBackup (tm) 5.1 Advanced Reporter System Administrator's Guide for UNIX and Windows
http://support.veritas.com/docs/268189

You do know that it was eol at Netbackup 5.1?

[Chia_Tan_Beng]

Marco,

Is your master a Unix or Windows box?

If on Unix, do a "bpps -a" and you should have the following processes running:

ARO Processes
-------------
/usr/openv/nbar/bin/ardbd --no-defaults --set-variable connect_
/bin/sh /usr/openv/nbar/bin/ardbmon
/usr/openv/nbar/bin/armonitor
/usr/openv/java/jre/bin/PA_RISC2.0/java -Djava.endorsed.dirs=/u


You can also try re-cycling the NBAR daemon at master server without rebooting the server:
/usr/openv/nbar/bin/nbar stop
/usr/openv/nbar/bin/nbar start

[Marco_Barragan]

Sorry i couldn't write back, this past week was really crazy at work.

Now i am back with the nbar problem... My netbackup server is a Unix server, i have checked the logs and it says it can't connect to the database, though the databse is up. After i use a netstat to check on the ports on listening, the database port is up, i think is the 3336 tcp port.

For some reason the 8885 nbar http port doesn't run. Any ideas?

[Marco_Barragan]

ok, i run the bpps and got this putput:

ARO processes
-------------------------
/opt/VRTSnbaro/bin/ardbd --no-defaults --set-variable connect_timeout=30 --user
/bin/sh /opt/VRTSnbaro/bin/ardbmon

How do i get the other two processes to run?

[Stumpr2]

did you do as Chia suggested and run
nbar stop
nbar start

[Marco_Barragan]

Yes.

I already fixed it, it seems when the server whent down not all the processess where correctly killed and the database that nbar uses was corrupt. there is a script to check the database:

/opt/VRTSnbaro/bin/goodies/table_check.sh

options check and repair, to fix the database the nbar uses.

Thanx anyway for the help.