John J. Stimson-III wrote:
>
> My bacula-dir.conf file has this section:
>
> # Generic catalog service
> Catalog {
> Name = MyCatalog
> dbname = bacula; user = bacula; password = ""
> }
>
> ...
>
> # ./grant_mysql_privileges -p
> (big permissions table prints)
> Privileges for bacula gran
Has anyone got any other ideas about this one? I have searched for
the error message returned by the bacula-dir start script, and found
many cases all with different causes. Is there any way to get more
specific error information, making the director start up in debug or
verbose mode? A log file
On Wed, Apr 25, 2007 at 02:53:46PM -0400, Frank Sweetser wrote:
> On Wed, Apr 25, 2007 at 11:17:23AM -0700, John J. Stimson-III wrote:
> > # Generic catalog service
> > Catalog {
> > Name = MyCatalog
> > dbname = bacula; user = bacula; password = ""
>
> This looks like you've configured bacula
On Wed, Apr 25, 2007 at 11:17:23AM -0700, John J. Stimson-III wrote:
> # Generic catalog service
> Catalog {
> Name = MyCatalog
> dbname = bacula; user = bacula; password = ""
This looks like you've configured bacula to connect to the mysql server with an
empty password, which is not the same
I am new to both bacula and mysql and I need some suggestions about
how to further diagnose this problem. I cannot get the bacula
director daemon to start. The mqsqld is running and the database
generation scripts are able to connect as user root (with a password)
as well as user bacula (with no