On Wed, 16 Sep 2009, Richard Mortimer wrote:

> The immediate failure is because the number of affected rows is zero. I'm not
> sure what the underlying cause could be (apart from the fact that JobId 104670
> is not in the Job table - pruning or a bug?)

More likely bug than pruning. It's being run by the scheduler and then
failing almost immediately.

> But I vaguely remember a discussion about zero lines changed on bacula-devel.
> Looking at the code the test that reports the failure has changed between
> 2.4.4 and now (it tests affected_rows < 1 in the latest code).

This happens about 1 in 10 runs, so it's not consistent.

It also happens more often than not on various incremental/diff backups of
the bacula server and there is _always_ at least one changed file each run
(logfiles)

AB



------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users