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. --------------------------------------------------------------- This was an upgrade from 1.38.9-10. The first error, the one referring to line 18, looks as if it might be a problem with the install scripts, and may not be related to the original bug. That error might have caused the later ones. Alternately, the fact that I setup the database somewhat behind the back of the config system may explain all the errors, and particularly the later ones. My original response of "no" to "setup new database with dbconfig" (not the original words, but it was the intent) may be messing things up here. Or, the presence of multiple versions of postgres running on my machine could be causing confusion. Any hints? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
