Your message dated Sun, 21 Nov 2010 13:02:28 +0000
with message-id <[email protected]>
and subject line Bug#509050: fixed in postgresql-common 112
has caused the Debian Bug report #509050,
regarding pg_upgradecluster fails if cluster does not stop
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
509050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509050
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-8.3
Version: 8.3.5-1
Severity: normal
Upgrading server from Etch to Lenny (before release of lenny).
The Postgres upgrade from 7.4 to 8.3 was well handled and excellently
documented (good work by packagers and Postgres developers).
However on my system on running "pg_upgradecluster 7.4 main" failed because
Postgres was in use by an Apache fastcgi script. In the end I "kill -9" the
remaining Postgres 7.4 processes, and found that postgres 8.3 cluster was
correctly configured when I started it manually.
I would file this as minor, but it is more than cosmetic, but shouldn't be a
problem for most users.
Last bit of output from "pg_upgradecluster"
Stopping target cluster...
Stopping old cluster...
pg_ctl: postmaster does not shut down
Disabling automatic startup of old cluster...
Configuring old cluster to use a different port (5433)...
Starting target cluster on the original port...
Error: Port conflict: cluster 7.4/main is already running on port 5432
Error: Could not start target cluster; please check configuration and log files
Probably obvious to more experienced Postgres admins. Should the documentation
recommend disabling all clients, or should the script check and be more
aggressive closing down the database? In this case I should have disabled all
the clients manually before the update to avoid loss of data (but it was only a
test server).
Either way I'm very impressed, I've had far more difficult upgrades of very
expensive proprietary databases.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-6-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages postgresql-8.3 depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libcomerr2 1.41.3-1 common error description library
ii libkrb53 1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries
ii libpam0g 1.0.1-4 Pluggable Authentication Modules l
ii libpq5 8.3.5-1 PostgreSQL C client library
ii libssl0.9.8 0.9.8g-14 SSL shared libraries
ii libxml2 2.6.32.dfsg-5 GNOME XML library
ii locales 2.7-16 GNU C Library: National Language (
ii postgresql-client-8.3 8.3.5-1 front-end programs for PostgreSQL
ii postgresql-common 94 PostgreSQL database-cluster manage
ii ssl-cert 1.0.23 simple debconf wrapper for OpenSSL
ii tzdata 2008h-2 time zone and daylight-saving time
postgresql-8.3 recommends no packages.
Versions of packages postgresql-8.3 suggests:
ii pidentd [ident-server] 3.0.19.ds1-4 TCP/IP IDENT protocol server with
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 112
We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive:
postgresql-client-common_112_all.deb
to main/p/postgresql-common/postgresql-client-common_112_all.deb
postgresql-common_112.dsc
to main/p/postgresql-common/postgresql-common_112.dsc
postgresql-common_112.tar.gz
to main/p/postgresql-common/postgresql-common_112.tar.gz
postgresql-common_112_all.deb
to main/p/postgresql-common/postgresql-common_112_all.deb
postgresql-server-dev-all_112_all.deb
to main/p/postgresql-common/postgresql-server-dev-all_112_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt <[email protected]> (supplier of updated postgresql-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 21 Nov 2010 13:52:25 +0100
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all
Architecture: source all
Version: 112
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <[email protected]>
Changed-By: Martin Pitt <[email protected]>
Description:
postgresql-client-common - manager for multiple PostgreSQL client versions
postgresql-common - PostgreSQL database-cluster manager
postgresql-server-dev-all - extension build tool for multiple PostgreSQL
versions
Closes: 509050 591924
Changes:
postgresql-common (112) unstable; urgency=medium
.
* Urgency medium since this fixes an RC bug.
* debian/changelog: Fix changelog entry in version 111 for #597654: init
script priority was fixed to S19, not S29.
* pg_ctlcluster: Also pass additional pg_ctl arguments in "stop" and
"reload" mode.
* pg_ctlcluster: Pass correct exit code from pg_ctl in case of errors.
* PgCommon.pm, get_db_encoding(): Fix uninitialized variable if psql fails.
* t/040_upgrade.t: Check that pg_upgradecluster exits early and gracefully
if the old cluster does not stop (usually because there are still active
connections to it). This reproduces #509050.
* pg_upgradecluster: Move stopping of old cluster and disabling connections
to it much ealier, and properly fail without starting the upgrade.
(Closes: #509050)
* debian/postgresql-common.preinst: Remove obsolete init script from
postgresql-8.3 for upgrades from Lenny. It provides "postgresql" which is
also provided by our common init script, and insserv chokes on this. Our
common init script handles 8.3 as well and will just take over. Note that
this is a policy violation, but we can't clean up in -8.3 since that does
not exist any more in Squeeze. (Closes: #591924)
Checksums-Sha1:
00c5adf513200f5d0f6549c2f0b64d3578edbef6 1579 postgresql-common_112.dsc
24241ca6dfd99347c9251dbb396e045a059f005c 127045 postgresql-common_112.tar.gz
1fa84666e0ac5643a6559d4223b868183ff54e10 127264 postgresql-common_112_all.deb
75dade91bf98f8b1c096b5904cb35f0e670a9cae 56658
postgresql-client-common_112_all.deb
e1b176d9257ab6c49779f07aa74c837ee08c038b 42002
postgresql-server-dev-all_112_all.deb
Checksums-Sha256:
62e6c480458da2c493f1d4822621f13bcc1708533560a3c8a759b97d9179cb88 1579
postgresql-common_112.dsc
52a592feb33a2f7443defa8e20e8920b0df0b39b7b5ecc3e7679738549aab2a2 127045
postgresql-common_112.tar.gz
c622201906f985e30114aba0558a0ade40f96e8a427e57049f8cf53920911f47 127264
postgresql-common_112_all.deb
571531086fa8da704a58d75c2bb17baf1e27ada48368d583e67d0a1aba3aa32d 56658
postgresql-client-common_112_all.deb
cc6e9b7af4bf06f9ab53b6863f40fdcd97fd37f101164606b6feb01d685413da 42002
postgresql-server-dev-all_112_all.deb
Files:
27f5dd488b43675b5d34b9122af7dfc4 1579 database optional
postgresql-common_112.dsc
08dbc5b746da65d67c2536e0cac90dbd 127045 database optional
postgresql-common_112.tar.gz
14185c35df4d63caff02ab22ee559f09 127264 database optional
postgresql-common_112_all.deb
3c3f6c59ea7213553f9775161f03f426 56658 database optional
postgresql-client-common_112_all.deb
828780b410c4833181a4f3f722b59bd4 42002 database optional
postgresql-server-dev-all_112_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJM6RY9AAoJEPmIJawmtHufQScP/294Z/5S8TsnC4KYVsgy+obt
5VmVil1CkEsscZmL4ndohBfEFh77A2Ma+DKZtZKD/fAXrpReJvUsmBp9FP1qxggS
vKrP9UDqDWpDvwmRr2zGVFQgA3FsLy/KCkces10s51Vd2dWlobXsoSRdvaTiP0Rm
iqbkNAS0hJnLGSF2jLZ6rY0m4Slai/T43nrGh3KIv5wMPnI2mRLnbaXhYOUQduBk
in+UeI2wAJYTPl3O+jmkXGA+ZP2FlfLBfgL6qNjsIywBmz8sbNNZMIHkjmV6FXMF
9POUlv5eflWPjR/gD8sqSY9rLwvWjHCdOxMsB6/avEPvowxZuGcLk3m0EQbtK/+y
9ngmvyvAovExro4KWWQefW1TPWmZPE21+LdfGZzQyqbL7BSHLjFzc4iylq1Mvy4z
6BdnksJEQ2Rs42FXyImH/5kcLnAbpiexT9y4SuX+UAHixoto3GOirNbB9+QoHqxH
/qD2vLloSq+eGm93WD5o/dY5j4JKgyo5clGsv1dNWqFYDsqZ/nzeAk1bRw/4Ek6l
PxGIBy3bDoxShlmc3Zu/tEnuAEr1fKQTZzcdQagR1bRwMzYkrXtQ/zNMNwWkL7qc
uwFS4trYqDrybma/aeXjwh3+nVha1nEWmaePEOYS7T/ukC+WXDpglhwPR9ZS7S5/
Zb6dyD/hpCDIepWsX9QZ
=pYvi
-----END PGP SIGNATURE-----
--- End Message ---
