启动包停靠器postgressql的无效长度
启动包停靠器postgressql的无效长度
提问于 2022-05-16 19:36:20
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如果能提供任何帮助，我会很感激
码头作曲家文件
版本：“3.9”
服务: postgres: image: postgres:14-高寒端口：- 5432:5432卷：-/app/postgres:/var/lib/postgresql/data环境：- POSTGRES_PASSWORD=S3cret - POSTGRES_USER=citizix_user - POSTGRES_DB=citizix_db
使用ubuntu 20.4
Stack Overflow用户
发布于 2022-05-17 07:15:51
有些东西，可能是监视系统，是建立到数据库服务器的TCP连接，然后关闭它们而不发送正确的PostgreSQL连接数据包。
您可以在您的%h中包含log_line_prefix，以查看这些连接的客户端地址，这可能有助于识别罪魁祸首。
解决方案是让监视系统建立数据库连接，而不仅仅是TCP连接。这不仅会消除消息，而且会使测试更加有用。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/72264710
复制相关文章
相似问题
腾讯云开发者
