The original setup was one Sun280R machine running all the daemons and postgres.
This machine is responsible for backups.
Because the DB is too slow, and slow down the overall backup performance (from 10K it slows down to 1K...), I wanted to move Postgres.
So now, all bacula daemons are still running on Sun280R, and here I'm also running bconsole.
I only changed the configuration to connect to the new DB on the other host.
And actually the Director is connecting correctly.
Probably, the scheduling will run.
But I need to add volumes and run a job by hand now, to check performance, and bconsole is giving problems.
When I run bconsole, it correctly connects to the Director, and its prompt is there ready to accept commands. But any command comes out with that error.

Gabriele Bulfon - Sonicle S.r.l.
Tel +39 028246016 Int. 30 - Fax +39 028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com



----------------------------------------------------------------------------------

Da: Bill Moran <[EMAIL PROTECTED]>
A: Gabriele Bulfon <[EMAIL PROTECTED]>
Cc: bacula-users@lists.sourceforge.net
Data: 11 settembre 2006 13.41.23 CEST
Oggetto: Re: [Bacula-users] Bacula-dir and remote Postgres

Gabriele Bulfon <[EMAIL PROTECTED]> wrote:

> Hello,
> after discovering that Postgres is too slow on Sun 280R machines forBacula management, I decided to test one of them and have the PostgresDB run on another faster Solaris machine on the LAN.
> So I prepared the new DB from scratch, modified my original bacula-dir.conf to connect to the new DB host :
> Catalog {
> Name = MyCatalog
> dbname = bacula;
> user = bacula;
> password = "bacula"
> DB Address = myhost.mydomain.com
> DB Port = 5432
> }
> Now I see the Director starts on the new DB (the old one is down), but.......
> ....if I run bconsole as before on the Director's machine, any command hangs for a while and then says:
> Could not open database "bacula".
> postgresql.c:168 Unable to connect to PostgreSQL server.
> Database=bacula User=bacula
> It is probably not running or your password is incorrect.
> I am absolutely sure that Director connects to the DB, because debug is enabled, and I can see the Director is ok at startup.
> Infact, if I shutdown the remote DB, Directors complains and does not start up.
> ...what is my problem?!?

Are you sure you're only running 1 director? Are you sure bconsole is
configured to connect to the director that's able to talk to the database?

Without more details, those are the best guesses I've got right now
Based on your narrative, I was confused as to where the director is now
running -- is it on the database machine or the 280R?

--
Bill Moran

Be calm.

Morpheus




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to