Re: could not send data to client: Permission denied

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Jakots <postgres(at)chown(dot)me>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: could not send data to client: Permission denied
Date: 2020-08-27 16:44:11
Message-ID: 3167711.1598546651@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Daniel Jakots <postgres(at)chown(dot)me> writes:
> On Thu, 27 Aug 2020 09:04:25 -0700, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>> Are you using some sort of authentication for the API?

> Sorry I'm not sure what you mean?

> Between the clients and the python code I use some "basic auth" (and IP
> restrictions on the reverse proxy). But I can't see how it would cause
> the problem.

The error shows that you're already through authentication and executing a
normal query (since a query is cited in the log). So whatever this is,
it doesn't seem like it could be an authentication issue.

It looks like send() itself is returning EACCES, which seems just
weird. The send(2) man page does cite some possible causes of
EACCES, but none of them seem relevant here. I think you might
need a kernel guru.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Jakots 2020-08-27 17:03:55 Re: could not send data to client: Permission denied
Previous Message Daniel Jakots 2020-08-27 16:14:49 Re: could not send data to client: Permission denied