View Issue Details

IDProjectCategoryView StatusLast Update
0001258bareos-core[All Projects] directorpublic2020-07-06 09:36
ReporterIntAssigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version19.2.7 
Fixed in Version 
Summary0001258: release command not allowed in runscript makes admin job "ReleaseAllTapeDrives.conf" unusable
DescriptionIn Chapter "Tape Drive Cleaning" : https://docs.bareos.org/TasksAndConcepts/AutochangerSupport.html?highlight=releasealltapedrives conf#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 "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 "Tape Drive Cleaning": https://docs.bareos.org/TasksAndConcepts/AutochangerSupport.html?highlight=releasealltapedrives conf#tape-drive-cleaning
Additional InformationThis issue exists at least since version 17.2 - I am bringing this back to your attention by cloning the original issue.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

Int

Int

2020-07-06 09:36

reporter   ~0004021

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

user1

2020-07-06 09:36

reporter   ~0004022

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

2020-07-06 09:36

reporter   ~0004023

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-07-06 09:36

reporter   ~0004024

Hi @all,

any news? I run into the same problem.

greets

Issue History

Date Modified Username Field Change
2020-07-06 09:36 Int New Issue
2020-07-06 09:36 Int Issue generated from: 0000980
2020-07-06 09:36 Int Note Added: 0004021
2020-07-06 09:36 Int Note Added: 0004022
2020-07-06 09:36 Int Note Added: 0004023
2020-07-06 09:36 Int Note Added: 0004024