[YSQL] Logs are flooded with "incomplete startup packet" messages #4813
Assignees
Labels
area/ysql
Yugabyte SQL (YSQL)
Comments
d-uspenskiy
added a commit
that referenced
this issue
Jun 25, 2020
Summary: Postgres logs each failed connection attempt ``` 2019-11-28 13:24:26.501 UTC [15168] LOG: incomplete startup packet ``` Different monitoring tools may scans opened ports without sending any data. Postgres log file will be flooded with above message in this case. Solution is to avoid logging in case connection has no data. Additional details can be found here: https://www.percona.com/blog/2019/12/03/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/ Vanilla postgres patch: https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=342cb650e Test Plan: Manual: - start YB cluster with ysql enabled - run simple port monitoring `for i in {1..100}; do nc -zv localhost 5433 ; done` - check absence of `incomplete startup packet` log `cd ~/yugabyte-data && grep -e "incomplete startup packet" -R` Reviewers: alex, neha Reviewed By: neha Subscribers: mihnea, mikhail, yql Differential Revision: https://phabricator.dev.yugabyte.com/D8722
AbdallahKhaled93
pushed a commit
to AbdallahKhaled93/yugabyte-db
that referenced
this issue
Jun 29, 2020
Summary: Postgres logs each failed connection attempt ``` 2019-11-28 13:24:26.501 UTC [15168] LOG: incomplete startup packet ``` Different monitoring tools may scans opened ports without sending any data. Postgres log file will be flooded with above message in this case. Solution is to avoid logging in case connection has no data. Additional details can be found here: https://www.percona.com/blog/2019/12/03/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/ Vanilla postgres patch: https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=342cb650e Test Plan: Manual: - start YB cluster with ysql enabled - run simple port monitoring `for i in {1..100}; do nc -zv localhost 5433 ; done` - check absence of `incomplete startup packet` log `cd ~/yugabyte-data && grep -e "incomplete startup packet" -R` Reviewers: alex, neha Reviewed By: neha Subscribers: mihnea, mikhail, yql Differential Revision: https://phabricator.dev.yugabyte.com/D8722
deeps1991
pushed a commit
to deeps1991/yugabyte-db
that referenced
this issue
Jul 22, 2020
Summary: Postgres logs each failed connection attempt ``` 2019-11-28 13:24:26.501 UTC [15168] LOG: incomplete startup packet ``` Different monitoring tools may scans opened ports without sending any data. Postgres log file will be flooded with above message in this case. Solution is to avoid logging in case connection has no data. Additional details can be found here: https://www.percona.com/blog/2019/12/03/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/ Vanilla postgres patch: https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=342cb650e Test Plan: Manual: - start YB cluster with ysql enabled - run simple port monitoring `for i in {1..100}; do nc -zv localhost 5433 ; done` - check absence of `incomplete startup packet` log `cd ~/yugabyte-data && grep -e "incomplete startup packet" -R` Reviewers: alex, neha Reviewed By: neha Subscribers: mihnea, mikhail, yql Differential Revision: https://phabricator.dev.yugabyte.com/D8722
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed on one of our internal clusters that YSQL logs are flooded with
incomplete startup packetmessages.We should look into the patch mentioned here:
https://www.percona.com/blog/2019/12/03/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/
The text was updated successfully, but these errors were encountered: