bacula-director-pgsql fails to purge if postgresql is not running
Bug #582755 reported by
edro4838
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: bacula
using packages from ubuntu release 10.4
package
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue May 18 17:54:33 2010
ErrorMessage: subprocess installed pre-removal script returned error exit status 10
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: bacula
Title: package bacula-
To post a comment you must log in.
Removing bacula- director- pgsql ... bacula- director- pgsql.bacula. 2010-05- 18-17.54. pgsql.Xtx4Aw. postgresql/ .s.PGSQL. 5432"? WARNING **: /build/ buildd/ glib2.0- 2.24.0/ gobject/ gsignal. c:3079: signal name `depressed' is invalid for instance `0x16e0e00' at /usr/share/ perl5/Debconf/ FrontEnd/ Gnome.pm line 120, <GEN0> line 11. director- pgsql remove: retrying. director- pgsql (--purge):
dbconfig-common: dumping pgsql database bacula to /var/tmp/
unable to connect to postgresql server.
error encountered dumping database:
psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/
GLib-GObject-
dbconfig-common: bacula-
dpkg: error processing bacula-
subprocess installed pre-removal script returned error exit status 10