<[EMAIL PROTECTED]> writes: > Sorry about that last empty post...
Sorry, me too if my middle reply sounded snotty, it appeared here that you had purposely posted those two links in both your earlier messages ... they appear here with no `> ' in front. Maybe your mailer is mangling stuff or mine is. >> bacula-1.36.3-r2.ebuild >> >> How is it different than: >> >> ls /usr/portage/app-backup/bacula/*.ebuild >> > /usr/portage/app-backup/bacula/bacula-1.36.3-r2.ebuild > The current version of bacula is 1.38.2 which is > several months of development ahead of 1.36.3. > Although this will not fix your problem as I agree > with you it looks like a problem with the database. I did build the current version from the tar.gz and had the same problem with it. But please do email your ebuild for 38.X > Did you run the bacula scripts to create the database > and grant privileges? And you started mysql? Where > there any errors or warnings when you ran these > scripts? Now that is somewhat confusing.. I see a herd of scripts in /etc/bacula but nothing explaining how to use them. At least not in the tutorial and really no manual comes with even the tarball even though it refers you to a `doc' directory, for html manual there is none in the tar.gz. Apparently the README's are out of date. How can I diagnose the problem here? It appears the `director' cannot talk to the mysql deamon. Mysql started with no errors from `/etc/init.d/mysql start'. But now I get strange behavior there like this: # /etc/init.d/mysql stop * Stopping mysqld (/etc/mysql/my.cnf) ... [ !! ] HOST:reader /etc/bacula # /etc/init.d/mysql start * WARNING: "mysql" has already been started. HOST:reader /etc/bacula Claims to have stopped but then warns its already started. But no permission type error. Ok, its running now but the directory cannot talk to it: Using the command suggested in manual tutorial as a starter command it fails: ./bacula start Starting the Bacula Storage daemon Starting the Bacula File daemon Starting the Bacula Director daemon 22-Nov 13:31 bacula-dir: Fatal error: Could not open database "bacula". 22-Nov 13:31 bacula-dir: Fatal error: mysql.c:169 Unable to connect to MySQL server. Database=bacula User=bacula It is probably not running or your password is incorrect. 22-Nov 13:31 bacula-dir ERROR TERMINATION Please correct configuration file: /etc/bacula/bacula-dir.conf Were are the directions for using the scripts in /etc/bacula ? > Also do you have mysql as one of your use flags for > bacula? I used no special use flags and I don't see mysql in make.conf. Wouldn't bacula tell me if it were not compiled to use mysql? ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
