public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Ron Johnson <[email protected]>
Cc: Peter <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Failing GSSAPI TCP when connecting to server
Date: Sun, 29 Sep 2024 22:05:35 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com>
References: <[email protected]>
	<CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com>

Ron Johnson <[email protected]> writes:
> On Sun, Sep 29, 2024 at 2:00 PM Peter <[email protected]> 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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Failing GSSAPI TCP when connecting to server
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox