Check the ACSLS server's acsss_event.log. It should be in
/export/home/ACSSS/log/acsss_event.log, I believe. See if you're getting any
errors from the ACSLS server trying to communicate back to the NBU server.

Also log into the ACSLS server as the user acsss (or as root and su - to
acsss) and run cmd_proc. Do a "query server" to make sure the ACSLM is
online and ready to go. You can also leave this cmd_proc window up and then
try robtest from the Linux box and see if any errors show up in the upper
section of the cmd_proc window. Oh yeah, make sure to set the terminal to
vt100 or similar as cmd_proc is a curses-based interface.

It's probably a network communication thing between the ACSLS server and the
Linux box... The ACS API (which NBU and any other backup software will tie
into their robotic daemons) is all TCP/IP based.

B-

On 1/23/03 4:03 PM, "David A. Chapa" <david AT datastaff DOT com> wrote:

> I'm getting an ACS STATUS 72 when trying to enter robtest.
> 
> I configured my media server's "robot" as ACS, pointed it to the ACS/LS
> server, 
> everything seemed happy when I did that.
> 
> Then I configured one drive (9840), brought it up and the drive never went to
> ACS control, but stayed at AVR and robtest wouldn't come up but timed out with
> that 72 error from ACS.
> 
> ideas?
> 
> Thoughts?
> 
> David
> 
> PS...RedHat Linux 7.x, NBU 4.5MP3
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 

-- 
Brian Blake
Professional Services Organization
VERITAS Software
brian.blake AT veritas DOT com