[Pkg-postgresql-public] Bug#882409: postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres"

[Andreas Beckmann]

Package: postgresql-9.4
Version: 9.4.12-0+deb8u1
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts

Hi,

this issue has been showing up on piuparts for a long time already, but
I never took the time to analyze it further since I expected this to be
rather a problem in the piuparts postgresql handling, but this does
not seem to be case.

The script we use in piuparts to upgrade the postgresql database on
version bumps is here:
https://anonscm.debian.org/git/piuparts/piuparts.git/tree/custom-scripts/scripts/pre_distupgrade_zz_database-server#n92

The essential part here should be

		echo "Upgrading PostgreSQL Cluster from ${from} to ${to}"
		pg_dropcluster ${to} main --stop
		pg_upgradecluster -v ${to} ${from} main
		pg_dropcluster ${from} main

I don't know whether this is the correct approach, but it is what I
did after reading the documentation. Better solutions welcome.
It works in most cases (squeeze->wheezy, jessie->stretch, stretch->buster
on both amd64 and i386) except wheezy->jessie on amd64 (but i386 is fine).

  Upgrading PostgreSQL Cluster from 9.1 to 9.4
  psql: FATAL:  Peer authentication failed for user "postgres"
  psql: FATAL:  Peer authentication failed for user "postgres"
  Use of uninitialized value $out in pattern match (m//) at /usr/share/perl5/PgCommon.pm line 915.
  psql: FATAL:  Peer authentication failed for user "postgres"
  Use of uninitialized value $out in pattern match (m//) at /usr/share/perl5/PgCommon.pm line 921.
  Use of uninitialized value $ctype in scalar chomp at /usr/share/perl5/PgCommon.pm line 924.
  Use of uninitialized value $collate in scalar chomp at /usr/share/perl5/PgCommon.pm line 925.
  Error: could not get cluster locales

The strange part is that the same test succeeds for i386 (on the
same amd64 host where the amd64 test fails):

  Upgrading PostgreSQL Cluster from 9.1 to 9.4
  Stopping old cluster...
  Disabling connections to the old cluster during upgrade...
  Restarting old cluster with restricted connections...
  Creating new cluster 9.4/main ...
    config /etc/postgresql/9.4/main
    data   /var/lib/postgresql/9.4/main
    locale C
    port   5433
  Disabling connections to the new cluster during upgrade...
  Roles, databases, schemas, ACLs...
  Fixing hardcoded library paths for stored procedures...
  Upgrading database postgres...
  Analyzing database postgres...
  Fixing hardcoded library paths for stored procedures...
  Upgrading database template1...
  Analyzing database template1...
  Re-enabling connections to the old cluster...
  Re-enabling connections to the new cluster...
  Copying old configuration files...
  Copying old start.conf...
  Copying old pg_ctl.conf...
  Copying old server.crt...
  Copying old server.key...
  Stopping target cluster...
  Stopping old cluster...
  Disabling automatic startup of old cluster...
  Configuring old cluster to use a different port (5433)...
  Starting target cluster on the original port...
  Success. Please check that the upgraded cluster works. If it does,
  you can remove the old cluster with
  
    pg_dropcluster 9.1 main


I'm attaching the full wheezy->jessie logs for amd64 and i386.

The corresponding piuparts failues are listed here:
https://piuparts.debian.org/wheezy2jessie/unclassified_failures.html


Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgres-w2j.amd64.log.gz
Type: application/gzip
Size: 30504 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20171122/7f492a11/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgres-w2j.i386.log.gz
Type: application/gzip
Size: 57012 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20171122/7f492a11/attachment-0003.bin>