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-----
