Your message dated Sun, 25 Sep 2005 17:23:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329214: postgresql: Security update on template0 fails
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Sep 2005 14:19:06 +0000
>From [EMAIL PROTECTED] Tue Sep 20 07:19:06 2005
Return-path: <[EMAIL PROTECTED]>
Received: from port31.ds1-gl.adsl.cybercity.dk (imap.irs-mail.com)
[212.242.181.96]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EHixd-0004sG-00; Tue, 20 Sep 2005 07:19:06 -0700
Received: from srvdk04.irs-mail.com (unknown [192.168.11.14])
by imap.irs-mail.com (Postfix) with ESMTP id D71C726F77
for <[EMAIL PROTECTED]>; Tue, 20 Sep 2005 16:19:03 +0200 (CEST)
Received: by srvdk04.irs-mail.com (Postfix, from userid 1000)
id BCB4D9940; Tue, 20 Sep 2005 16:19:02 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Per Jensen <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgresql: Security update on template0 fails
X-Mailer: reportbug 3.8
Date: Tue, 20 Sep 2005 16:19:02 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: postgresql
Version: 7.4.7-6sarge1
Severity: normal
When doing a 'aptitude dist-upgrade' the following messages appear:
Errors were encountered while processing:
postgresql
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ack! Something bad happened while installing packages. Trying to recover:
Setting up postgresql (7.4.7-6sarge1) ...
Applying security update in database gforge...success
Applying security update in database pcic...success
Applying security update in database template1...success
Applying security update in database template0...
dpkg: error processing postgresql (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
postgresql
Is seems the update is being applied to template0. It is not possible
to connect to template0. That might explain the missing "success" message
on template0.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages postgresql depends on:
ii adduser 3.63 Add and remove users and groups
ii debconf [debconf 1.4.30.13 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii dpkg 1.10.28 Package maintenance system for Deb
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libcomerr2 1.37-2sarge1 common error description library
ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libperl5.8 5.8.4-8 Shared Perl library
ii libpq3 7.4.7-6sarge1 PostgreSQL C client library
ii libreadline4 4.3-11 GNU readline and history libraries
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii postgresql-clien 7.4.7-6sarge1 front-end programs for PostgreSQL
ii procps 1:3.2.1-2 The /proc file system utilities
ii python2.3 2.3.5-3 An interactive high-level object-o
ii ucf 1.17 Update Configuration File: preserv
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- debconf information:
* postgresql/initdb/location: /var/lib/postgres/data
postgresql/upgrade/preserve_location: $PGDATA/..
* postgresql/settings/day_month_order: European
postgresql/upgrade/policy: true
* postgresql/settings/locale: da_DK.iso88591
postgresql/enable_lang: true
* postgresql/purge_data_too: false
postgresql/very_old_version_warning: true
postgresql/upgrade/dump_location: $PGDATA/..
postgresql/convert-pg_hba.conf: true
---------------------------------------
Received: (at 329214-done) by bugs.debian.org; 25 Sep 2005 15:24:02 +0000
>From [EMAIL PROTECTED] Sun Sep 25 08:24:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from box79162.elkhouse.de [213.9.79.162]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EJYMD-0004Ng-00; Sun, 25 Sep 2005 08:24:02 -0700
Received: from localhost.localdomain (unknown [195.227.105.180])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Martin Pitt (workstation)", Issuer "piware CA" (verified
OK))
by box79162.elkhouse.de (Postfix) with ESMTP id EBFA61F847D;
Sun, 25 Sep 2005 17:23:28 +0200 (CEST)
Received: by localhost.localdomain (Postfix, from userid 1000)
id 3DE0012F71; Sun, 25 Sep 2005 17:23:39 +0200 (CEST)
Date: Sun, 25 Sep 2005 17:23:39 +0200
From: Martin Pitt <[EMAIL PROTECTED]>
To: Per Jensen <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#329214: postgresql: Security update on template0 fails
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
HAS_PACKAGE autolearn=ham version=2.60-bugs.debian.org_2005_01_02
--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: postgresql-common
Version: 20
Hi Per!
Per Jensen [2005-09-20 16:19 +0200]:
> Applying security update in database gforge...success
> Applying security update in database pcic...success
> Applying security update in database template1...success
> Applying security update in database template0...
> dpkg: error processing postgresql (--configure):
> subprocess post-installation script returned error exit status 2
> Errors were encountered while processing:
> postgresql
>=20
>=20
> Is seems the update is being applied to template0. It is not possible=20
> to connect to template0. That might explain the missing "success" message
> on template0.
Actually the post installation script makes an effort to temporarily
enable connection to template0, apply the update, and revert the
"enable connection" change. This works for the common case.
The packages in sid are more robust against that, will print a better
error message, and not cause the whole package installation to fail,
so I'm closing this bug in sid.
Since we can not fix such bugs in stable releases, can you please
temporarily change your ACLs/configuration to allow template0
connection to user "postgres" in your setup, reconfigure the
postgresql package (dpkg --configure -a) and check whether it succeeds
then?
Thanks,
Martin
--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDNsD7DecnbV4Fd/IRAqR9AJ4tI6kro8nFAkk2xE257plb7JIJFQCgpGMY
i6XBQTYRj4XNzrMUidrC7Oo=
=nUxt
-----END PGP SIGNATURE-----
--jq0ap7NbKX2Kqbes--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
