Hello,

On 1/11/2006 5:30 PM, Ralf Gross wrote:
Hi,

I tried to configure bacula to use our Qualstart TLS-4120 AIT-2
autochanger on a debian sarge system with bacula 1.36.3.

To get the mtx-changer script to work, I enabled the following line:

mt -f $device offline

... mtx-changer seems to work, and I don't see anything special in the configuration...

I've try to get the status of the the automounter I get this:

*status
The defined Storage resources are:
     1: File
     2: Autochanger
Select Storage resource (1-2): 2
Connecting to Storage daemon Autochanger at epefp119:9103

epefp119-sd Version: 1.36.3 (22 April 2005) i386-pc-linux-gnu debian 3.1
Daemon started 11-Jan-06 17:17, 0 Jobs run since started.

Running Jobs:
No Jobs running.
====

Terminated Jobs:
 JobId  Level   Files          Bytes Status   Finished        Name
======================================================================
   345  Full          0              0 Other    20-Dec-05 06:37 C59SN021
   315  Diff          0              0 Error    25-Dec-05 13:08 Client1
   349  Incr          0              0 Other    25-Dec-05 13:38 C59SN021
   316  Diff          0              0 Error    30-Dec-05 20:08 C59VRSBB
   353  Incr          0              0 Other    30-Dec-05 20:38 C59SN021
   319  Incr          0              0 Error    05-Jan-06 03:08 Client1
   357  Incr          0              0 Other    05-Jan-06 03:38 C59SN021
   320  Incr          0              0 Error    10-Jan-06 10:08 C59VRSBB
   361  Incr          0              0 Other    10-Jan-06 10:38 C59SN021
   751  Incr          0              0 Cancel   11-Jan-06 12:52 C59VRSBB
====

Device status:
Archive "FileStorage" is not open or does not exist.
Archive "Autochanger" is not open or does not exist.


I think this is not what I should see at this point.

Hmm. I'm never really sure about this. The "is not open or does not exist" is not always something to worry about.

BUT what did btape say when you tested your autochanger? I'm sure you didn't skip that step since it's so prominently mentioned in the manual, right? ;-)

*label
The defined Storage resources are:
     1: File
     2: Autochanger
Select Storage resource (1-2): 2
Enter new Volume name: Test2
Enter slot (0 for none): 2
Automatically selected Pool: Default
Connecting to Storage daemon Autochanger at epefp119:9103 ...
Sending label command for Volume "Test2" Slot 2 ...
3301 Issuing autochanger "loaded drive 0" command.
3991 Bad autochanger "loaded drive 0" command: ERR=Child exited with
code 1.

Code 1... no permissions, I suspect.
Verify under which user account the SD runs. Compare with the permissions for /dev/sg3 and /dev/st0

3304 Issuing autochanger "load slot 2, drive 0" command.
3992 Bad autochanger "load slot 2, drive 0": ERR=Child exited with code 1.
Label command failed for Volume Test2.
Do not forget to mount the drive!!!


Any ideas?

Yes, you tested as root, and the SD runs as user bacula:bacula, I think.

Arno

Ralf


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to