--On Wednesday, March 03, 2004 15:05:55 -0500 Brian Cuttler [EMAIL PROTECTED] wrote:
Hello Amanda Users,
I'm running
IRIX 6.5.19
amanda 2.4.2p2
MTX 1.3.8
MTX itself seems to work correctly (see output below).
However I'm unable to get proper replies either from the
glue script nor from amanda (which one would expect with
a problem with the level underneath).
Perhaps I've selected the wrong glue script for this robot ?
samar 42% mtx -f /dev/scsi/sc1d4l0 inquiry
Product Type: Medium Changer
Vendor ID: 'BDT '
Product ID: 'ThinStor AutoLdr'
Revision: 'T16r'
Attached Changer API: No
samar 57% amtape samar eject
amtape: slot /usr/local/libexec/chg-zd-mtx[3]: not ejected: test: argument expected
samar 58% amtape samar device
test: argument expected
These error being explained (I think) by this output, which I do
not understand.
samar 60% /usr/local/libexec/chg-zd-mtx -eject
/usr/local/libexec/chg-zd-mtx[3]: test: argument expected
0 Drive was not loaded
Doubly odd since the only tape is loaded.
samar 61% /usr/local/libexec/chg-zd-mtx -info
/usr/local/libexec/chg-zd-mtx[15]: test: argument expected
8 1
According to the comments in chg-zd-mtx, there should be 3 or 4
numbers returned: current slot, number of slots, if it cam go backwards,
and optionally a 1 if you have a barcode reader.
The 'test: argument expected' error most likely means one of the
test statements in the script is trying to evaluate a null variable.
Does your changerfile for that config define all the necessary parameters?
Try working through all the commands in the section of comments at the
top of the script on testing your setup. Also check to see that the
shell listed on the first line uses a test compatible with the arguments
used in the script (some shells use a built-in test, others do a system
call to a standalone test program) and not all can test for all the same
things.
If you still can't find anything, try adding in an echo statement
before each test to print the argument variables and see which one(s) is
causing it to bomb.
Frank
You get the idea.
samar 55% mtx -f /dev/scsi/sc1d4l0 status
Storage Changer /dev/scsi/sc1d4l0:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded)
Storage Element 1:Empty
Storage Element 2:Empty
Storage Element 3:Empty
Storage Element 4:Empty
Storage Element 5:Empty
Storage Element 6:Empty
Storage Element 7:Empty
Storage Element 8:Empty
MTX inventory returns without any output, perhaps normal behaviour
if the other slots are empty (the users seem to have pillaged the tapes
performing their own archives - which is actually a welcome change).
thank you,
Brian
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
--
Frank Smith [EMAIL PROTECTED]
Sr. Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501