I doubt that this is a databse issue.
Messages from console commands in Job RunScripts are logged against
jobid 0.
In Bacula 7 there is bug though and the messages are only sent when the
config is reloaded or the director is restarted rather than being sent
with the messages for the job that
I was thinking it was more of a corrupted database issue. I’ve pretty much
checked everything else.
Is there something significant about “JobID 0”?
From: Brady, Mike [mailto:mike.br...@devnull.net.nz]
Sent: Saturday, January 17, 2015 8:27 PM
To: bacula-users@lists.sourceforge.net
Subject: Re: [Ba
Nothing local for crontabs in /var/spool/cron and /etc/cron* (CentOS 6.5).
I'll pay more attention to when I get the email and the tcpdump suggestion may
be the next thing I do since I don't want to change the password, at least not
yet.
I thought maybe something was corrupted in the database ca
