From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: Peter <pmc@citylink.dinoex.sub.org>,
        "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: Failing GSSAPI TCP when connecting to server
In-reply-to: <CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com>
References: <ZvmUe9_0WMfy5o-P@disp.intra.daemon.contact> <CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Sun, 29 Sep 2024 20:27:50 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1341514.1727661935.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sun, 29 Sep 2024 22:05:35 -0400
Message-ID: <1341515.1727661935@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1341515.1727661935%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> writes:
> On Sun, Sep 29, 2024 at 2:00 PM Peter <pmc@citylink.dinoex.sub.org> wrote:
>> My application is trying to connect the database server, and meanwhile
>> tries to talk to the KDC server for a service ticket.

>> A configuration problem on the machine(s) can be ruled out,

> Famous last words.

The TCP trace looks like the client side is timing out too quickly
in the unsuccessful case.  It's not clear to me how the different
Discourse version would lead to the Kerberos library applying a
different timeout.  Still, it seems like most of the moving parts
here are outside of Postgres' control --- I don't think that libpq
itself has much involvement in the KDC communication.

I concur with looking at the Discourse release notes and maybe asking
some questions in that community.

			regards, tom lane