Hi there
@bill arlofski I installed the latest version of the
MTX-Changer-python-script and now it seems as I cannot do any backup
anymore.
The errormessages are however incomprehensible:
->->->
08-Jun 06:14 -dir JobId 785: Start Backup JobId 785,
Job=FileServer_Full.2024-06-07_23.05.00_04
08-Jun 06:14 -dir JobId 785: Using Device "LTO9-1" to write.
08-Jun 06:14 -sd JobId 785: Spooling data ...
08-Jun 07:35 -sd JobId 785: User specified Job spool size reached:
JobSpoolSize=1,000,000,233,561 MaxJobSpoolSize=1,000,000,000,000
08-Jun 07:35 -sd JobId 785: Writing spooled data to Volume. Despooling
1,000,000,233,561 bytes ...
08-Jun 08:08 -sd JobId 785: Despooling elapsed time = 00:32:55, Transfer rate =
506.3 M Bytes/second
08-Jun 08:08 -sd JobId 785: Spooling data again ...
08-Jun 09:17 -sd JobId 785: User specified Job spool size reached:
JobSpoolSize=1,000,000,233,456 MaxJobSpoolSize=1,000,000,000,000
08-Jun 09:17 -sd JobId 785: Writing spooled data to Volume. Despooling
1,000,000,233,456 bytes ...
08-Jun 09:52 -sd JobId 785: Despooling elapsed time = 00:35:02, Transfer rate =
475.7 M Bytes/second
08-Jun 09:52 -sd JobId 785: Spooling data again ...
08-Jun 10:52 -sd JobId 785: User specified Job spool size reached:
JobSpoolSize=1,000,000,236,145 MaxJobSpoolSize=1,000,000,000,000
08-Jun 10:52 -sd JobId 785: Writing spooled data to Volume. Despooling
1,000,000,236,145 bytes ...
08-Jun 11:40 -sd JobId 785: Despooling elapsed time = 00:47:02, Transfer rate =
354.3 M Bytes/second
08-Jun 11:40 -sd JobId 785: Spooling data again ...
08-Jun 12:46 -sd JobId 785: User specified Job spool size reached:
JobSpoolSize=1,000,000,238,584 MaxJobSpoolSize=1,000,000,000,000
08-Jun 12:46 -sd JobId 785: Writing spooled data to Volume. Despooling
1,000,000,238,584 bytes ...
08-Jun 12:57 -sd JobId 785: [SI0202] End of Volume "000005L9" at 365:31284 on device
"LTO9-1" (/dev/nst0). Write of 1048576 bytes got -1.
08-Jun 12:57 -sd JobId 785: Re-read of last block succeeded.
08-Jun 12:57 -sd JobId 785: End of medium on Volume "000005L9"
Bytes=19,347,105,154,048 Blocks=14,628,112 at 08-Jun-2024 12:57.
08-Jun 12:57 -sd JobId 785: 3307 Issuing autochanger "unload Volume 000005L9, Slot
6, Drive 0" command.
08-Jun 13:00 -sd JobId 785: 3995 Bad autochanger "unload Volume 000005L9, Slot 6,
Drive 0": ERR=Child exited with code 1
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -dir JobId 785: There are no more Jobs associated with Volume
"000008L9". Marking it purged.
08-Jun 13:00 -dir JobId 785: All records pruned from Volume "000008L9"; marking it
"Purged"
08-Jun 13:00 -dir JobId 785: Recycled volume "000008L9"
08-Jun 13:00 -sd JobId 785: 3991 Bad autochanger "loaded? drive 0" command:
ERR=Child exited with code 1.
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -sd JobId 785: 3991 Bad autochanger "loaded? drive 0" command:
ERR=Child exited with code 1.
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -sd JobId 785: 3991 Bad autochanger "loaded? drive 0" command:
ERR=Child exited with code 1.
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -sd JobId 785: 3991 Bad autochanger "loaded? drive 0" command:
ERR=Child exited with code 1.
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -sd JobId 785: 3304 Issuing autochanger "load Volume 000008L9, Slot 7,
Drive 0" command.
08-Jun 13:00 -sd JobId 785: Fatal error: 3992 Bad autochanger "load Volume 000008L9
Slot 7, Drive 0": ERR=Child exited with code 1.
Results=Usage:
mtx-changer-python.py [-c <config>] [-s <section>] [-i <jobid>] [-j <jobname>] <chgr_device>
<mtx_cmd> <slot> <drive_device> <drive_index>
mtx-changer-python.py -h | --help
mtx-changer-python.py -v | --version
08-Jun 13:00 -sd JobId 785: Despooling elapsed time = 00:13:48, Transfer rate =
1.207 G Bytes/second
08-Jun 13:00 -sd JobId 785: Elapsed time=06:46:15, Transfer rate=164.0 M
Bytes/second
08-Jun 13:00 -fd JobId 785: Error: bsock.c:395 Wrote 65210 bytes to Storage
daemon:server06.brace.de:9103, but only 32768 accepted.
08-Jun 13:00 -fd JobId 785: Fatal error: backup.c:911 Network send error to SD.
ERR=Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
08-Jun 13:00 -fd JobId 785: Error: bsock.c:275 Socket has errors=1 on call to
Storage daemon:server06.brace.de:9103
08-Jun 13:00 -dir JobId 785: Error: Bacula -dir 11.0.6 (10Mar22):
<-<-<-
The mtx-changer-python.log stops at June 5th and does not even show the June
8th messages.
It looks for me as the new script cannot interprete the changer commands?
If I copy back the older version of the changer script I get the those messages:
->->->
09-Jun 08:04 -sd JobId 790: 3995 Bad autochanger "unload Volume
*Unknown*, Slot 6, Drive 0": ERR=Child exited with code 1
Results=Traceback (most recent call last): File
"/usr/libexec/bacula/mtx-changer-python.py", line 968, in <module>
result = do_unload() ^^^^^^^^^^^ File
"/usr/libexec/bacula/mtx-changer-python.py", line 792, in do_unload
checkdrive = do_checkdrive() ^^^^^^^^^^^^^^^ File
"/usr/libexec/bacula/mtx-changer-python.py", line 647, in do_checkdrive
cmd = tapeinfo_bin + ' -f ' + sg ~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: can only concatenate str (not "NoneType") to str 09-Jun 08:04
-sd JobId 790: Warning: mount.c:216 Open of Tape device "LTO9-1"
(/dev/nst0) Volume "000008L9" failed: ERR=tape_dev.c:169 Unable to open
device "LTO9-1" (/dev/nst0): ERR=Kein Medium gefunden <-<-<- I switched
then again to latest version of the mtx-changer-python.py script, it
seems to change the tape again. I am pretty sure that problem might
rather be related to the scrip that to the tape library. I could not
even backup the catalogue (5 failed backups). Any idea? Cheers TB
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
