No, the problem remains unsolved. I'm trying out one thing after the other
but to no avail. The next thing I tried out was:
r...@newglfs01 bin]# ./bacula start -d100
Starting the Bacula Storage daemon
bacula-sd: stored_conf.c:701-0 Inserting director res: newglfs01-mon
newglfs01-sd: jcr.c:140-0 read_last_jobs seek to 192
newglfs01-sd: jcr.c:147-0 Read num_items=0
newglfs01-sd: stored.c:528-0 calling init_dev /root/bakup
newglfs01-sd: dev.c:269-0 init_dev: tape=0 dev_name=/root/bakup
newglfs01-sd: stored.c:530-0 SD init done /root/bakup
newglfs01-sd: bnet_server.c:96-0 Addresses host[ipv4:0.0.0.0:9103]
Starting the Bacula File daemon
bacula-fd: filed_conf.c:448-0 Inserting director res: newglfs01-mon
newglfs01-fd: jcr.c:140-0 read_last_jobs seek to 192
newglfs01-fd: jcr.c:147-0 Read num_items=0
newglfs01-fd: filed.c:259-0 filed: listening on port 9102
newglfs01-fd: bnet_server.c:96-0 Addresses host[ipv4:0.0.0.0:9102]
Starting the Bacula Director daemon
bacula-dir: dird.c:177-0 Debug level = 100
bacula-dir: jcr.c:140-0 read_last_jobs seek to 192
bacula-dir: jcr.c:147-0 Read num_items=0
bacula-dir: mysql.c:101-0 db_open first time
bacula-dir: mysql.c:130-0 initdb ref=1 connected=0 db=0
bacula-dir: mysql.c:166-0 mysql_init done
[r...@newglfs01 bin]# bacula-dir: mysql.c:187-0 mysql_real_connect done
bacula-dir: mysql.c:189-0 db_user=bacula db_name=bacula db_password=
bacula-dir: dird.c:927 Could not open Catalog "MyCatalog", database
"bacula".
bacula-dir: dird.c:932 mysql.c:195 Unable to connect to MySQL server.
Database=bacula User=bacula
MySQL connect failed either server not running or your authorization is
incorrect.
bacula-dir: mysql.c:228-0 closedb ref=0 connected=0 db=0
15-Apr 12:57 bacula-dir ERROR TERMINATION
Please correct configuration file: /root/bacula/bin/bacula-dir.conf
And that's all. I think debug level 100 is pretty high and changing it to
500 and 1000 have had no impact whatsoever on the debug messages I'm
getting. Interestingly, with -d100 option, I don't have to run ./bconsole
for the bacula-dir process to die. It dies on its own within a few seconds.
Am getting desperate now for any help :)
Thanks and regards
Chandranshu
On Wed, Apr 15, 2009 at 12:36 PM, Maria McKinley <ma...@shadlen.org> wrote:
> Chandranshu . wrote:
>
>> This is exactly the problem I have reported in the other thread at
>> http://sourceforge.net/mailarchive/forum.php?thread_name=76a720440904141403r6602a127t8de767b943d7973e%40mail.gmail.com&forum_name=bacula-users<
>> http://sourceforge.net/mailarchive/forum.php?thread_name=76a720440904141403r6602a127t8de767b943d7973e%40mail.gmail.com&forum_name=bacula-users>
>> with slightly more details. Looks like something is broken in the setup.
>>
>> If it helps, I'm using mysql-5.0.45 on 64-bit Red Hat Linux and have tried
>> using users both with and w/o a password.
>>
>> Thanks and Regards
>> Chandranshu
>>
>
> yup, exactly the same problem. I can log into myql using the same
> name/password that is present in the bacula-dir.conf file, but from the
> config file it doesn't work. That thread ends rather abruptly, did you solve
> your problem?
>
> thanks,
> maria
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
