Package: postgresql-13 Version: 13.1-1+b1 Severity: normal Short bug report: ================= from the postregsql log: 2021-01-11 18:20:07.039 CET [969840] LOG: PostgreSQL 13.1 (Debian 13.1-1+b1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.0-18) 10.2.0, 64-bit startet 2021-01-11 18:20:07.039 CET [969840] LOG: erwarte Verbindungen auf IPv4-Adresse »127.0.0.1«, Port 5434
(in english: expecting connection on IPv4 address "127.0.0.1", port 5434).
2021-01-11 18:20:07.078 CET [969840] LOG: Datenbanksystem ist bereit, um
Verbindungen anzunehmen
(in english: Database system is ready to accept connections)
However:
netstat -nlp | grep 5432
<no output>
And clients complain that connection is not possible on that port.
Long version: (aka: What lead up to this)
=============
I'm running postgresql for ages. Until a few days ago I had version
11, 12 and 13 installed. The client was from 13, the server was
running version 11. I intended to upgrade the server but made a
mistake: I dropped the cluster on version 11, not 13 to prepare the
upgrade.
As I'm regularly backing up (including database dumps) I decided to
simply (probably bad idea?) import the dump into version 13. However,
I could not connect to the database afterwards.
I removed postgresql 11 and 12, but no change.
After (finally) reading the man page of pg_wrapper, I could connect.
However, I needed to explicitly pass "--cluster 13/main" to psql. I
did this, but found out that I could work around this explicit
flag by adding
helge * 13 main *
to /etc/postgresql-common/user_clusters
(This file was untouched before).
However, this does not help if I try to acces via other methods, like
in perl scripts (same user) or in PHP scripts (different user, added
that in user_clusters as well). So I'm now trying to track this down,
but to no avail so far.
What really makes me think in circles is that the server happily tells
me he is listening on port 5434 but actually does not, so I'm a bit
lost how to proceed debugging this.
If you have an idea, besides the bug reported above, how to revert to
the 11 behaviour (simply connecting to the db server running on port
5434 without needing to edit user_clusters and other files) I would be
more than happy :-))
[I have modified pg_hba.conf, but I tried both with the stock install
and the version of "pg_hba.conf" I used with postgresql-11, no change
detected both in behaviour and (non) error output]
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.3 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postgresql-13 depends on:
ii debconf [debconf-2.0] 1.5.74
ii libc6 2.31-9
ii libgcc-s1 10.2.1-3
ii libgssapi-krb5-2 1.18.3-4
ii libicu67 67.1-5
ii libldap-2.4-2 2.4.56+dfsg-1
ii libllvm11 1:11.0.0-5+b1
ii libpam0g 1.3.1-5
ii libpq5 13.1-1+b1
ii libselinux1 3.1-2+b2
ii libssl1.1 1.1.1i-1
ii libstdc++6 10.2.1-3
ii libsystemd0 247.2-4
ii libuuid1 2.36.1-4
ii libxml2 2.9.10+dfsg-6.3+b1
ii libxslt1.1 1.1.34-4
ii locales 2.31-9
ii postgresql-client-13 13.1-1+b1
ii postgresql-common 223
ii ssl-cert 1.1.0
ii tzdata 2020f-1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages postgresql-13 recommends:
pn sysstat <none>
postgresql-13 suggests no packages.
-- debconf information:
postgresql-13/postrm_purge_data: true
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
