>From a routine weekly differential of a Windows 2000 client (Director
and Catalog on a multicore Solaris 10 x86 server) with Bacula 3.0.3
running against MySQL 5.1:
08-Mar 03:47 babylon4-sd JobId 1398: Job write elapsed time = 00:08:54,
Transfer rate = 2.641 M
+bytes/second
08-Mar 03:49 babylon4-dir JobId 1398: Fatal error: sql_create.c:825 Fill
File table Query failed:
+INSERT INTO File (FileIndex, JobId, PathId, FilenameId, LStat,
MD5)SELECT batch.FileIndex,
+batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5
FROM batch JOIN Path ON
+(batch.Path = Path.Path) JOIN Filename ON (batch.Name = Filename.Name):
ERR=Lock wait timeout
+exceeded; try restarting transaction
If you run into this problem, there is a fairly simple fix in most
cases. The default innodb lock wait timeout is 50 seconds. To change
it, edit the MySQL config file (normally /etc/my.cnf) and change the line:
# innodb_lock_wait_timeout=50
to:
innodb_lock_wait_timeout=100
Then restart MySQL and Bacula.
If the problem still occurs, something else is going on. But this
should fix the problem in probably >99% of cases in which the 50-second
timeout is only infrequently being exceeded.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
