Re: BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029] LOG: invalid length of startup" in logfile - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029] LOG: invalid length of startup" in logfile
Date
Msg-id 1433.1532440454@sss.pgh.pa.us
Whole thread Raw
In response to BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029]LOG: invalid length of startup" in logfile  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> Modification in pg_hba.conf:

> Add line "host    all             all             172.24.84.43/0         
> md5" in Section # IPv4 local connections:

The above is accepting connections from *anywhere*, not only 172.24.84.43.
ITYM 172.24.84.43/32 ...

> And Modification in postgresql.conf:
> listen_addresses = '*'

> After Restart postgres Cluster, I receive all Minutes Messages like
> ""2018-07-24 10:46:12.566 CEST [32029] LOG:  invalid length of startup" in
> Logfile. But the remote Connection from Host 172.24.84.43 is working as
> expected.

What that says is you're getting port-scanned by something or other,
once you expose a PG port on your network-accessible interface.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15291: Lateral join has different/suprising semantics (with impure function)
Next
From: Andres Freund
Date:
Subject: Re: BUG #15293: Stored Procedure Triggered by Logical Replication isUnable to use Notification Events