Hi,
28.08.2007 18:51,, Richard White wrote::
> Bacula 2.2.0 on SLES 10. Ecrix 1x10 autoloader.
>
> When I originally set this up, it labeled barcodes flawlessly. Now
> I get this error:
>
> *label barcodes . . . Sending Label command for volume "B0000001"
> Slot 1 ... 3307 Issuing autochanger "unload slot 8, drive 0"
> command. 3304 Issuing autochanger "load slot 1, drive 0" command.
> 3305 Autochanger "load slot 1, drive 0", status is OK. 3301 Issuing
> autchanger "loaded? drive 0" command. 3302 Autochanger "loaded?
> drive 0" result is Slot 1. 3910 Unable to open device "VXA3"
> (/dev/nst0): ERR=dev.c:425 Unable to open device "VXA3"
> (/dev/nst0): ERR=Input/output error
>
> Label command failed for Volume B0000001
>
> Here are the pertinent sections of bacula-sd.conf:
>
> # Autochanger resource Autochanger { Name = "Auto" Device = VXA3
> Changer Device = /dev/sg1 Changer Command =
> "/bacula/bin/mtx-changer %c %o %S %q %d" }
>
> # Internal VXA-3 Drive #
>
> Device { Name = VXA3 Drive Index = 0 Autochanger = yes Media Type =
> VXA-3 Archive Device = /dev/nst0 AutomaticMount = yes;
> # when device opened, read it AlwaysOpen = yes; LabelMedia = Yes
> RemovableMedia = yes; RandomAccess = no; }
>
>
> and bacula-dir.conf:
>
> Storage { Name = Auto Address = 10.1.0.17 SDPort = 9103 Password =
> "ourpassword" Device = "Auto" Media Type = VXA-3
Here, you should also set "Autochanger = Yes"
> }
>
> #Storage { # Name = VXA # Address = 10.1.0.17 # SDPort = 9103 #
> Password = "ourpassword" # Device = "VXA3" # Media Type = "VXA-3"
> # Maximum Concurrent Jobs = 5 #}
>
>
> Please note that I have run this without the comments as well, but
> the result is the same. Is there a log file I can examine that
> might shed some light on this?
It is possible to create logs inside mtx-changer. Just add lines to
output possibly relevant information to a file.
Typically, at the start of mtx-changer, I'd do something like
echo `date` >> /var/log/mtx-changer.log
echo "called with $@" >> /var/log/mtx-changer.log
and later add return codes from the actual autochanger operations.
What you need depends on the problem, of course, so you might find
yourself adding more and more output lines over time...
A trace of the SD operations can be created by issuing a command like
'setdebug level=200 trace=1 storage=Auto' in bconsole. In the SD'S
working directory, a <SD-name>.trace file be created containing lots
of details of the internal operations.
Note that the debug level you need is unknown to me, i.e. I didn't
look up at which level the SD logs tape and autochanger operations at
sufficient detail. The "200" above was just an example - I usually use
400 and get lots and lots of stuff.
Arno
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
