Analysis by Marc and Eric indicates that you may be suffering from a rather
arbitrary default time limit that MySQL imposes on locks, which is rather
absurd.
===
>From Marc:
innodb_lock_wait_timeout=50
Timeout in seconds an InnoDB transaction may wait for a lock before being
rolled back. Inno
Hi Kern,
Kern Sibbald napsal(a):
> On Monday 24 September 2007 15:58, Arno Lehmann wrote:
>
>> Hi,
>>
>> 24.09.2007 14:53,, Kern Sibbald wrote::
>>
>>> Hello,
>>>
>>> On Monday 24 September 2007 13:57, Chris Howells wrote:
>>>
Kern Sibbald wrote:
> 4. The err
On Monday 24 September 2007 15:58, Arno Lehmann wrote:
> Hi,
>
> 24.09.2007 14:53,, Kern Sibbald wrote::
> > Hello,
> >
> > On Monday 24 September 2007 13:57, Chris Howells wrote:
> >> Kern Sibbald wrote:
> >>> 4. The errors you guys are seeing is because batch insert is turned on
>
> Again, it may
Hello,
At this time, I believe that this is a configuration problem with your MySQL.
You have several options for correcting the problem:
1. Correct your MySQL configuration so that it can work correctly.
2. Turn off batch insert mode
3. Backup to version 1.38.11 (I don't recommend this).
4.
Hi,
24.09.2007 14:53,, Kern Sibbald wrote::
> Hello,
>
> On Monday 24 September 2007 13:57, Chris Howells wrote:
>> Kern Sibbald wrote:
>>> 4. The errors you guys are seeing is because batch insert is turned on
Again, it may be turned on, but the config.out told me it was off.
This might be a m
Hi Kern,
I litle bit investigated this issue. When I configured Bacula 2.2.4 on SuSE
Linux with MySQL 5.0.45 with this option (see below), I didn't get any error
messages about "Table 'bacula.batch' doesn't exist ".
BUT after much Backup Job(at the end of Job) (during this Backu Job no problem,
Hello,
On Monday 24 September 2007 13:57, Chris Howells wrote:
> 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 allo
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 tab
Hi Kern,
now I finished testing Bacula 2.2.4 with configuration (without
"--enable-batch-insert")
./configure \
--sbindir=/bacula/bin \
--sysconfdir=/bacula/bin \
--with-pid-dir=/bacula/working \
--with-subsys-dir=/bacula/working \
On Monday 24 September 2007 09:54, Ondrej Planka wrote:
> Hi Kern,
>
> tahnks for your TIP, but this issue is still open.
Please explain. I don't see why the issue should be open with what you
describe below.
> When I once more configured Bacula 2.2.4 (old version -make uninstall, make
> distcle
Hi Kern,
tahnks for your TIP, but this issue is still open.
When I once more configured Bacula 2.2.4 (old version -make uninstall, make
distclean) without "--enable-batch-insert" - job appears to be correct - now I
am testing this issue.
BUT: When backup job finished, I saw this status (command
Hello,
I've tested this backwards and forwards with all kinds of variations,
including looking at the code. Everything that I do works perfectly fine.
A few points:
1. Make sure you are always starting from a clean source file. If you built
it on another machine then copied it, the source is
> Hi,
>
> 23.09.2007 15:15,, Marc Cousin wrote::
> >> You shouldn't concern yourself with the "batch" table. It is a temp table
> >> and there is no need to create.
>
> Or rather, that's the way it should be.
>
> >> Your problem has nothing to do with the batch insert code itself, but
> >> simp
Hi,
23.09.2007 15:15,, Marc Cousin wrote::
>> You shouldn't concern yourself with the "batch" table. It is a temp table
>> and there is no need to create.
Or rather, that's the way it should be.
>> Your problem has nothing to do with the batch insert code itself, but
>> simply that it is turned
Hi guys,
I have the same problem. I upgraded Bacula 1.38.11 (SuSE Linux + Mysql
5.0.24) to 2.2.4 and I got thousand error messages as you seen below.
22-Sep 07:34 noem-dir: Backup_TOV.2007-09-22_04.34.57 Fatal error:
sql_create.c:730 sql_create.c:730 insert INSERT INTO batch VALUES
(510514,100
> You shouldn't concern yourself with the "batch" table. It is a temp table
> and there is no need to create.
>
> Your problem has nothing to do with the batch insert code itself, but
> simply that it is turned off for some unknown reason.
>
> Regards,
>
> Kern
>
Anyway, doesn't it seems like the
On Saturday 22 September 2007 23:44, Arno Lehmann wrote:
> Hi,
>
> I'm seeing an interesting thing at a Bacula 2.2.4 installation.
>
> This is on FreeBSD 7 current, which is not an OS I know well, so I
> might present information unrelated to each other here. See below for
> details where I'm unsur
Hi,
I'm seeing an interesting thing at a Bacula 2.2.4 installation.
This is on FreeBSD 7 current, which is not an OS I know well, so I
might present information unrelated to each other here. See below for
details where I'm unsure.
This is a Bacula installed from the ports. In
/usr/ports/sysut
18 matches
Mail list logo
