closing bad idle connection: EOF about mysql

[cong08]

MySQL

[cong08]

I found the following log in the service area: 2024-05-16T11:13:29.336399Z 7367834 [Note] [MY-010914] [Server] Aborted connection 7367834 to db: '' user: '' host: '' (Got timeout reading communication packets). (sql_connect.cc:835) 2024-05-16T11:14:10.286303Z 7367835 [Note] [MY-013417] [Server] The wait_timeout period was exceeded, the idle time since last command was too long. (net_serv.cc:1508) However, the MySQL wait_timeout is set to 28800, and I have set ConnMaxLifetime to 240s. It seems that the server is actively closing the connection. Could it be that ConnMaxLifetime is not taking effect? Should I also set SetConnMaxIdleTime? If SetConnMaxIdleTime is set to a time greater than ConnMaxLifetime, will it close the connection?

[methane]

That 4 lines of code is not enought to reproduce.
Can you reproduce it with Docker MySQL?
And can you write complete, runnable sample code?

Anyway, only I can say is Go received EOF. It means someone close the connection.
wait_timeout is common, but not only reason to close connections.
Your OS, router, middleware, etc... can close your connection.
And as your server says, someone between Go and MySQL closed your connection.

I can not debug your environment. You should debug your environment with Wireshark and tcpdump.