Date: Sun, 18 Oct 2020 11:30:42 +0000
From: bugzilla-noreply@freebsd.org
To: ports-bugs@FreeBSD.org
Subject: [Bug 250068] databases/postgres{12|13}-server: psql: error: could not connect to server: server closed the connection unexpectedly
Message-ID: <bug-250068-7788-rLtiNtLQtf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-250068-7788@https.bugs.freebsd.org/bugzilla/>
References: <bug-250068-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250068 --- Comment #1 from O. Hartmann <ohartmann@walstatt.org> --- I just checked on several other CURRENT installations of ours and with different configuration option set when postgresql12|13-server is compiled - with our setup it is always the same. The one thing we didn't check so far is whether the database itself, which = is migrated via a simple dump (pg_dumpall) and rereading when the new setup postgresql server is running might be the culprit. Compiling server and client with the standard config options resulted in the same fail as described above.=20 Disabling ipfw (the firewall we use) or switching to pass everything doesn't change anything. Even allow explicitely ::1 and 127.0.0.1 doesn't change anything. Again, hosts are configured to use IPv4 and IPv6! Remote access via LDAP backed users to databases works fine. Local access via socket works fine, but not when explicetely connect via tcp ::1 or 127.0.0.1! Mots hosts in our lab run dual stack, so next I'll try to switch off IPV6. New setups on freshly installed hosts with IPV4 only seem to work properly. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250068-7788-rLtiNtLQtf>