This issue has been resolved.  The problem was a network issue.  A 
configuration that was changed on one of the switches without someone checking. 
 Oh well...

Thanks for the help Justin!

-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com] 
Sent: Thursday, June 18, 2009 2:11 PM
To: Baumann, Kevin
Cc: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] bpadm error



On Thu, 18 Jun 2009, Baumann, Kevin wrote:

>
>> What happens if you run:
>
>> $ /usr/openv/netbackup/bin/admincmd/bppolicynew test
>> $
>
> # /usr/openv/netbackup/bin/admincmd/bppolicynew test
> cannot connect on socket
>
>> Is your master working?
>> bpps -a output?
>
> # bpps -a
> NB Processes
> ------------
> /usr/openv/netbackup/bin/nbsl
> /usr/openv/netbackup/bin/bpdbm
> /usr/openv/netbackup/bin/nbstserv
> /usr/openv/netbackup/bin/nbsvcmon
> /usr/openv/netbackup/bin/bpcompatd
> /usr/openv/netbackup/bin/nbrmms
>
> MM Processes
> ------------
> /usr/openv/volmgr/bin/ltid
> vmd
>
> Forgot to mention this is on Solaris 10, 6.5.3 master server.
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>

> # /usr/openv/netbackup/bin/admincmd/bppolicynew test
> cannot connect on socket

Something seems wrong here, check jnbSA/make sure all the appropriate 
processes are active- I normally see that when one of the processes down 
or a service died, or xinetd/inetd is not started.

If you can, try to cycle services (bp.kill_all) & netbackup start (if 
possible).

If all else fails, check all of the logs in usr/openv/netbackup/logs/* for 
today's date and there you should find the problem :)

Justin.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu