Hello,
I´m trying to run a console command from an admin job and this is crashing my director. A simple Console = "list jobs", inside a RunScript directive, crashes the director (bacula-dir dead but subsys locked) and it generates a "Bacula GDB traceback of bacula-dir on myDirector" mail.
Below is my Admin Job with a "list jobs" console command. My goal is a "list nextvol job=\"my\job\" days=1" command. Tried "list jobs", "list clients", and so on, all of them result in the same. When it runs on client side this does not happen. When I enter bconsole after restarting bacula, I get the messages:
17-Apr 17:24 myDirector-dir JobId 17821: console command: run BeforeJob "list jobs"
17-Apr 17:24 myDirector-dir JobId 0: Automatically selected Catalog: MyCatalog
17-Apr 17:24 myDirector-dir JobId 0: Using Catalog "MyCatalog"
Job {
Name = "NextVolume"
Type = Admin
Client = myclient-fd
FileSet = "NextVolumeFileSet"
Storage = "mystorage-sd"
Messages = Standard
Max Start Delay = 0
Max Run Sched Time = 12 hours
Pool = Scratch
Priority = 30
Schedule = "NextVolumeCycle"
RunScript {
RunsWhen = Before
RunsOnClient = no
Fail Job on Error = no
Console = "list jobs"
}
}
########################################################
#
# FileSet for Job NextVolume
#
########################################################
FileSet {
Name = "NextVolumeFileSet"
Include {
Options {
signature = MD5
}
}
}
Thank you!
Ana
