Drives AVR mode: Manually UPping a robot

The process is fairly simple. I can also explain why robtest still works.

On a media server that has the robot and drives 'local' two processes run (for tld type robot).

tldd and tldcd

tldcd talks directly to the robot

tldd talks to tldcd to get things done, eg, mount / unmount.

If the media server cannot communicate with its local robot, it's drives will goto AVR.  Also, if tldd cannot talk to tldcd, drives will go AVR - not impossible but less likely as a casue as the processes run on the same box,.

For a media server that has a remote robot, but local drives only tldd will run.  This will talk with tldcd on the remote robot control host to get tapes mounted/ unmounted etc ...  If tldd cannot talk with tldcd due to say a network issue, then the drives will go AVR on the non- robot control host media server, but everything will be fine on the robot control host - hence why robtest will still work.

In your case, both media servers have robots, so both will have tldcd running, but ths process is only talking to the local robot.  tldd will talk with tldcd on the local and remote server as explained above.

So in this case, the most likely cause, based on what I know, is that there is some intermittant network issue where the two servers cannot talk with one another.  It could be a one-way issue, which would explain why the drives only go into AVR mode on one of the servers.

The most common reasons for drives in AVR mode :

RCH has lost connectivity to the robot

tldd cannot talk to tldcd

Config is wrong

If the confiog was wrong the drives would stay in AVR, so we can pretty much rule this out.