Alan Brown wrote:
> 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?)
>>
>
>
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
Hi,
On 15/09/2009 16:54, Alan Brown wrote:
>
> 2.4.4 (not able to update yet)
>
> I keep getting errors like this on update slots and incremental updates of
> the bacula-dir server
>
> Subject: Bacula: Admin Fatal Error of UpdateSlots.2009-09-13_12.30.43 Full
>
> 14-Sep 18:24 msslay-dir JobId 1046
2.4.4 (not able to update yet)
I keep getting errors like this on update slots and incremental updates of
the bacula-dir server
Subject: Bacula: Admin Fatal Error of UpdateSlots.2009-09-13_12.30.43 Full
14-Sep 18:24 msslay-dir JobId 104670: Fatal error: sql_update.c:122 Update
failed: affected_
