In response to Gabriele Bulfon <[EMAIL PROTECTED]>: > Hello, > I open again the question about Bacula working on Postgres. > This time, I really need to have Director and Postgres run on two different > machines. > The reason: I only have one Solaris machine and one Windows machine, so I > cannot move the Director to the Windows machine together with Postgres (as > far as I know, the Director is still not supported on Windows). > What happens is that once I add the needed entries to the bacula-dir.conf to > connect to the new machine (DB Address and DB Port), Director starts (and > with log enabled to 500, I can see a lot of queries correctly handled), but > when I run bconsole on the Director, the Director initially responds with the > prompt, then any command that needs DB access (such as "list volumes") hangs > for some seconds and then fails saying that it cannot connect to the DB. > If I look at the log, I can see some timeout failures. > How can I investigate more this? Why the first queries go through correctly, > and then they fail with bconsole? > Please help...I really need to move the DB on the other machine....
Help: 1) Provide the logs you captured, not your interpretation of them. Nobody is going to be able to diagnose "I can see some timeout failures" 2) Bump up connection logging on the PostgreSQL server. You'll want to provide those logs as well. 3) Put some effort into formatting your emails so they're readable. -- Bill Moran Collaborative Fusion Inc. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
