James Harper wrote:
> I've been using bacula on a Xen server for many months with no problems
> at all. A week ago I set up some jobs to run concurrently to the
> existing jobs to back up some remote clients to a remote sd.
>
> Since then, jobs aren't completing and are hanging around and things are
> just not running well, although I think the jobs ran okay for the first
> few nights. I upgraded bacula from Debian's 2.2.0 to 2.2.6 around the
> same time, remembering that there was a critical bug in Bacula releases
> around that time. This was probably a bit foolish in retrospect - I
> should have let 2.2.6 run for a bit before introducing the new jobs.
>
> I think the cause may be being indicated by the following messages being
> logged:
>
> "
> 03-Feb 23:24 bitvs1-dir JobId 2104: Fatal error: sql_create.c:732
> sql_create.c:732 insert INSERT INTO batch VALUES
> (234440,2104,'/usr/local/src/linux-2.6-2.6.18.dfsg.1/arch/powerpc/sysdev
> /','mmio_nvram.c','P0A BVJx1 IGg B Po Po A sk BAA I BHoxp9 BFELiO BHoxqG
> A A E','LwUL7mrqTpsgiK8bTaPM5A') failed:
> Incorrect key file for table '/tmp/#sqle43_153_0.MYI'; try to repair it
> 03-Feb 23:24 bitvs1-dir JobId 2104: Fatal error: catreq.c:482 Attribute
> create error. Pool record not found in Catalog.
> "
This is actually fairly concerning. Normally, in the case of MySQL declaring
a table is corrupt, I'd suggest that you just repair the table and move on.
In this case, though, the table that's corrupt is the batch table. This is
just a temporary table, which normally shouldn't even be hanging around long
enough to get a chance to be corrupted, which means that something is hitting
it really quick.
The first thing I'd check is to make sure that the partition holding /tmp
isn't running out of space. If it is, either tell MySQL to use a different
directory with more space, or increase the amount of space allocated to /tmp.
Beyond that, I'd check through your kernel logs to make sure that there aren't
any filesystem or hard drive errors popping up.
Just to make one thing clear, though - this is almost certainly not a Bacula
problem. All that Bacula ever does is fire off standard SQL queries at the
server, which (barring some catastrophic but in MySQL) should never be able to
produce a corrupt table.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
