View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000980bareos-coredirectorpublic2018-07-09 09:042024-02-22 15:05
ReporterInt Assigned Tojoergs  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
PlatformLinuxOSCentOSOS Version7
Product Version17.2.4 
Summary0000980: release command not allowed in runscript makes admin job "ReleaseAllTapeDrives.conf" unusable
DescriptionIn Chapter "19.14 Tape Drive Cleaning" in Bareos documentation an admin job "ReleaseAllTapeDrives.conf" is given to release tapes if the tape libraries auto-cleaning won’t work when there are tapes in the drives.
But this job fails with error:
"Can't use release command in a runscript : release: is an invalid command."

It seems that at some point running release was forbidden, but this makes the example in Chapter "19.14 Tape Drive Cleaning" useless.
Please update the documentation with how to achieve tape release with currently allowed commands (or allow release command in a runscript again).
Steps To ReproduceImplement admin job "ReleaseAllTapeDrives.conf" as described in Bareos documentation Chapter "19.14 Tape Drive Cleaning"
TagsNo tags attached.

Activities

Int

Int

2018-12-29 09:26

reporter   ~0003164

Will this issue be fixed in bareos-18.2 release?
user1

user1

2019-01-16 09:32

reporter   ~0003179

I have the same issue, log files says:

/var/log/bareos/bareos.log- Volume Session Id: 144
/var/log/bareos/bareos.log- Volume Session Time: 1539591089
/var/log/bareos/bareos.log- Last Volume Bytes: 8,889,862,675,324 (8.889 TB)
/var/log/bareos/bareos.log- Termination: Backup OK
/var/log/bareos/bareos.log-
/var/log/bareos/bareos.log:19-Oct 09:03 bareos-dir JobId 4037: console command: run BeforeJob "release storage=QuantumSL3 alldrives"
/var/log/bareos/bareos.log:19-Oct 09:03 bareos-dir JobId 0: Can't use release command in a runscript19-Oct 09:03 bareos-dir JobId 0: release: is an invalid command.
/var/log/bareos/bareos.log-19-Oct 09:03 bareos-dir JobId 4037: Error: BAREOS 16.2.7 (09Oct17): 19-Oct-2018 09:03:15
/var/log/bareos/bareos.log- JobId: 4037
/var/log/bareos/bareos.log- Job: ReleaseAllTapeDrives.2018-10-19_09.03.12_00
/var/log/bareos/bareos.log- Scheduled time: 19-Oct-2018 09:03:09
/var/log/bareos/bareos.log- Start time: 19-Oct-2018 09:03:15

This is *really* annoying since my tape drive tries to clean itself and ofc it runs into an error since there is another tape loaded.
Int

Int

2019-12-13 13:38

reporter   ~0003667

one and a half years are over since this bug was reported and assigned - will this be fixed or not ?
Some feedback would be nice.
kinglui

kinglui

2020-02-10 09:28

reporter   ~0003756

Hi @all,

any news? I run into the same problem.

greets
bruno-at-bareos

bruno-at-bareos

2024-02-22 15:05

manager   ~0005801

Actual documentation and Code work correctly

Job {
    Name = ReleaseAllTapeDrives
    JobDefs = DefaultJob
    Schedule = "WeeklyCycleAfterBackup"
    Type = Admin
    Priority = 200

    RunScript {
        Runs When = Before
        Runs On Client = no
        Console = "release storage=Tape alldrives"
    }
}

22-Feb 15:03 yoda-dir JobId 15509: console command: run BeforeJob "release storage=autochanger-0 alldrives"
22-Feb 15:03 yoda-dir JobId 0: Connecting to Storage daemon autochanger-0 at bareos-quadstore:9103 ...
22-Feb 15:03 yoda-dir JobId 0: 3307 Issuing autochanger "unload slot 4, drive 0" command.
22-Feb 15:03 yoda-dir JobId 0: 3921 Device ""tapedrive-0" (/dev/nst0)" already released.
22-Feb 15:03 yoda-dir JobId 0: Connecting to Storage daemon autochanger-0 at bareos-quadstore:9103 ...
22-Feb 15:03 yoda-dir JobId 0: 3921 Device ""tapedrive-1" (/dev/nst1)" already released.
22-Feb 15:03 yoda-dir JobId 15509: Start Admin JobId 15509, Job=cleanalltapes.2024-02-22_15.03.47_04
22-Feb 15:03 yoda-dir JobId 15509: BAREOS 23.0.1 (17Jan24): 22-Feb-2024 15:03:49
  JobId: 15509
  Job: cleanalltapes.2024-02-22_15.03.47_04
  Scheduled time: 22-Feb-2024 15:03:45
  Start time: 22-Feb-2024 15:03:49
  End time: 22-Feb-2024 15:03:49
  Bareos binary info: Bareos subscription release
  Job triggered by: User
  Termination: Admin OK

Issue History

Date Modified Username Field Change
2018-07-09 09:04 Int New Issue
2018-07-09 13:06 joergs Assigned To => joergs
2018-07-09 13:06 joergs Status new => assigned
2018-12-29 09:26 Int Note Added: 0003164
2019-01-16 09:32 user1 Note Added: 0003179
2019-12-13 13:38 Int Note Added: 0003667
2020-02-10 09:28 kinglui Note Added: 0003756
2020-07-06 09:36 Int Issue cloned: 0001258
2024-02-22 15:05 bruno-at-bareos Status assigned => closed
2024-02-22 15:05 bruno-at-bareos Resolution open => fixed
2024-02-22 15:05 bruno-at-bareos Note Added: 0005801