PostgreSQL init process complete; ready for start up.
2022-05-16 19:28:51.674 UTC [1] LOG: starting PostgreSQL 14.2 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
2022-05-16 19:28:51.674 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2022-05-16 19:28:51.674 UTC [1] LOG: listening on IPv6 address "::", port 5432
2022-05-16 19:28:51.677 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-05-16 19:28:51.681 UTC [51] LOG: database system was shut down at 2022-05-16 19:28:51 UTC
2022-05-16 19:28:51.684 UTC [1] LOG: database system is ready to accept connections
2022-05-16 19:29:07.610 UTC [59] LOG: invalid length of startup packet
2022-05-16 19:29:07.611 UTC [58] LOG: invalid length of startup packet
2022-05-16 19:29:07.612 UTC [60] LOG: invalid length of startup packet
2022-05-16 19:29:08.647 UTC [62] LOG: invalid length of startup packet
2022-05-16 19:29:08.650 UTC [61] LOG: invalid length of startup packet
2022-05-16 19:29:08.652 UTC [63] LOG: invalid length of startup packet任何帮助都将不胜感激我不知道
Docker编写器文件
版本：“3.9”
服务：邮政：图片：postgres：14个阿尔卑斯港口：- 5432：5432卷：- ~/应用程序/postgres：/var/库/postgresql/数据环境：- 邮政编码密码= S3 cret-邮政编码用户=公民用户-邮政编码数据库=公民数据库
使用Ubuntu 20.4
1条答案
按热度按时间n3h0vuf21#
某个东西（可能是监视系统）正在建立到数据库服务器的TCP连接，然后在没有发送正确的PostgreSQL连接包的情况下关闭这些连接。
您可以在
log_line_prefix中包含%h，以查看这些连接的客户机地址，这可能有助于确定问题所在。解决方案是让监控系统建立一个数据库连接，而不仅仅是一个TCP连接，这样不仅可以消除消息，而且可以使测试更加有用。