Re: [Bacula-users] Problem after an uppgrade from 2.0.X to 2.2.0

2007-09-28 Thread Fredrik Gidensköld
-Original Message- From: Ryan Novosielski [mailto:[EMAIL PROTECTED] Sent: den 28 september 2007 05:08 To: Fredrik Gidensköld Cc: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Problem after an uppgrade from 2.0.X to 2.2.0 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Re: [Bacula-users] Problem after an uppgrade from 2.0.X to 2.2.0

2007-09-27 Thread Arno Lehmann
Hello, 28.09.2007 05:07,, Ryan Novosielski wrote:: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Fredrik Gidensköld wrote: >> Im runing Bacula under Debian and MySQL 5.0.x. and it worked just fine. >> >> Until I used "dselect" to uppgrade Bacula from 2.0.X to 2.2.0 and I got >> this pro

Re: [Bacula-users] Problem after an uppgrade from 2.0.X to 2.2.0

2007-09-27 Thread Ryan Novosielski
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fredrik Gidensköld wrote: > Im runing Bacula under Debian and MySQL 5.0.x. and it worked just fine. > > Until I used "dselect" to uppgrade Bacula from 2.0.X to 2.2.0 and I got this > problmen. > > First I run Bacula as user 'bacula' and got this er

[Bacula-users] Problem after an uppgrade from 2.0.X to 2.2.0

2007-09-26 Thread Fredrik Gidensköld
Im runing Bacula under Debian and MySQL 5.0.x. and it worked just fine. Until I used "dselect" to uppgrade Bacula from 2.0.X to 2.2.0 and I got this problmen. First I run Bacula as user 'bacula' and got this errorr: "nas:/etc/init.d# /usr/sbin/bacula-dir -v -d99 -f -g bacula -u bacula bacula-d