baros turns to drive 65535 and doesn't turn to drive 0

[Сергей Михайлович Супотницкий]

I have an ubuntu 18 lts operating system. Connected to it (via fiber channel) HP MSL2024 tape drive
Now stands bareos 19.2.6

After updating bareos from version 18, I ran into such a problem. Backup jobs stopped running

Here is the error log

-Mar 19: 00:10 bareos-dir JobId 230: Start Backup JobId 230, Job = backup_lenta_sed_monthly.2020-03-19_00.00.01_00
19-Mar 00:10 bareos-dir JobId 230: Connected Storage daemon at bareos.vipmed.local: 9103, encryption: TLS_CHACHA20_POLY1305_SHA256
19-Mar 00:10 bareos-dir JobId 230: Using Device "MSL2024" to write.
19-Mar 00:10 bareos-dir JobId 230: Connected Client: sed at sed.vipmed.local: 9102, encryption: None
19-Mar 00:10 bareos-dir JobId 230: Handshake: Cleartext
Mar 19 00:10 bareos-dir JobId 230: Encryption: None
19-Mar 00:10 sed JobId 230: Created 24 wildcard excludes from FilesNotToBackup Registry key
Mar 19 00:10 AM sed JobId 230: Warning: XATTR support requested in fileset but not available on this platform. Disabling ...
19-Mar 00:10 bareos-sd JobId 230: 3304 Issuing autochanger "load slot 2, drive 65535" command.
Mar 19 00:15 bareos-sd JobId 230: Fatal error: 3992 Bad autochanger "load slot 2, drive 65535": ERR = Child died from signal 15: Termination.
Results = Program killed by BAREOS (timeout)

Mar 19 00:15 sed JobId 230: Fatal error: filed / dir_cmd.c: 2641 Bad response to Append Data command. Wanted 3000 OK data
, got 3903 Error append data

 
 

 
 The most important mistake is here.
 
 3304 Issuing autochanger "load slot 2, drive 65535" command.
 
 and I don’t know how to solve it, because before there was a call to drive 0 and everything worked and now (after the update) I see that the baros is turning to drive 65535. I don’t have such a drive and therefore bareos can’t write anything to the tape.
 
 Tell me - how to fix it - i.e. to make bareos access drive 0 and not drive 65535
 

[Sascha Bejer]

Hi,

I can report the same issue on Debian Buster after upgrade to 19.2.6 with the MSL2024, and have not found the cause yet.

MTX Log shows below change after the upgrade:

202003xx-11:31:17 Parms: /dev/tape/by-id/scsi-3500e09efff10c796 listall 0 /dev/tape/by-id/scsi-35005076312158754-nst 0
202003xx-13:24:23 Parms: /dev/tape/by-id/scsi-3500e09efff10c796 listall 0 /dev/tape/by-id/scsi-35005076312158754-nst 65535

Any advice would be welcomed.

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/b786580b-cd4d-4089-823e-08d1b12fdfb4%40googlegroups.com.

.

[Сергей Михайлович Супотницкий]

Here are some other errors I found

ls  /var/lib/bareos/

bareos.2181.traceback     mtx.err.2X7pvLAiRG        mtx.err.BnTTqWeJJq        mtx.err.ilMsZP5oW5        mtx.err.npFTtHZZXo        mtx.err.WB1LJ3y59O
bareos-dir.2181.bactrace  mtx.err.3c0gXo4Fyl        mtx.err.CfOKvwZk71        mtx.err.JE3Zwrjh96        mtx.err.OeeV8UqCzB        mtx.err.WnULBeG9ys
bareos-dir.9101.pid       mtx.err.4OgcrcpoDs        mtx.err.djC8p4vWXh        mtx.err.jGwfZHi5uK        mtx.err.onkaRFXiTf        mtx.err.WpPhSFJKHO
bareos-dir.9101.state     mtx.err.4voLBJ6cYe        mtx.err.Ej1oral9Lp        mtx.err.Jxj3kU3PlD        mtx.err.P5wKV9JoH8        mtx.err.Wu0CVw0Mhv
bareos-dir.conmsg         mtx.err.5nlyYIGeYN        mtx.err.ENkeHpQ7ZF        mtx.err.KqhcZDgaSu        mtx.err.P6fomUNw0V        mtx.err.xI64sbx2ue
bareos-fd.9102.pid        mtx.err.63iivQ3fdJ        mtx.err.Eut26qTnmq        mtx.err.kxwXJd0uwj        mtx.err.Pa0KSfd3lB        mtx.err.XL9s4BAHaD
bareos-sd.9103.pid        mtx.err.6dP2VftIiz        mtx.err.euYLFytenu        mtx.err.l0v7KJTYP2        mtx.err.PqFchMJ5oB        mtx.err.XyvlWK0MU5
bareos-sd.9103.state      mtx.err.6G6Bfj0AOV        mtx.err.eVkTiFAwVa        mtx.err.mMJfaGswKl        mtx.err.PRW3eaRGAj        mtx.err.Y4vJZf8Wlw
mtx.err.07QKFODEU1        mtx.err.6trnwmw8o9        mtx.err.Fyqh0cF9bC        mtx.err.mmNpf4DwCc        mtx.err.R9Tuiwh47b        mtx.err.yhZaPv8cLG
mtx.err.0aOfzKFwyq        mtx.err.7YMO1uwV2N        mtx.err.gbXwIQH2tc        mtx.err.Mq9IB6YYNC        mtx.err.rixAWbfqlx        mtx.err.ZggqUv9x4E
mtx.err.0oaB4yAIgu        mtx.err.aQpq4B8g1c        mtx.err.GeQe6Lgo9E        mtx.err.mQTSu6ZhvW        mtx.err.Rl4RS7q28t        mtx.err.ZvgnJdwxxT
mtx.err.0stx7PLiyP        mtx.err.arGzGOEjTZ        mtx.err.hCzAaa7PxB        mtx.err.MvQtB4EVxY        mtx.err.SCEslYKZDY        mtx.err.zvULweo4cs
mtx.err.0UdoqoVOw3        mtx.err.BAruu1FgUJ        mtx.err.HJxPrzjEzh        mtx.err.n7uTPLsJOf        mtx.err.tJCAKUnM1S        storage/
mtx.err.2vfPzNUgbd        mtx.err.BMtM4eA8Oz        mtx.err.hrIUeGVesL        mtx.err.Na2dfvIzBj        mtx.err.Tm44Stzg9X        

 

cat /var/lib/bareos/mtx.err.n7uTPLsJOf

illegal <drive-number> argument '65535' to 'load' command

вторник, 24 марта 2020 г., 13:30:58 UTC+3 пользователь sascha.bejer написал:

To unsubscribe from this group and stop receiving emails from it, send an email to bareos...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/b786580b-cd4d-4089-823e-08d1b12fdfb4%40googlegroups.com.

.

[the...@gmx.de]

Hello Sascha,

i can also confirm the error on an Debian 8.11 System with a Dell PowerVault 124 (LT04) tape roboter.
I did an update from Bareos 16.2 to 19.2.6 and experienced the 65535 drive error too.

Fortunately i found a workaround but not a real solution. But for now my tape backup is at least
working again. The workaround is possible for me because the tape roboter drive (drive 0) is my
one and only drive.

I only changed the variable for the drive in the configuration file. In my case its the file:

/etc/bareos/bareos-sd.d/autochanger/PowerVault124t.conf

Here is the content:

Autochanger {
  Name = PowerVault124t
  Changer Device = /dev/sg3
  Device = LTO-4
#  Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
  Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a 0"
}

As you can see i commented out the old line with the parameter %d just to the literal "0" and my
tape backup is back on the road again.

Nevertheless i would appreciate very much a real solution for our problem and not just a quick an dirty
hack.

Thanks a lot in advance to a real Bareos Developer or Expert for a good solution to our problem.

Have a nice and sane time and i wish all the best,

Thomas Erich

Am 24.03.20 um 11:30 schrieb Sascha Bejer:

. --

You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/2f6ee386-826b-644a-2ed7-d7ff805db812%40access-company.com.

[Сергей Михайлович Супотницкий]

Thomas , Thank you so much. Your advice helped

вторник, 24 марта 2020 г., 14:27:04 UTC+3 пользователь theo378 написал:

To unsubscribe from this group and stop receiving emails from it, send an email to bareos...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/b786580b-cd4d-4089-823e-08d1b12fdfb4%40googlegroups.com.

. --
You received this message because you are subscribed to the Google Groups "bareos-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bareos...@googlegroups.com.

[Frank Bergkemper]

I tried to reproduce the reported issue without success, yet.

How does your configuration look like in detail? Providing the following
configurations files could help to understand the problem better.

/etc/bareos/bareos-dir.d/storage/tapelib.conf
/etc/bareos/bareos-sd.d/autochanger/autochanger-*.conf
/etc/bareos/bareos-sd.d/device/tapedrive-*.conf

Thanks & regards,
Frank

--
Frank Bergkemper frank.be...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-630693-94
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz

[Sascha Bejer]

Hi Frank,

Below config with a Quantum Superloader 3:

/etc/bareos/bareos-dir.d/storage/Tape.conf

Storage {
  Name = Tape
  Address  = xxx
  Password = "xxx"
  Device = autochanger
  Media Type = LTO
  Auto Changer = yes
  Collect Statistics = yes
  Maximum Concurrent Jobs = 10
}

/etc/bareos/bareos-sd.d/autochanger/autochanger.conf

Autochanger {
  Name = "autochanger"
  Changer Device = /dev/tape/by-id/scsi-xxx
  Device = tapedrive

#  Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
  Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a

0"  # Workarround for Drive 65535 issue
}

/etc/bareos/bareos-sd.d/device/tapedrive.conf

Device {

    Name = "tapedrive"
    DeviceType = tape

    # default:0, only required if the autoloader have multiple drives.
    # DriveIndex = 0

    ArchiveDevice = /dev/tape/by-id/scsi-xxx
    MediaType = LTO

    AutoChanger = yes
    AutomaticMount = yes
    MaximumFileSize = 10GB
    Minimum block size = 524288
    Maximum block size = 524288

    Spool Directory = /spool
    Maximum Spool Size = 6000GB
    Maximum Concurrent Jobs = 10
    Removable Media = yes
    Collect Statistics = yes
}

Br, Sascha

On 02.04.20 13:46, Frank Bergkemper wrote:
> I tried to reproduce the reported issue without success, yet.
>
> How does your configuration look like in detail? Providing the following
> configurations files could help to understand the problem better.
>
> /etc/bareos/bareos-dir.d/storage/tapelib.conf
> /etc/bareos/bareos-sd.d/autochanger/autochanger-*.conf
> /etc/bareos/bareos-sd.d/device/tapedrive-*.conf
>
> Thanks & regards,
> Frank
>

--

.

[Frank Bergkemper]

Thanks a lot, that was the right hint.



02-Apr 14:29 bareos-sd JobId 14: 3304 Issuing autochanger "load slot 1,
drive 65535" command.
02-Apr 14:29 bareos-sd JobId 14: Fatal error: 3992 Bad autochanger "load
slot 1, drive 65535": ERR=Child exited with code 1.



For some reason the default value of the DriveIndex is not applied and
set to 0, instead it has the maximum value.

Going to investigate further next to find the root cause here.

However, if you set the DriveIndex explicitly in your Device Resource
it works fine.


02-Apr 14:32 bareos-sd JobId 15: 3304 Issuing autochanger "load slot 1,
drive 0" command.
02-Apr 14:32 bareos-sd JobId 15: 3305 Autochanger "load slot 1, drive
0", status is OK.


As a workaround set the DriveIndex in your Device Resource explicitly
until we fixed this.

# default:0, only required if the autoloader have multiple drives.

DriveIndex = 0

Thanks & regards,
Frank

--

[Frank Bergkemper]

Bug report created, see https://bugs.bareos.org/view.php?id=1220 .

Regards,