LOG: incomplete startup packet
Hello,
Time to time found in postgres.log the following message
01:35:22.608 LOG: incomplete startup packet
01:35:27.147 LOG: incomplete startup packet
01:35:52.593 LOG: incomplete startup packet
01:35:57.146 LOG: incomplete startup packet
01:36:22.596 LOG: incomplete startup packet
01:36:27.146 LOG: incomplete startup packet
01:36:52.593 LOG: incomplete startup packet
01:36:57.145 LOG: incomplete startup packet
Are any way exists how to identify the source. What need to collect and
what need to see.
Best Regards
Paul
On 8/11/18 11:19 π.μ., Pavel Demidov wrote:
Hello,
Time to time found in postgres.log the following message
01:35:22.608 LOG: incomplete startup packet
01:35:27.147 LOG: incomplete startup packet
01:35:52.593 LOG: incomplete startup packet
01:35:57.146 LOG: incomplete startup packet01:36:22.596 LOG: incomplete startup packet
01:36:27.146 LOG: incomplete startup packet
01:36:52.593 LOG: incomplete startup packet
01:36:57.145 LOG: incomplete startup packetAre any way exists how to identify the source. What need to collect and what need to see.
Just try enable log_connections and the previous line should tell you the IP.
Best Regards
Paul
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
Hi
čt 8. 11. 2018 v 10:19 odesílatel Pavel Demidov <zeller56@gmail.com> napsal:
Hello,
Time to time found in postgres.log the following message
01:35:22.608 LOG: incomplete startup packet
01:35:27.147 LOG: incomplete startup packet
01:35:52.593 LOG: incomplete startup packet
01:35:57.146 LOG: incomplete startup packet01:36:22.596 LOG: incomplete startup packet
01:36:27.146 LOG: incomplete startup packet
01:36:52.593 LOG: incomplete startup packet
01:36:57.145 LOG: incomplete startup packetAre any way exists how to identify the source. What need to collect and
what need to see.Best Regards
Paul
some monitoring tools does it
Regards
Pavel
Hello,
Thank your answer. If there are a lot of messages 'LOG: incomplete startup
packet' into postgres log will it cause the log overflow?
Does it possible to filter it or ban to write.
Regards,
Paul
On Thu, Nov 8, 2018 at 1:06 PM Pavel Stehule <pavel.stehule@gmail.com>
wrote:
Show quoted text
Hi
čt 8. 11. 2018 v 10:19 odesílatel Pavel Demidov <zeller56@gmail.com>
napsal:Hello,
Time to time found in postgres.log the following message
01:35:22.608 LOG: incomplete startup packet
01:35:27.147 LOG: incomplete startup packet
01:35:52.593 LOG: incomplete startup packet
01:35:57.146 LOG: incomplete startup packet01:36:22.596 LOG: incomplete startup packet
01:36:27.146 LOG: incomplete startup packet
01:36:52.593 LOG: incomplete startup packet
01:36:57.145 LOG: incomplete startup packetAre any way exists how to identify the source. What need to collect and
what need to see.Best Regards
Paulsome monitoring tools does it
Regards
Pavel
út 13. 11. 2018 v 16:42 odesílatel Pavel Demidov <zeller56@gmail.com>
napsal:
Hello,
Thank your answer. If there are a lot of messages 'LOG: incomplete startup
packet' into postgres log will it cause the log overflow?
Does it possible to filter it or ban to write.
It is garbage. Usually it means nothing, but better to work live without
this garbage.
Pavel
Show quoted text
Regards,
PaulOn Thu, Nov 8, 2018 at 1:06 PM Pavel Stehule <pavel.stehule@gmail.com>
wrote:Hi
čt 8. 11. 2018 v 10:19 odesílatel Pavel Demidov <zeller56@gmail.com>
napsal:Hello,
Time to time found in postgres.log the following message
01:35:22.608 LOG: incomplete startup packet
01:35:27.147 LOG: incomplete startup packet
01:35:52.593 LOG: incomplete startup packet
01:35:57.146 LOG: incomplete startup packet01:36:22.596 LOG: incomplete startup packet
01:36:27.146 LOG: incomplete startup packet
01:36:52.593 LOG: incomplete startup packet
01:36:57.145 LOG: incomplete startup packetAre any way exists how to identify the source. What need to collect and
what need to see.Best Regards
Paulsome monitoring tools does it
Regards
Pavel