On Fri, Jul 28, 2006 at 09:50:15PM -0700, Ross Boylan wrote: > I'm not sure all the issues below are related to the work-around, but > it seems likely that some are. So I'll report them under this bug. > > After the steps described in earlier mails, I did an upgrade. Here's > the log: > ------------------------------------------------------------------ > Setting up bacula-director-pgsql (1.38.11-1) ... > dbconfig-common: writing config to > /etc/dbconfig-common/bacula-director-pgsql.conf > Replacing config file /etc/dbconfig-common/bacula-director-pgsql.conf with > new version > Processing configuration .../usr/share/bacula-director/postinst-common: line > 18: /etc/bacula/bacula-dir.conf.dpkg-tmp: No such file or directory > Ok. > Stopping Bacula Director: bacula-dir. > Starting Bacula Director: 28-Jul 21:34 bacula-dir: Fatal error: Could not > open Catalog "MyCatalog", database "bacula". > 28-Jul 21:34 bacula-dir: Fatal error: postgresql.c:168 Unable to connect to > PostgreSQL server. > Database=bacula User=bacula > It is probably not running or your password is incorrect. > 28-Jul 21:34 bacula-dir ERROR TERMINATION > Please correct configuration file: /etc/bacula/bacula-dir.conf > failed. > ---------------------------------------------------------------
Maybe this is a simple problem. Postgres was being upgraded at the same time, and had not been setup when this error happened. I just did this: # invoke-rc.d bacula-director start Starting Bacula Director: bacula-dir. *If* that's all that's going on, my immediate problem is solved. How to make this work in general (i.e., package uses a database that is being upgraded at same time) require more knowledge of debian packaging than I have (maybe the package needs to pre-depends on the database?). Also, if this interpretation is correct, this is probably a separate bug from the original. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
