While testing something, I ran into this (director version 5.2.5, Ubuntu 12.04, client is an Ubuntu 14.04 running
fd version 5.2.6).
Shouldn’t “Fail job on error = No” have made it continue regardless of the error?
RunScript {
Command = "/etc/bacula/scripts/pre_backup.sh %l"
Runs on Client = Yes
Runs When = Before
Runs On Success = Yes
Runs On Failure = Yes
Fail job on error = No
}
I had a syntax error in the script, and got this in the log:
2015-02-27 14:48:05
git-luc-fd JobId 26973: Error:
Runscript: ClientRunBeforeJob returned non-zero status=2. ERR=Child exited with code 2
2015-02-27 14:48:05
bacula-dir JobId 26973: Fatal error: Bad response to
ClientRunBeforeJob command: wanted 2000 OK
RunBefore
, got 2905 Bad
RunBeforeJob command.
2015-02-27 14:48:05
bacula-dir JobId 26973: Fatal error: Client "git-luc-fd"
RunScript failed.
[...]
Start time:
27-Feb-2015 14:48:04
End time: 27-Feb-2015 14:48:05
Elapsed time: 1 sec
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s