Hi Alan,
12.05.2008 10:40, Alan Brown wrote:
> A couple of months ago, one job started consistently failing with this
> error:
>
> 09-May 22:30 msslay-dir JobId 56964: No prior Full backup Job record found.
> 09-May 22:30 msslay-dir JobId 56964: No prior or suitable Full backup found
> in catalog. Doing FULL backup.
> 09-May 22:37 msslay-dir JobId 56964: Fatal error: sql_update.c:122 Update
> failed: affected_rows=0 for UPDATE Job SET
> JobStatus='R',Level='F',StartTime='2008-05-09
> 22:37:18',ClientId=3,JobTDate=1210369038,PoolId=12 WHERE JobId=56964
> 09-May 22:37 msslay-dir JobId 56964: Warning: Error updating job record.
> sql_update.c:194 Update failed: affected_rows=0 for UPDATE Job SET
> JobStatus='f',EndTime='2008-05-09
> 22:37:18',ClientId=3,JobBytes=0,JobFiles=0,JobErrors=0,VolSessionId=0,VolSessionTime=0,PoolId=12,FileSetId=173,JobTDate=1210369038,RealEndTime='2008-05-09
> 22:37:18',PriorJobId=0 WHERE JobId=56964
>
> I've been trying to make sense of it for a while.
>
> Recently I added a new machine and 2 new backup jobs.
>
> Again, one of them is consistently failing with similar database errors.
That looks... interesting.
>
> Mysqlcheck -A and dbcheck both say the database is fine.
>
>
> There's plenty of space on the databases disks (including tmp space) and
> ~85 other backups (which are all a LOT larger in terms of file numbers and
> file volumes) are suceeding happily.
>
> Does anyone have any ideas?
Well, I guess you checked the obvious. The only thing you don't
mention is if the job entries exist in the catalog. In your example,
JobId 56964. Have you verified this?
If it does exist, and MySQL reports no error details on the update, I
would try to run the update command from the mysql console program.
Perhaps that shows some more details. (By the way - could it be that
the table grew above the default limit of I believe 2GB?)
If the job record does not exist it's time to find why it can't be
created. Perhaps searching through the (Bacula) console log reveals
some eralier, non-critical error, or the MySQL logs show something.
In any case, this looks like a MySQL related problem, and trying to
create the records by hand might give you more error details.
Arno
> AB
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
