>This is what you said Scott Ruckh >>> On 3 Aug 2007 at 23:17, Scott Ruckh wrote: >>> >>>> I am running Bacula version 2.1.28 (built from sources) on CentOS 4.5 >>>> x86_64. >>> >>> That is the latest BETA version of Bacula. >>> >>>> I recently upgraded php to PHP 5.2.3 and subsequently I also upgraded >>>> MySQL to version 5.0.45. >>>> >>>> I hit a few bumps but all-in-all most things are back to normal. >>>> >>>> Unfortunately bacula is giving me some fits. >>>> >>>> Before MySQL upgrade I was running bacula 2.0.8 without too many >>>> issues. After the upgrade bacula did not work as expected. >>>> >>>> After trying a few things, I downloaded the latest beta from >>>> sourceforge and started over. >>>> >>>> I used the scripts in the /etc/bacula directory to create the MySQL >>>> database and tables, and then the grant permission script to grant >>>> permissions. >>>> >>>> The storage daemon, the client, and the director all start without >>>> errors. >>>> >>>> I kick off a backup job for a remote client and all starts off normal >>>> as it did before. The pre backup job runs fine and terminates. Then >>>> bacula looks like it is off to the races doing it thing. >>>> >>>> Unfortunately nothing is being written to the database during the >>>> backup, and in the log I get a ton of errors that look like the >>>> following: >>>> >>>> 03-Aug 22:49 firewall-dir: AMD01_FULL.2007-08-03_22.42.29 Fatal error: >>>> catreq.c:478 Attribute create error. sql_get.c:1005 Media record for >>>> Volume "FULL-0001" not found. 03-Aug 22:49 firewall-dir: >>>> AMD01_FULL.2007-08-03_22.42.29 Fatal error: sql_create.c:730 >>>> sql_create.c:730 insert INSERT INTO batch VALUES >>>> (8774,1,'C:/path/','filename.ext','A A IH/ B A A A CJ/ A A BGm2w7 >>>> BGS3tM BGS3tM A A M','1QMVRHuM+6/LjZpNVY/8KQ') failed: Table >>>> 'bacula.batch' doesn't exist >>>> >>>> There definitely is not a bacula.batch table. Where does this table >>>> get created? Do I need to do any special initialization of the >>>> database before running the backup job. Is there something with >>>> MySQL5 that I need to consider that I did not have to with MySQL4? >>> >>> There is an upgrade script which you need to run manually. This will >>> perform any database modifications required for the latest version >>> you are running >> >> When I looked at the upgrade script it did not look like it would have any >> impact and the script was for upgrading older 1.38 type databases. >> >>> FYI, I'm running 2.0.3 and do not have a batch table. >>> >>> I checked the database creation and update files. It does not seem >>> to create the batch table. I'll check with devel@ and find out the >>> story. >>> >>>> I did a quick google for Media record for Volume "xxxx" not found and >>>> did not come up with anything useful. I am not sure what that error >>>> is telling me. >>> >>> It's tell you that it could not find an entry for the Volume it is >>> trying to backup. >>> >>> BTW: Did you happen to drop the old database and create a new one for >>> Bacula? Is FULL-0001 a VOLUME label that you created with the >>> previous version of Bacula? >> >> I dropped tables and database after I could not get things working with >> old >> database. I have created the database and tables from scratch several >> times. Each time, the scripts completes successfully and database/tables >> are created. When the daemons are started for the first time, the >> bacula.Pool table is updated with the information from the bacula-dir.conf >> file. As such, I assumed bacula/MySQL are playing nice with each other. >> The FULL-001 is an auto-labled/auto-created volume (on disk). >> >>>> I will admit I have not looked at the manual in quite some time as the >>>> backups were working fine before the MySQL upgrade. >>>> >>>> I am hoping someone knows what this error means and can point me in >>>> the right direction. > >Interestingly enough when I built the src.rpm (v2.0.3) using: > >rpmbuild -bb --define "build_centos4 1" --define "build_mysql5 1" bacula.spec > >It appears to be working fine. > >When I used the following configure command when compiling from source (v2.0.3) when I had MySQL v4.x everything also worked fine. > >CFLAGS="-g -Wall -O0 -I/usr/lib64/mysql" \ >LDFLAGS="-L/usr/lib64/mysql -L/lib64 -L/usr/lib64" \ >./configure \ >--sbindir=/usr/local/sbin/bacula \ >--sysconfdir=/etc/sysconfig \ >--with-scriptdir=/etc/bacula \ >--enable-smartalloc \ >--with-pid-dir=/var/run \ >--with-subsys-dir=/var/lock/subsys \ >--enable-conio \ >--with-openssl \ >--with-mysql \ >--with-working-dir=/usr/local/bin/bacula/working \ >--with-dump-email="[EMAIL PROTECTED]" \ >--with-job-email="[EMAIL PROTECTED]" \ >--with-dir-user=bacula \ >--with-dir-group=bacula \ >--with-sd-user=bacula \ >--with-sd-group=bacula \ >--with-fd-user=root \ >--with-fd-group=root \ >--with-python > >Unfortunately using the above configure command with v2.0.3 and 2.1.x >Betas when using MySQL v5 there appear to be some issues. The source >compiles without error, but the above described symptoms are present. > >Is there something blatantly wrong with the configure command when using a >MySQL5 database? > >Thanks.
I have the same problem with Bacula 2.2.1 on Ubuntu 7.04. Unfortunately, I cannot build a rpmpackage on Ubuntu. What does rpmbuild differently with the mysql5 param compared to the configure? Andreas ------------------------------------------------------------------------- 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
