Kern Sibbald wrote: > 4. The errors you guys are seeing is because batch insert is turned on but > something went wrong in creating the batch table. I suspect that you have not > setup the correct permissions on MySQL that allows the user you are running > with (normally "bacula") to create tables. However, if that is the case, > there *should* be an error message that is printed -- I don't imagine that > error path has been tested though. Something to be investigated more.
I had a problem with bacula backups failing with a similar error. I eventually debugged it to be a problem with MySQL not allowing the creation of temporary tables. So 'CREATE TABLE blah' worked, but 'CREATE TEMPORARY TABLE blah' didn't. Very weird I thought! I eventually worked out that this was because the permissions on /tmp where wrong - I'd accidentally done a 'rm -rf /tmp', and then failed to re-create it properly. The perms on /tmp were something like 600 and owned root:root. In the default Debian/Ubuntu configurations that I have seen MySQL creates its temporary tables in /tmp, but of course the mysql user couldn't write to /tmp, and it therefore failed. Using /tmp for temporary tables can also cause problems on backups with lots of files if you have quite a small / (slash partition) because / fills up and the backup dies :) You can check/configure where temporary tables are located by looking at the 'tmpdir' option in my.cnf. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
