public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Failing GSSAPI TCP when connecting to server
Date: Sun, 29 Sep 2024 20:27:50 -0400
Message-ID: <CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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.
> Earlier these TCP connections did run like this, and were successful:
>
> [snip]
>
> A configuration problem on the machine(s) can be ruled out,
Famous last words.
> because both
> old (working) and new (failing) application are installed on the same
> machine at the same time, using the same network, same hardware, same
> OS, same libgssapi and same postgres client software connecting to the
> same database.
>
> There are no errors logged on the KDC server, it appears to have
> orderly processed the requests (at least at first, it starts to
> complain later when the stale sockets get too many).
>
> The error message on the postgres server is
> FATAL: GSSAPI authentication failed for user "pmc"
>
Is there a way to test pmc authentication via some other tool, like psql?
> The OS is FreeBSD Release 13.4-p1
> The postgres client library libpq.so.5 is Release 15.7
> The application postgres interface is rubyGem pq Release 1.5.4
> The application is Discourse 2.2.0 (working) and 2.3.1 (failing)
>
> What is going on there?
>
If *only *the application changed, then by definition it can't be a
database problem. *Something* in the application changed; you just haven't
found it.
Specifically, I'd read the Discourse 2.3.0 and 2.3.1 release notes.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!
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]
Subject: Re: Failing GSSAPI TCP when connecting to server
In-Reply-To: <CANzqJaD6QOd2MrcG+sxfgJtQcuXcpn0NdGjir3C9q4CnkC=faA@mail.gmail.com>
* 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