Your message dated Tue, 08 Oct 2019 18:37:08 +0000 with message-id <e1ihum8-000ar5...@fasolo.debian.org> and subject line Bug#941985: fixed in perl 5.30.0-6 has caused the Debian Bug report #941985, regarding FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied 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 ow...@bugs.debian.org immediately.) -- 941985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: postgresql-11 Version: 11.5-3sid2 Severity: important Since yesterday postgresql@11-main.service fails to start and systemctl status ends with: postgresql@11-main.service: Failed with result 'protocol'. Failed to start PostgreSQL Cluster 11-main. In /var/log/postgresql/postgresql-11-main.log I see this: 2019-10-07 13:29:48.816 CEST [1058] LOG: listening on IPv6 address "::1", port 5432 2019-10-07 13:29:48.816 CEST [1058] LOG: listening on IPv4 address "127.0.0.1", port 5432 2019-10-07 13:29:48.820 CEST [1058] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2019-10-07 13:29:48.845 CEST [1060] LOG: database system was shut down at 2019-10-07 07:54:57 CEST 2019-10-07 13:29:48.864 CEST [1058] LOG: database system is ready to accept connections 2019-10-07 13:29:49.395 CEST [1098] [unknown]@[unknown] LOG: incomplete startup packet 2019-10-07 13:43:20.898 CEST [1058] LOG: received fast shutdown request 2019-10-07 13:43:20.904 CEST [1058] LOG: aborting any active transactions 2019-10-07 13:43:20.905 CEST [1058] LOG: background worker "logical replication launcher" (PID 1066) exited with exit code 1 2019-10-07 13:43:20.905 CEST [1061] LOG: shutting down 2019-10-07 13:43:20.979 CEST [1058] LOG: database system is shut down 2019-10-07 13:44:00.487 CEST [1086] FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied 2019-10-07 13:44:00.487 CEST [1086] LOG: database system is shut down pg_ctl: could not start server Examine the log output. And then the last 4 lines get repeated many times. A bit further up the log file, when postgresql-11 got upgraded to this version, there are these lines: 2019-10-06 23:23:42.714 CEST [2172] diederik@akonadi_diederik FATAL: terminating connection due to administrator command 2019-10-06 23:23:42.714 CEST [1054] LOG: background worker "logical replication launcher" (PID 1064) exited with exit code 1 The FATAL line appears ~30 times, all within the same second. Downgrading postgresql-11 and postgresql-client-11 to the version in testing (11.5-2+b1) did not fix the issue. I then tried to access /etc/ssl/private/ssl-cert-snakeoil.key (as user postgres) and indeed couldn't access that file. User postgres is in group ssl-cert and this was the permissions to the private dir: drwx--x--- 2 root ssl-cert 4096 okt 7 18:13 private When I changed it to this: drwxr-x--- 2 root ssl-cert 4096 okt 7 18:13 private I could access the ssl-cert-snakeoil.key file as user postgres, but this did not resolve the issue. It kept reporting "Permission denied". Since 2019-10-07 13:44:00.487 CEST, I only get those last 4 lines. I don't know if it's relevant, but together with the upgrade of postgresql-11, apparmor and llvm got upgraded. And the FATAL line appeared when perl got upgraded from 5.28 to 5.30. I mention those other upgrades as downgrading the postgresql packages to the testing versions did not fix the issue (which it often does). As I'm therefor not 100% sure the issue is (directly) in the postgresql packages, I set the severity to important instead of grave. Anyway, the result is no running postgresql, thus no akonadi, thus no working kmail for me. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-11 depends on: ii debconf [debconf-2.0] 1.5.73 ii libc6 2.29-2 ii libgcc1 1:9.2.1-8 ii libgssapi-krb5-2 1.17-6 ii libicu63 63.2-2 ii libldap-2.4-2 2.4.48+dfsg-1+b1 ii libllvm9 1:9-2 ii libpam0g 1.3.1-5 ii libpq5 12.0-1+b1 ii libselinux1 2.9-2+b2 ii libssl1.1 1.1.1d-1 ii libstdc++6 9.2.1-8 ii libsystemd0 242-7 ii libuuid1 2.34-0.1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxslt1.1 1.1.32-2.1 ii locales 2.29-2 ii postgresql-client-11 11.5-3sid2 ii postgresql-common 207 ii ssl-cert 1.0.39 ii tzdata 2019c-3 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages postgresql-11 recommends: ii sysstat 12.0.6-1 postgresql-11 suggests no packages. -- debconf information: postgresql-11/postrm_purge_data: true
--- End Message ---
--- Begin Message ---Source: perl Source-Version: 5.30.0-6 We believe that the bug you reported is fixed in the latest version of perl, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni <nt...@debian.org> (supplier of updated perl 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 08 Oct 2019 20:25:35 +0300 Source: perl Architecture: source Version: 5.30.0-6 Distribution: unstable Urgency: medium Maintainer: Niko Tyni <nt...@debian.org> Changed-By: Niko Tyni <nt...@debian.org> Closes: 941985 Changes: perl (5.30.0-6) unstable; urgency=medium . * Apply upstream patch fixing a regression in group id parsing that broke setting supplementary group IDs. (Closes: #941985) Checksums-Sha1: 65b0c4c9300925093f939a2ab4b419e000686d75 2983 perl_5.30.0-6.dsc 3a63ae2e0e74e460ece01ab319b3358b6168aa45 161256 perl_5.30.0-6.debian.tar.xz Checksums-Sha256: 3d480d10a1368303d235abd2b986d3f3cd1d56f64150867dba4041eba7b4a2ec 2983 perl_5.30.0-6.dsc 2d65fb2db865784b04ee99917b4232c72b28b8e62cc9599978fc1839f1fba808 161256 perl_5.30.0-6.debian.tar.xz Files: 0b2026f08aacba87cee98cbc3be84684 2983 perl standard perl_5.30.0-6.dsc 3d5fcf3b0d17523e3a939c25cf0e2af9 161256 perl standard perl_5.30.0-6.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAl2c0NERHG50eW5pQGRl Ymlhbi5vcmcACgkQLsD/s7cwGx/8/A//YZ+Z3H5kRMfkGn31wl1fdsGPVFVPY3Gv qUhebqnMgYy6uf2YTgwN0ZjqJGs2ZLKPx1ifC1YEy86MZZ1DAHxwViMR4lRUe2R2 cM9GqJXrlcBmjz46mD98FR2Q6mXn0GEw7GguLLaj1mw+MobH7beuDcqaBG8iXlWH dpl9hAgMZAce5mj9b2qcWvclnol2YIll6KaXx8FccFoVop8z+tCmp9Diby3fRn0q j5DBh3z9Fszm6mGZdepxB9dyKqXXBneWZAXUB8kS6HZRnLU790YLBY2YnLC4NiDH Jpax4BXcRFQwcBGbHNUp5SDrWrk6xJOwDd1kZ3465klIkHx0S7Z4jvf4pEQVZSqo ok49L3pK3sB5B6ajeNYBFd0uhQajtxt8CTKK/1ySCdHTBLPqPpTw0vw719MMS5/H 56pKSERo6qMaB0ofsnh28mpbgZiIl2Hdmd0MjVL8T05L9U70dxjSIQ4tPfAAFcTg /IT+TtuAuORJH7omCIC27vaTsJCNhxA4quete83JPKL2kht6wJRcxvBbQ5zMjeTF KMy9w5983REfbmnGHtjZUODNZUwtCMmlo+/LNP4bODrbkrF+7uh2C8Wg+4jOMGib tcDp/+3bho+7BDdNVSD+mBBheVfuqGFr3oCVD8Ri3NrMsbGpDKRYY4UCcxgMRKoE cjK4sg96RGI= =2gnT -----END PGP SIGNATURE-----
--- End Message ---
