On 11/6/06, Sarath Jayewardena <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I guess different distributions make modifications to software to fit into
> their philosophy. I faced the same problem when I started playing with
> bacula on Debian (using sqlite). These were the steps that I took to
> re-start f
Hi,
I guess different distributions make modifications to software to fit into
their philosophy. I faced the same problem when I started playing with
bacula on Debian (using sqlite). These were the steps that I took to
re-start from scratch:
- stopped bacula daemons
- remove all files in /var
> (I installed using "apt-get" in debian)
Ah ok... I installed using the source..
> I didn't do anything to create the database last time, i just ran
> "apt-get install bacula-director-mysql" i suppose i can do that again.
Perhaps you can try 'dpkg-reconfigure bacula-director-mysql' after droppi
On 11/6/06, Ger Apeldoorn <[EMAIL PROTECTED]> wrote:
> The scripts are by default in the /etc/bacula directory AFAIK.
thank you for your promt answer.
there is no drop_mysql_tables anywhere on my system.
(I installed using "apt-get" in debian)
> If you really don't have them, you can drop the ent
The scripts are by default in the /etc/bacula directory AFAIK.
start them like this:
cd /etc/bacula
./drop_mysql_tables
If you really don't have them, you can drop the entire bacula database (see
below) and recreate it as you have done before.
#WARNING: This deletes your database!!
mysql -u roo
