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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: stefan(dot)muster(at)isc-ejpd(dot)admin(dot)ch
Subject: BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029] LOG: invalid length of startup" in logfile
Date: 2018-07-24 09:19:44
Message-ID: 153242398409.1403.3646573029055189847@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15292
Logged by: stefan muster
Email address: stefan(dot)muster(at)isc-ejpd(dot)admin(dot)ch
PostgreSQL version: 11beta2
Operating system: SUSE Linux Enterprise Server 12 (x86_64)
Description:

Modification in pg_hba.conf:

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

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.

If listen_addresses = '*' change to listen_addresses = 'localhost' and
restart the Postgres Cluster, I do not receive any further error messages
in logfile. But as expected, the remote connections are not working in this
case.

I've also postgresql version 10 on the same host and can not detect any
issuses when we change listen_adresses = '*'

Thanks a lot for your Investigation and feedback.

With best regards
Stefan

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-07-24 09:27:16 Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack
Previous Message PG Bug reporting form 2018-07-24 07:10:26 BUG #15291: Lateral join has different/suprising semantics (with impure function)