Hi,
I'm using Bacula version 9.4.2 on Debian 9.8. This server is a virtual
machine on KVM hypervisor.
My Bacula Server was worked properly until yesterday, but now it has
problems of locking of jobs, as the follow:
Running Jobs:
Console connected at 10-abr-19 17:09
Console connected at 10-abr-1
On 4/10/19 12:35 PM, David Brodbeck wrote:
I'm having trouble getting virtual full backups working. I feel like I'm
missing something basic about how they're supposed to be structured, but I
could use help figuring out what it is.
It's also possible I misunderstand the error message -- will it
I'm having trouble getting virtual full backups working. I feel like I'm
missing something basic about how they're supposed to be structured, but I
could use help figuring out what it is.
It's also possible I misunderstand the error message -- will it error out
if there aren't 30 jobs to consolida
The difference might be something in the process's environment. Try printing
the environment using /bin/env in the script to compare between the post job
and other cases.
You could also try using Bacula's bsmtp utility (or /bin/mail) instead of
mutt.
__Martin
> On Wed, 10 Apr 2019 11:46:04
Thanks Martin, it behaved just as you said.
What I'm trying to troubleshoot is a post job script failing:
09-Apr 22:38 bacula_dir JobId 48848: AfterJob: /sent: Permission denied
(errno = 13)
09-Apr 22:38 bacula_dir JobId 48848: AfterJob: Could not send the message.
It was running fine for mon
> On Wed, 10 Apr 2019 09:48:59 +0100, Adam Weremczuk said:
>
> Hi all,
>
> I'm running old Bacula 5.2.6 with LTO-4 tapes and trying to add a test
> job that will execute a script from the director:
>
> RunScript {
> RunsWhen = after
> RunsOnClient = no
> Runs
Hi all,
I'm running old Bacula 5.2.6 with LTO-4 tapes and trying to add a test
job that will execute a script from the director:
RunScript {
RunsWhen = after
RunsOnClient = no
RunsOnFailure = yes
FailJobOnError = no
Command = "/etc/bacula/scripts/t
