Hi,
04.12.2008 17:11, Bob Hetzel wrote:
> Nevermind all... The answer was
> to run "mysql" then kill the offending process which was apparently
> leftover from the dbcheck command. In my case the output showed it was
> process 517, so I did...
>
> mysql> kill 517 ;
>
> That allowed bacula to
Nevermind all... The answer was
to run "mysql" then kill the offending process which was apparently
leftover from the dbcheck command. In my case the output showed it was
process 517, so I did...
mysql> kill 517 ;
That allowed bacula to continue normally.
But methinks that's a bug for dbchec
Hi all,
I'm using bacula 2.4.3 and I'm thinking I might have created a problem
by terminating dbcheck with ctrl-c. I had read about it taking a long
time to complete if you haven't run it in a while and don't have the
right temporary indexes created. Anyway... I didn't restart the
database
