Upping the mysql wait timeout and interactive timeout to values greater
than the longest backup job seemed to make these errors go away- so
although someone mentioned it in passing previously on the list, it
might be worth mentioning in the 2.2.0 release notes or documentation
since the use of
Thanks for your reply Arno.
> 28-Aug 13:02 socrates-dir: Socrates.2007-08-28_12.55.12 Fatal error:
> > sql_create.c:730 sql_create.c:730 insert INSERT INTO batch VALUES
> > (,13172,'/backups/bacula/working/','bacula-dir.9101.state','GgJ T0AR
> > IGg B A Bs A fw BAA I BG1EyX BG1Exw BG1Exw A A
Hi,
28.08.2007 19:18,, Justin Wainwright wrote::
> Just recently upgraded to Bacula 2.2.0 from 2.0.3 on Debian etch with
> mySQL 5.0.32- since the upgrade, I've seen a number of incremental jobs
> fail with references to the bacula.batch table:
>
> 28-Aug 13:02 socrates-dir: Socrates.2007-08-28
Just recently upgraded to Bacula 2.2.0 from 2.0.3 on Debian etch
with mySQL 5.0.32- since the upgrade, I've seen a number of
incremental jobs fail with references to the bacula.batch table:
28-Aug 13:02 socrates-dir: Socrates.2007-08-28_12.55.12 Fatal
error: catreq.c:478 Attribute cr
