[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924881: marked as done (postgresql: buster upgrade breaks older postgresql (9.6) and newer postgresql (11) is also inoperative)

Your message dated Mon, 28 Dec 2020 14:40:15 +0000
with message-id <E1ktth1-0001QL-Kh@fasolo.debian.org>
and subject line Bug#924881: fixed in ssl-cert 1.1.0
has caused the Debian Bug report #924881,
regarding postgresql: buster upgrade breaks older postgresql (9.6) and newer postgresql (11) is also inoperative
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 owner@bugs.debian.org
immediately.)


-- 
924881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924881
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: postgresql
Version: 11+200
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Maintainer,

Upgraded to buster over the last 24 hours, including cleaning up configuration,
and now obsolete packages.  Stuck trying to get postgresql functional.  Been
through several previous postgresql upgrades, and know I need to upgrade the
old cluster manually, but I don't get the old or new cluster up.

9,6 journal entires, including from before/during upgrade
- ---8<---
Mar 09 21:40:55 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 09 21:40:57 monster systemd[1]: Started PostgreSQL Cluster 9.6-main.
Mar 16 20:07:03 monster systemd[1]: Stopping PostgreSQL Cluster 9.6-main...
Mar 16 20:07:04 monster systemd[1]: Stopped PostgreSQL Cluster 9.6-main.
Mar 16 20:07:04 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 16 20:07:06 monster systemd[1]: Started PostgreSQL Cluster 9.6-main.
Mar 16 20:07:18 monster systemd[1]: Stopping PostgreSQL Cluster 9.6-main...
Mar 16 20:07:19 monster systemd[1]: Stopped PostgreSQL Cluster 9.6-main.
Mar 16 20:07:19 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 16 20:07:21 monster systemd[1]: Started PostgreSQL Cluster 9.6-main.
Mar 17 11:56:10 monster systemd[1]: Stopping PostgreSQL Cluster 9.6-main...
Mar 17 11:56:11 monster systemd[1]: postgresql@9.6-main.service: Succeeded.
Mar 17 11:56:11 monster systemd[1]: Stopped PostgreSQL Cluster 9.6-main.
- -- Reboot --
Mar 17 11:57:21 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 17 11:57:22 monster postgresql@9.6-main[1380]: The PostgreSQL server failed to start. Please check the log output:
Mar 17 11:57:22 monster postgresql@9.6-main[1380]: 2019-03-17 16:57:21 GMT FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 17 11:57:22 monster postgresql@9.6-main[1380]: 2019-03-17 16:57:21 GMT LOG:  database system is shut down
Mar 17 11:57:22 monster systemd[1]: postgresql@9.6-main.service: Can't open PID file /run/postgresql/9.6-main.pid (yet?) after start: No such file or directory
Mar 17 11:57:22 monster systemd[1]: postgresql@9.6-main.service: Failed with result 'protocol'.
Mar 17 11:57:22 monster systemd[1]: Failed to start PostgreSQL Cluster 9.6-main.
- -- Reboot --
Mar 17 13:10:58 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 17 13:10:59 monster postgresql@9.6-main[1324]: The PostgreSQL server failed to start. Please check the log output:
Mar 17 13:10:59 monster postgresql@9.6-main[1324]: 2019-03-17 18:10:58 GMT FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 17 13:10:59 monster postgresql@9.6-main[1324]: 2019-03-17 18:10:58 GMT LOG:  database system is shut down
Mar 17 13:10:59 monster systemd[1]: postgresql@9.6-main.service: Can't open PID file /run/postgresql/9.6-main.pid (yet?) after start: No such file or directory
Mar 17 13:10:59 monster systemd[1]: postgresql@9.6-main.service: Failed with result 'protocol'.
Mar 17 13:10:59 monster systemd[1]: Failed to start PostgreSQL Cluster 9.6-main.
Mar 17 13:50:18 monster systemd[1]: Starting PostgreSQL Cluster 9.6-main...
Mar 17 13:50:19 monster postgresql@9.6-main[21028]: The PostgreSQL server failed to start. Please check the log output:
Mar 17 13:50:19 monster postgresql@9.6-main[21028]: 2019-03-17 18:50:19 GMT FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 17 13:50:19 monster postgresql@9.6-main[21028]: 2019-03-17 18:50:19 GMT LOG:  database system is shut down
Mar 17 13:50:19 monster systemd[1]: postgresql@9.6-main.service: Can't open PID file /run/postgresql/9.6-main.pid (yet?) after start: No such file or directory
Mar 17 13:50:19 monster systemd[1]: postgresql@9.6-main.service: Failed with result 'protocol'.
Mar 17 13:50:19 monster systemd[1]: Failed to start PostgreSQL Cluster 9.6-main.
- --->8---

11 journal entries, after upgrade (didn't have it before)
- ---8<---
% journalctl -u postgresql@11-main.service
- -- Logs begin at Sat 2018-02-24 00:07:52 CST, end at Sun 2019-03-17 16:57:35 CDT. --
Mar 16 20:58:20 monster systemd[1]: Starting PostgreSQL Cluster 11-main...
Mar 16 20:58:20 monster postgresql@11-main[24594]: Error: /usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D /var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s -o  -c config_file="/etc/postgresql/11/main/postgresql.conf"  exited with status 1:
Mar 16 20:58:20 monster postgresql@11-main[24594]: 2019-03-16 20:58:20.838 CDT [24599] FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 16 20:58:20 monster postgresql@11-main[24594]: 2019-03-16 20:58:20.839 CDT [24599] LOG:  database system is shut down
Mar 16 20:58:20 monster postgresql@11-main[24594]: pg_ctl: could not start server
Mar 16 20:58:20 monster postgresql@11-main[24594]: Examine the log output.
Mar 16 20:58:20 monster systemd[1]: postgresql@11-main.service: PID file /run/postgresql/11-main.pid not readable (yet?) after start: No such file or directory
Mar 16 20:58:20 monster systemd[1]: Failed to start PostgreSQL Cluster 11-main.
Mar 16 20:58:20 monster systemd[1]: postgresql@11-main.service: Unit entered failed state.
Mar 16 20:58:20 monster systemd[1]: postgresql@11-main.service: Failed with result 'resources'.
- -- Reboot --
Mar 17 11:57:21 monster systemd[1]: Starting PostgreSQL Cluster 11-main...
Mar 17 11:57:21 monster postgresql@11-main[1349]: Error: /usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D /var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s -o  -c config_file="/etc/postgresql/11/main/postgresql.conf"  exited with status 1:
Mar 17 11:57:21 monster postgresql@11-main[1349]: 2019-03-17 11:57:21.786 CDT [1610] FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 17 11:57:21 monster postgresql@11-main[1349]: 2019-03-17 11:57:21.786 CDT [1610] LOG:  database system is shut down
Mar 17 11:57:21 monster postgresql@11-main[1349]: pg_ctl: could not start server
Mar 17 11:57:21 monster postgresql@11-main[1349]: Examine the log output.
Mar 17 11:57:21 monster systemd[1]: postgresql@11-main.service: Can't open PID file /run/postgresql/11-main.pid (yet?) after start: No such file or directory
Mar 17 11:57:21 monster systemd[1]: postgresql@11-main.service: Failed with result 'protocol'.
Mar 17 11:57:21 monster systemd[1]: Failed to start PostgreSQL Cluster 11-main.
- -- Reboot --
Mar 17 13:10:58 monster systemd[1]: Starting PostgreSQL Cluster 11-main...
Mar 17 13:10:58 monster postgresql@11-main[1341]: Error: /usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D /var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s -o  -c config_file="/etc/postgresql/11/main/postgresql.conf"  exited with status 1:
Mar 17 13:10:58 monster postgresql@11-main[1341]: 2019-03-17 13:10:58.636 CDT [1588] FATAL:  could not load server certificate file "/etc/ssl/certs/ssl-cert-snakeoil.pem": ee key too small
Mar 17 13:10:58 monster postgresql@11-main[1341]: 2019-03-17 13:10:58.636 CDT [1588] LOG:  database system is shut down
Mar 17 13:10:58 monster postgresql@11-main[1341]: pg_ctl: could not start server
Mar 17 13:10:58 monster postgresql@11-main[1341]: Examine the log output.
Mar 17 13:10:58 monster systemd[1]: postgresql@11-main.service: Can't open PID file /run/postgresql/11-main.pid (yet?) after start: No such file or directory
Mar 17 13:10:58 monster systemd[1]: postgresql@11-main.service: Failed with result 'protocol'.
Mar 17 13:10:58 monster systemd[1]: Failed to start PostgreSQL Cluster 11-main.
- --->8---

Tried swapping /etc/ssl/certs/ssl-cert-snakeoil.pem for another .pem I had
hanging around (ssl-cert-snakeoil.pem.broken) which was larger, and it didn't
change the error message

I expected 11 to come up, even if 9.6 needed me to manually massage the
configuration.  Didn't expect to have to change the 9.6 configuration, either,
but I only remember the 9.x line of upgrades clearly, so having to updated the
configuration after a major version change is reasonable.

- -- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages postgresql depends on:
ii  postgresql-11  11.2-2

postgresql recommends no packages.

Versions of packages postgresql suggests:
pn  postgresql-doc  <none>

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iHQEARECADQWIQTFhn3a8g2plxzZYyjnmmovsbVAWQUCXI7DmxYcYnNzQGlndWFu
YXN1aWNpZGUubmV0AAoJEOeaai+xtUBZ4Z4AmgKrR0toPOaOXvTiWPoQQ8aj3cUZ
AJ9Z/jlqJcsl55FyS+mYl8UPHQRuvQ==
=oCiB
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Source: ssl-cert
Source-Version: 1.1.0
Done: Stefan Fritsch <sf@debian.org>

We believe that the bug you reported is fixed in the latest version of
ssl-cert, which is due to be installed in the Debian FTP archive.

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 924881@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Fritsch <sf@debian.org> (supplier of updated ssl-cert 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 28 Dec 2020 15:20:52 +0100
Source: ssl-cert
Architecture: source
Version: 1.1.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers <debian-apache@lists.debian.org>
Changed-By: Stefan Fritsch <sf@debian.org>
Closes: 924881
Changes:
 ssl-cert (1.1.0) unstable; urgency=medium
 .
   [ Stefan Fritsch ]
   * Remove obsolete openssl-blacklist suggests.
   * Add some autopkgtests. LP: #1679405
   * Create correct hash symlink. LP: #1324897
   * Automatically re-create the default snakeoil certificate if its key
     length is below 2048 bits or if the signature algorithm is not sha256.
     Closes: #924881
 .
   [ Bryce Harrington ]
   * Refactor make-ssl-cert a bit, add usage message.
   * Add --expiration-days option. LP: #1853021
Checksums-Sha1:
 9a259a81cadd448c8a96eef290f142352e6a7abd 1645 ssl-cert_1.1.0.dsc
 b6f21c5f3e445a7b69a14f5dab56d1c6f94aad73 31336 ssl-cert_1.1.0.tar.xz
 2fa7a4809455515c6f7b8595dbd0536b9331ba07 6778 ssl-cert_1.1.0_source.buildinfo
Checksums-Sha256:
 ce2bc71d68fce2fd571e5d718ac3060adb39703e2e11baada67e9386c8fb6386 1645 ssl-cert_1.1.0.dsc
 02afb973963cc7e5a45ccbf4393349a2cfb90a279378b2803f0068eaee207bce 31336 ssl-cert_1.1.0.tar.xz
 fb49256e65dd57e5fddbc6b8e47feb7de962a161a4834620d133be62ad4fb208 6778 ssl-cert_1.1.0_source.buildinfo
Files:
 e003b2bdc814672a48588de9aace3483 1645 utils optional ssl-cert_1.1.0.dsc
 00a64e367fe616b41083756757d58362 31336 utils optional ssl-cert_1.1.0.tar.xz
 6895627bf093117b312637a02d315789 6778 utils optional ssl-cert_1.1.0_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOpiNza8JqByyYYsxxodfNUHO/eAFAl/p6nQACgkQxodfNUHO
/eCGIA/8CUigG3D78p4cc2xQUMHyjqFxcpGzBpQBr2ruza8mJhCct7i1wYmwIm7z
kcSRPHMHRbWpvi6ZUdDIdzo/+ztMpwxehKeJi90CRzO61B/HGi25pZeJJt0PmbiY
gPF1mITUNgqrUaWzx+QGikWMZ1SdRPwID6Nl61lvdijSlADIvr2bUOaSo3EJDtB4
4aTv+8LGBpSxOSPig9f9kkXf5ywHrkVFLXPiIYZEqiVZ9N5uZCohw6KGm6nvYVpG
rCf46uFaaQg8hvvqBrIS7MD1C5tjxg7t2SdP2UEMIL40ET/QNW+rBExo8JbBFQpL
CYb3ETY8RmsjER/E6Rb8G9hGCgZDBLiuVqeXr36S7YKwXd3gNL444QFHBXe7kLeL
6X48dLcIwW9nDSGiTSkvlxg9sd/X/lMZd3og0rlWJScqrXjrOZyUfgXpXH7bQy30
e0JoIQTZsM4h78qr0tAXAS5BHMM3jpJDaQWAFAaX3F8iqkBfp6bq28gT5N/ce1Kl
UP7U9Iux7LE0BDynlp0o18EGVR0Q5yAVjrFb5iYstDFqmzn3kVrmsr7nCaexqjQk
E1fpFlXXT3jNXbHss74yCqu2O9XGgTPGCnqenVOyq28GoLDxMilA3Zj9RFjbzZf7
d1mFAk3y6xlOcCMTRNWVbwq6gPY8RHbHmdowbORTF9gS0wHyUW8=
=hsxZ
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: