Package: postgresql-common Version: 200+deb10u3 Severity: normal Hello,
When the old cluster has SSL turned off, but when SSL is broken enough to prevent PG from starting, pg_upgradecluster fails. This is because pg_upgradecluster is started before the data copy with SSL turned on. And with SSL broken won't start. It is not entirely unusual that SSL is broken. See, e.g., bug #924881. I am not sure how easy it is to break SSL in a way that prevents PG from starting but #924881 shows that it is possible. SSL is complicated enough that it has many ways to break. :-) The initial cluster startup for data copy is with pg_hba.conf in "trust" mode, so SSL is not needed for the copy step. Regards, Karl -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-common depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.71 ii lsb-base 10.2019051400 ii postgresql-client-common 200+deb10u3 ii procps 2:3.3.15-2 ii ssl-cert 1.0.39 ii ucf 3.0038+nmu1 Versions of packages postgresql-common recommends: ii e2fsprogs 1.44.5-1+deb10u2 ii logrotate 3.14.0-4 Versions of packages postgresql-common suggests: ii libjson-perl 4.02000-1 -- debconf information: postgresql-common/catversion-bump: * postgresql-common/ssl: true * postgresql-common/obsolete-major:
