Re: [Bacula-users] MySQL errors

2009-06-18 Thread John Kennedy
Martin Simmons wrote:
 On Tue, 16 Jun 2009 14:29:25 +0100, John Kennedy said:
 We keep getting the following errors when running backups and any time
 we query:

 16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
 sql_get.c:359 query SELECT VolumeName,MAX(VolIndex) FROM JobMedia,Media
 WHERE JobMedia.JobId=8703 AND JobMedia.MediaId=Media.MediaId GROUP BY
 VolumeName ORDER BY 2 ASC failed:
 Can't create/write to file '/tmp/#sql_555_0.MYI' (Errcode: 30)

 I can not find any problems with MySQL and /tmp is not full nor are
 there any permission issues.
 I am relatively new to Bacula and know a bit about MySQL (just short of
 Jr DBA level).
 
 Errcode 30 means Read-only file system so I think you might have problems
 with your /tmp directory.
 
 What are the permissions on it?  Can you create files in /tmp from the shell
 when running as the same user as mysqld?
 
 Is it a separate partition and does mount show rw for it?  Have you tried
 rebooting in single user mode and doing an fsck to check for errors?
 
 __Martin
 
 --
 Crystal Reports - New Free Runtime and 30 Day Trial
 Check out the new simplified licensing option that enables unlimited
 royalty-free distribution of the report engine for externally facing 
 server and web deployment.
 http://p.sf.net/sfu/businessobjects
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users

For some reason the FS was put in a read only state. Once we cleared
those problems then things went back to being almost happy...
Thanks,
John

-- 
John Kennedy
Linux System Administrator
Publishing Technology plc
T: +44 1865 397838
M: +44 7771 962776
john.kenn...@publishingtechnology.com
http://www.publishingtechnology.com

Publishing Technology plc is registered in England No. 837205.
Registered Office: Unipart House, Garsington Road, Oxford OX4 2GQ.


The information in this message is intended solely for the addressee and should 
be considered confidential.  Publishing Technology does not accept legal 
responsibility for the contents of this message and any statements contained 
herein which do not relate to the official business of Publishing Technology 
are neither given nor endorsed by Publishing Technology and are those of the 
individual and not of Publishing Technology. This message has been scanned for 
viruses using the most current and reliable tools available and Publishing 
Technology excludes all liability related to any viruses that might exist in 
any attachment or which may have been acquired in transit.begin:vcard
fn:John Kennedy
n:Kennedy;John
org:Publishing Technology
adr:Garsington Rd;;Unipart House;Oxford;OXON;OX4 2GQ;United Kingdom
email;internet:john.kenn...@publishingtechnology.com
title:Linux System Administrator
tel;work:+44 1865 397 838
tel;cell:+44 7771 962 776
note:Publishing Technology plc is registered in England No. 837205.
x-mozilla-html:FALSE
url:http://www.publishingtechnology.com
version:2.1
end:vcard

--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] MySQL errors

2009-06-17 Thread Martin Simmons
 On Tue, 16 Jun 2009 14:29:25 +0100, John Kennedy said:
 
 We keep getting the following errors when running backups and any time
 we query:
 
 16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
 sql_get.c:359 query SELECT VolumeName,MAX(VolIndex) FROM JobMedia,Media
 WHERE JobMedia.JobId=8703 AND JobMedia.MediaId=Media.MediaId GROUP BY
 VolumeName ORDER BY 2 ASC failed:
 Can't create/write to file '/tmp/#sql_555_0.MYI' (Errcode: 30)
 
 I can not find any problems with MySQL and /tmp is not full nor are
 there any permission issues.
 I am relatively new to Bacula and know a bit about MySQL (just short of
 Jr DBA level).

Errcode 30 means Read-only file system so I think you might have problems
with your /tmp directory.

What are the permissions on it?  Can you create files in /tmp from the shell
when running as the same user as mysqld?

Is it a separate partition and does mount show rw for it?  Have you tried
rebooting in single user mode and doing an fsck to check for errors?

__Martin

--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] MySQL errors

2009-06-16 Thread John Kennedy
We keep getting the following errors when running backups and any time
we query:

16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
sql_get.c:359 query SELECT VolumeName,MAX(VolIndex) FROM JobMedia,Media
WHERE JobMedia.JobId=8703 AND JobMedia.MediaId=Media.MediaId GROUP BY
VolumeName ORDER BY 2 ASC failed:
Can't create/write to file '/tmp/#sql_555_0.MYI' (Errcode: 30)

I can not find any problems with MySQL and /tmp is not full nor are
there any permission issues.
I am relatively new to Bacula and know a bit about MySQL (just short of
Jr DBA level).
Thanks,
John

The information in this message is intended solely for the addressee and should 
be considered confidential.  Publishing Technology does not accept legal 
responsibility for the contents of this message and any statements contained 
herein which do not relate to the official business of Publishing Technology 
are neither given nor endorsed by Publishing Technology and are those of the 
individual and not of Publishing Technology. This message has been scanned for 
viruses using the most current and reliable tools available and Publishing 
Technology excludes all liability related to any viruses that might exist in 
any attachment or which may have been acquired in transit.

--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] MySQL Errors being logged

2008-02-05 Thread James Harper
 
 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.
 

Just to follow up, I freed up some space and the problem hasn't come
back.

Thanks for the tip.

James

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] MySQL Errors being logged

2008-02-03 Thread James Harper
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.


Bacula is version 2.2.6 (Debian package), MySQL is 5.0.32-7etch1 (again,
Debian package).

Any suggestions as to what I need to do to fix it? Blowing away the
database is an option, as my media are fairly high rotation (backups are
mainly for disaster recovery as opposed to file recovery), but obviously
a better solution would be preferred.

Thanks

James


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] MySQL Errors being logged

2008-02-03 Thread Frank Sweetser
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/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] MySQL Errors being logged

2008-02-03 Thread James Harper
 
 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.
 

When I just checked now, /var/log/mysql had about 2G of logfiles in it,
and the root filesystem (containing /var/log) was full.

My best guess is that it was filling up each night, but then by morning
mysql would have purged the oldest logfile, so it looked like space
wasn't a problem.

Should I expect that much logging to be happening? It looks like
database transaction logs. I have tuned it down to 3 days of log history
instead of 10.

Thanks for the tip!

James

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users