On 7 Sep 2007 at 8:52, BOLLENGIER Eric wrote: > Hi, > > I think that the batch mode is turn on in this setup... > > Can you get the config.out ?
Is this still relevant with recent posts about patching to add #ifdef's etc? > > Bye > > On Friday 07 September 2007 00:48:47 Dan Langille wrote: > > On 7 Sep 2007 at 0:34, Kern Sibbald wrote: > > > Dan, > > > > > > Can you find out more about these: "INSERT INTO Path (Path)..." SQL > > > errors. > > > > > > This doesn't sound like some new feature incompatibility, but that some > > > how (possibly because of trying with batch insert) the user's database > > > has been corrupted. > > > > > > In any case, I would like to see the exact output with the error message > > > if possible. > > > > The original post is here: > > > > http://marc.info/?l=bacula-users&m=118909912529540&w=2 > > > > The first error sounds like the batch table didn't exist. > > > > The second error looks like a nested select. > > > > > Thanks, > > > > > > Kern > > > > > > On Thursday 06 September 2007 21:43, Dan Langille wrote: > > > > It seems that turning off batch updates is not sufficient on MySQL < > > > > 4.1 > > > > > > > > ------- Forwarded message follows ------- > > > > Date sent: Thu, 6 Sep 2007 15:31:36 -0400 > > > > From: "Jody McDonnell" <[EMAIL PROTECTED]> > > > > To: "Dan Langille" <[EMAIL PROTECTED]>, > > > > [EMAIL PROTECTED] > > > > Subject: Re: [Bacula-users] Post-upgrade database issues, > > > > Bacula 1.38.11 to 2.2.1 on Solaris > > > > > > > > [ Double-click this line for list subscription options ] > > > > > > > > On 9/6/07, Dan Langille <[EMAIL PROTECTED]> wrote: > > > > > On 6 Sep 2007 at 13:18, Jody McDonnell wrote: > > > > > > Hi all, > > > > > > > > > > > > I spent the day yesterday upgrading the Bacula install on our > > > > > > Solaris servers from 1.38.11 to 2.2.1. Things initially seemed to > > > > > > work, but the overnight incremental backup failed with some > > > > > > database issues. > > > > > > > > > > > > I should note that I am using MySQL 4.0.18 with Bacula. I've been > > > > > > using this version since I started using Bacula three years ago > > > > > > with version 1.34.2. I haven't upgraded our version of MySQL, > > > > > > mainly because I wasn't exactly sure of the steps required to > > > > > > upgrade MySQL without risking data loss. > > > > > > > > > > > > The only database-related maintenance I performed before the > > > > > > upgrade was to compact the MySQL database via the mysqldump > > > > > > utility, as per section 21.2 of the Bacula manual. > > > > > > > > > > > > After building and installing Bacula 2.2.1, I ran the > > > > > > "update_mysql_tables_9_to_10" script to update my database tables > > > > > > from 1.38-era to 2.0-era. > > > > > > > > > > > > I seem to have encountered two issues. The first seems to be > > > > > > related to the fact that my initial configuration script included > > > > > > the "--enable-batch-insert" directive. The nightly incremental > > > > > > backup failed with the following error messages: > > > > > > > > > > Have you tried the old MySQL without the batch insert enabled? > > > > > > > > > > -- > > > > > Dan Langille - http://www.langille.org/ > > > > > Available for hire: http://www.freebsddiary.org/dan_langille.php > > > > > > > > I did try that...I recompiled Bacula without batch insert enabled, > > > > and > > > > I received the "INSERT INTO Path (Path)..." SQL error. > > > > > > > > Actually, to be more precise, when I first tried an incremental > > > > backup > > > > with batch insert enabled, I received "Table 'bacula.batch' does not > > > > exist" errors on the backup itself and "INSERT INTO Path (Path)..." > > > > errors on the Catalog backup job that ran immediately afterward. > > > > > > > > After I recompiled Bacula 2.2.1 without batch inserts enabled (and > > > > still with the old MySQL database), I triggered an incremental backup > > > > and received the "INSERT INTO Path (Path)..." SQL errors. > > > > > > > > I have pretty much completed what I'd thought about in my first > > > > post--and what you said sounded like a good plan--dumped the existing > > > > database tables to a text file, installed the MySQL 5.0.45 Community > > > > server, ran the grant_bacula_privileges, create_mysql_database, and > > > > make_mysql_tables scripts, and read my data back in via the mysql > > > > executable. The data looks okay--or, at least, I can get a > > > > decent-looking listing when I run "list volumes". > > > > > > > > I've just kicked off an incremental backup; I'll post back with > > > > results. > > > > > > > > Thanks! > > > > Jody > > > > > > > > ---------------------------------------------------------------------- > > > > --- > > > > 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 > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > > > > > > > ------- End of forwarded message ------- > > > > -- > Eric BOLLENGIER, Administrateur Système - Poste 1325 > SIGMA Informatique http://www.sigma.fr > 3 rue Newton, BP 4127, 44241 La Chapelle sur Erdre Cedex > tel : 02.40.37.14.00 > > -- Dan Langille - http://www.langille.org/ Available for hire: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------------------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
