Hello,
Perhaps a table is getting locked by Bacula and that is causing a sort of
deadlock, then gets timed out. In the case of bpipe, you are running the job
while Bacula is running, which could run into this problem.
I suspect that what might be happening is that after a certain point, Bacula
Hello,
Today i tried the bpipe plugin + mysqldump at home.
Ran into same problem like at work,
mysqldump: Error 2013: Lost connection to MySQL server during query when
dumping table `File` at row: ...
Then i tried without lock tables, here is the FileSet:
FileSet {
Name = CatalogPipe
Ignore
Hello,
On Thu, 2009-05-28 at 20:00 +1000, James Harper wrote:
> >
> > What is different when bacula calls mysqldump via bpipe plugin?
> >
>
> Can you comment on how long between starting the mysqldump and the
> failure occuring? Is it consistently the same duration, which could
> indicate a tim
You might look carefully at the mysqldump documentation. They probably have a
command line option that prevents timeouts or sets the timeout periods.
Normally if one writes C code such as Bacula, we must explicitly enable what
is called "reconnect=1". We set it in the initialization packet.
>
> What is different when bacula calls mysqldump via bpipe plugin?
>
Can you comment on how long between starting the mysqldump and the
failure occuring? Is it consistently the same duration, which could
indicate a timeout somewhere?
Btw - I always use gzip on the Exchange plugin and it works
Hello,
I found it is a mysqldump problem, but only if called via bpipe.
Got this message on bconsole:
*mysqldump: Error 2013: Lost connection to MySQL server during query
when dumping table `File` at row: 26695285
Don't understand, because i have no problems running the standard
BackupCatalog us
Hello,
On Wed, 2009-05-27 at 16:44 +0200, Kern Sibbald wrote:
> Nice that you ruled out problems with 4GB
>
> In looking at your plugin command line, I recommend:
> try turning off gzip on the plugin command line -- I don't think it will work
> correctly with the plugin (we have never used that
Nice that you ruled out problems with 4GB
In looking at your plugin command line, I recommend:
try turning off gzip on the plugin command line -- I don't think it will work
correctly with the plugin (we have never used that option). Then make sure
there is no compression in the Bacula FileSet.
Hello,
On Wed, 2009-05-27 at 14:28 +0200, Kern Sibbald wrote:
> It is quite possible that mysqldump creates a much larger dump file
> particularly if you have compression turned on.
>
> Perhaps you filled up your output filesystem.
definitely NO
>
> We have tested this many times and never ha
It is quite possible that mysqldump creates a much larger dump file
particularly if you have compression turned on.
Perhaps you filled up your output filesystem.
We have tested this many times and never had such problems. You might try
testing with a much smaller database to ensure that you ar
Hello,
I tried to setup bpipe plugin for Catalog backup.
Below you can see FileSet/Job config, Backup/Restore logs.
Everything looks ok, but mysqldump is incomplete!
Running "mysqldump -f --opt bacula > bacula.sql" from shell
results in 14G bacula.sql file.
/MYSQL/bacula.sql is only 3,325,644,28
11 matches
Mail list logo
