For what it's worth, I deleted all the volumes in the differential pool
for this client, and then the job ran once fine. Something must have
been undetectably scrozzled in the db.
Jeff Dickens wrote:
I just finished a dbcheck, which found no major problems, and then I
ran this job, which fai
Kevin Keane wrote:
Is there possibly something wrong with the permissions on that file, or
the /bacula/marie3 directory? Maybe it is only writable by root, not the
user that the bacula-sd is running as?
Nope, it has the same permissions, owner and group as all my other disk
volumes.
Is there possibly something wrong with the permissions on that file, or
the /bacula/marie3 directory? Maybe it is only writable by root, not the
user that the bacula-sd is running as?
Jeff Dickens wrote:
> I just finished a dbcheck, which found no major problems, and then I
> ran this job, whic
Is there possibly something wrong with the permissions on that file, or
the /bacula/marie3 directory? Maybe it is only writable by root, not the
user that the bacula-sd is running as?
Jeff Dickens wrote:
> I just finished a dbcheck, which found no major problems, and then I
> ran this job, whic
I just finished a dbcheck, which found no major problems, and then I ran
this job, which failed as follows:
Where it says "could not open: /bacula/marie3/marie3-diff-0616, ERR=No
such file or directory" that file does exist. It's 955MB.
Lots of other jobs are working fine, but this one keeps
