Re: [Bacula-users] SQL-Errors

2010-07-16 Thread Rory Campbell-Lange
Hi Alex On 16/07/10, Alex Huth (a.h...@tmr.net) wrote: > Fatal error: catreq.c:492 attribute create error. > 2010-07-16 10:19:06 > borusse.ewmr.base-sd > JobId=9 Job="borusse.2010-07-16_09.50.07_05" marked to be canceled. This appears to be an issue with MySQL table corruption. See http://wiki.b

[Bacula-users] SQL-Errors

2010-07-16 Thread Alex Huth
Hello! Today i got SQL-Errors doing a Fullbackup of a FreeBSD host. Hope someone can help with that. --- 2010-07-16 10:19:06 borusse.ewmr.base-dir Fatal error: sql_create.c:799 sql_create.c:799 insert INSERT INTO batch VALUES (466042,9,'/var/db/portsnap/files/','8b034d9c66

[Bacula-users] SQL errors from failed incremental backup - what happened?

2007-12-05 Thread Shon Stephens
All, I have a job which has failed the last few nights with the following errors: 03-Dec 20:00 mt-back4.director JobId 0: Fatal error: sql_create.c:489 sql_create.c:489 query SELECT ClientId,Uname FROM Client WHERE Name=' mt-back3.mentora' failed: Lost connection to MySQL server during query

Re: [Bacula-users] SQL errors after upgrade from 1.36 to 2.2.5

2007-10-28 Thread Ryan Novosielski
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Search the list. IIRC, there is a minimum PostgreSQL version associated with Bacula 2.2.x Disaster wrote: > Dear all, > after an upgrade I get those error (via Bacula daemon message). I've > upgraded from 1.36 to 2.2.5 on gentoo running postgres (I've

[Bacula-users] SQL errors after upgrade from 1.36 to 2.2.5

2007-10-17 Thread Disaster
Dear all, after an upgrade I get those error (via Bacula daemon message). I've upgraded from 1.36 to 2.2.5 on gentoo running postgres (I've successfully updated db to version 9 and then 10). backups are running ok and if I issue those query manually on my db they works. thanks Andrea On Wed, 2007

Re: [Bacula-users] SQL errors after upgrading to 2.2.5

2007-10-16 Thread Frank Sweetser
Silver Salonen wrote: > Hello! > > I use Bacula on FreeBSD-6.1. I upgraded dir and sd from 2.2.4 to 2.2.5 on > 12th > of oct. Now some of the jobs contain SQL errors: > > 15-Oct 23:06 backup-dir JobId 12440: Warning: SQL failed, but ignored. > ERR=Query failed: SELECT MAX(MediaId) FROM Media,P

[Bacula-users] SQL errors after upgrading to 2.2.5

2007-10-15 Thread Silver Salonen
Hello! I use Bacula on FreeBSD-6.1. I upgraded dir and sd from 2.2.4 to 2.2.5 on 12th of oct. Now some of the jobs contain SQL errors: 15-Oct 23:06 backup-dir JobId 12440: Warning: SQL failed, but ignored. ERR=Query failed: SELECT MAX(MediaId) FROM Media,POOL WHERE Pool.PoolId=179: ERR=Table '

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-27 Thread Ivan Adzhubey
On Monday 27 August 2007 02:27:14 am Ivan Adzhubey wrote: > > I have also tried to play with DBSocket, DBAddress and DBPort in Catalog > > resource but to no avail. > > Aha, I have changed bacula-dir startup command by specifying user/groop as > root instead of bacula and it worked. I can connect v

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Ivan Adzhubey
On Monday 27 August 2007 02:16:55 am Ivan Adzhubey wrote: > On Monday 27 August 2007 02:07:52 am Ivan Adzhubey wrote: > > On Monday 27 August 2007 01:53:52 am Ivan Adzhubey wrote: > > > confirmed it by running both ldd and nm against the binary). Is it > > > normal? I am pretty sure previous versio

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Ivan Adzhubey
On Monday 27 August 2007 02:07:52 am Ivan Adzhubey wrote: > On Monday 27 August 2007 01:53:52 am Ivan Adzhubey wrote: > > confirmed it by running both ldd and nm against the binary). Is it > > normal? I am pretty sure previous version 1.38.11 has been built with > > dynamic libraries. Now the .so v

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Ivan Adzhubey
On Monday 27 August 2007 01:53:52 am Ivan Adzhubey wrote: > confirmed it by running both ldd and nm against the binary). Is it normal? > I am pretty sure previous version 1.38.11 has been built with dynamic > libraries. Now the .so versions of libmysqlclient are installed in /lib and > bacula build

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Ivan Adzhubey
Hi Dan, On Sunday 26 August 2007 03:34:25 pm Dan Langille wrote: > On 26 Aug 2007 at 15:01, Ivan Adzhubey wrote: > > Hi, > > > > I have upgraded to bacula installation on our old RedHat 8.0 server to > > version 2.2.0 recently. It was built from sources with MySQL support > > enabled (including ba

Re: [Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Dan Langille
On 26 Aug 2007 at 15:01, Ivan Adzhubey wrote: > Hi, > > I have upgraded to bacula installation on our old RedHat 8.0 server to > version > 2.2.0 recently. It was built from sources with MySQL support enabled > (including batch inserts). MySQL version installed is 3.23.58. Now I am > getting t

[Bacula-users] SQL errors with MySQL 3.23.58

2007-08-26 Thread Ivan Adzhubey
Hi, I have upgraded to bacula installation on our old RedHat 8.0 server to version 2.2.0 recently. It was built from sources with MySQL support enabled (including batch inserts). MySQL version installed is 3.23.58. Now I am getting the following errors when bacula attempts to despool file attri