In message <[EMAIL PROTECTED]> you wrote:
> 
> 24.09.2007 08:00,, Christoph Litauer wrote::
...
> > Table 'bacula.batch' doesn't exist
> ...
> 
> The error above is probably due to Bacula not correctly handling batch 
> inserts. I discoverd something at least similar if not identical...
...

There have been several reports about this problem before; this onle
was IMHO especially interesting:

| From: "Jody McDonnell" <[EMAIL PROTECTED]>
| Date: Thu, 6 Sep 2007 13:18:39 -0400 (19:18 CEST)
| Subject: [Bacula-users] Post-upgrade database issues,
|       Bacula 1.38.11 to 2.2.1 on Solaris

In message <[EMAIL PROTECTED]>
Jody McDonnell wrote:
...
> ==============================
> 06-Sep 09:39 kodos-dir: BackupKang.2007-09-06_01.05.00 Fatal error:
> sql_create.c:730 sql_create.c:730 insert INSERT INTO batch VALUES
> (5432,2083,'/repo/cvsroot/est/build/','est.tar.gz,v','gAAW C2IJ IFt B
> Bw B A 3ezOL CAA G8Ew BG3vmb BG3uk8 BG3uk9 A A
> C','oqzs5tC+gpBJ0EESyZoa7A') failed:
> Table 'bacula.batch' doesn't exist
> 06-Sep 09:39 kodos-dir: sql_create.c:730 INSERT INTO batch VALUES
> (5432,2083,'/repo/cvsroot/est/build/','est.tar.gz,v','gAAW C2IJ IFt B
> Bw B A 3ezOL CAA G8Ew BG3vmb BG3uk8 BG3uk9 A A
> C','oqzs5tC+gpBJ0EESyZoa7A')
> 06-Sep 09:39 kodos-dir: BackupKang.2007-09-06_01.05.00 Fatal error:
> catreq.c:478 Attribute create error. sql_find.c:333 Request for Volume
> item 1 greater than max 0 or less than 1
> [...etc...]
> ==============================
> 
> There was a long pause in the backup while Bacula requested that a new
> tape be mounted. From searching through past posts to this list, it
> sounds like this is due to a timeout by MySQL, and I think that it
> might be possible to get around the issue by changing the wait_timeout
> value in my.cnf to some really large value.
> 
> Since I only have a single-tape DAT drive, backups can sometimes be
> stalled over an entire weekend waiting for a new tape to be mounted.
> Since I didn't really want to change the wait_timeout to be some huge
> number like 4 days, I decided to recompile Bacula 2.2.1 without the
> "--enable-batch-insert" directive. I hadn't previously noticed any
> database performance issues, anyway.

Now I'm running into the same problem, with a configuration of
bacula-2.2.4 that has been running fine before (and ever since I
upgraded to 2.x):

...
08-Oct 09:34 mneme-dir: Pollux-Other.2007-10-06_00.10.03 Fatal error: 
sql_create.c:730 sql_create.c:730 insert INSERT INTO batch VALUES 
(2688182,12294,'/work/concord/eldk-256k/eldk_build/target_rpms/crosstool/BUILD/crosstool-0.35.concord.256k.patched/build/gcc-4.0.0-glibc-2.3.5-eldk/powerpc-linux/gcc-4.0.0/gcc/ada/','s-exctab.ads','P0B
 Cn5cs IGk B Id Id A BDK BAA Q BG2Xqp /lTe1 BG0uvi A A 
C','NRehbvfPIksHds8p9o/Eiw') failed:
Table 'bacula.batch' doesn't exist
...

Here, too, the problem was most probably triggered by the  fact  that
the backup was hanging for a long time (over the weekend) because the
autoloader  was  unexpactedly  running  out  of  tapes,  which  never
happened before.


I see a common pattern here: when a backup job is  hanging  for  some
extended time, we run into these "Table 'bacula.batch' doesn't exist"
errors.

Is increasing the MySQL to really huge values really the way to go?

I think this should be fixed within bacula instead?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
Horses just naturally have mohawk haircuts.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to