public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Peter J. Holzer <[email protected]>
Cc: [email protected]
Subject: Re: expected authentication request from server, but received H
Date: Thu, 23 May 2024 17:23:14 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

"Peter J. Holzer" <[email protected]> writes:
> One of our users reports getting the error message
> "expected authentication request from server, but received H"
> when trying to connect to the database.

That's very bizarre, and I don't recall any similar reports in the
recent past.

> Server is PostgreSQL 15.7 (Ubuntu 15.7-1.pgdg22.04+1)
> I haven't been able to find out what client version they are using yet,
> but I suspect it's quite old.

It would definitely be interesting to find out what the client-side
code is, including the openssl version being used.

> We've been on 15.x for quite a while now and it did work until at least
> a month ago, so I wouldn't expect an incompatible protocol change,
> however, I think the upgrade from 15.6 to 15.7 was just last week, so
> maybe something changed between these minor versions?

A look at the release notes doesn't suggest that anything was changed
in that area.  But I wonder if your new build could differ in some
other relevant way, such as being linked to a newer openssl version.

> I'm especially intrigued by "received H". According to
> https://www.postgresql.org/docs/current/protocol-message-formats.html
> Byte1('H') could mark a Copy Out response or a Flush command. Both don't
> make sense in that context.

Yeah, that couldn't be a valid message type byte here.  I guess that
either (a) the TLS stuff is going wrong and delivering garbage
data, or (b) libpq is somehow out of sync with the server, such that
it's taking a data byte as a message type byte.

I found a description of an ancient instance of (b) here:

https://www.postgresql.org/message-id/flat/CAAZKuFaxdPccCs9%2B2hTbMM5iwPZP6C494sAVz6qZhOPcYSGkTQ%40m...

Of course we fixed that a dozen years ago, and anyway that particular
problem required a server that is in dire straits.

			regards, tom lane

view thread (3+ messages)  latest in thread

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: expected authentication request from server, but received H
  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