On Thu, 27 Aug 2020 12:44:11 -0400, Tom Lane wrote:
> 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.
Oh, send(2) on OpenBSD [1] says that the firewall may cause suc
Daniel Jakots writes:
> On Thu, 27 Aug 2020 09:04:25 -0700, Adrian Klaver
> 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
]:
> > [8-1] 10.10.10.43(41816):api@api: LOG: connection authorized:
> > user=api database=api Aug 27 02:10:02 db1 postgres[62464]: [9-1]
> > 10.10.10.43(41816):api@api: LOG: could not send data to client:
> > Permission denied
>
> I would think it is the above.
database=api
Aug 27 02:10:02 db1 postgres[62464]: [9-1] 10.10.10.43(41816):api@api: LOG:
could not send data to client: Permission denied
I would think it is the above.
Are you using some sort of authentication for the API?
Aug 27 02:10:02 db1 postgres[62464]: [9-2] 10.10.10.43(41816):api@ap
62464]: [9-1] 10.10.10.43(41816):api@api: LOG:
could not send data to client: Permission denied
Aug 27 02:10:02 db1 postgres[62464]: [9-2] 10.10.10.43(41816):api@api:
STATEMENT: SELECT ip FROM pf_ip_ban;
Aug 27 02:10:02 db1 postgres[62464]: [10-1] 10.10.10.43(41816):api@api: FATAL:
connection to cl
