Hello everyone! I’m running MySQL version 8.0.42 and sometimes I see these messages in my logs during server startup:
2025-07-18T01:15:23.245601Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 8500 (requested 450000)
2025-07-18T01:15:23.245604Z 0 [Warning] [MY-010141] [Server] Changed limits: max_connections: 8750 (requested 95000)
2025-07-18T01:15:23.245607Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 350 (requested 3500)
2025-07-18T01:15:23.421892Z 0 [Warning] [MY-000081] [Server] option 'max_allowed_packet': unsigned value 2147483648 adjusted to 1073741824
2025-07-18T01:15:23.423134Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.24.04.1) starting as process 2948571
2025-07-18T01:15:23.432416Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started
2025-07-18T01:15:23.907162Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended
2025-07-18T01:15:24.099715Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed
2025-07-18T01:15:24.099738Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel
2025-07-18T01:15:24.111967Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '127.0.0.1' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2025-07-18T01:15:24.112019Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.42-0ubuntu0.24.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2025-07-18T01:15:24.112254Z 12 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: 'mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead
2025-07-18T01:15:24.112256Z 13 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: 'mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead
What do these warnings mean and should I be worried about them? The server seems to work fine but I want to make sure everything is okay.
Those warnings just mean MySQL’s protecting your system. You set aggressive limits like 95,000 max connections or 450,000 open files, but your OS says “nope” and enforces its own caps through ulimit and systemd. MySQL backs down to safer values so your server doesn’t crash. I’ve seen this tons of times - DBAs copy configs from huge servers without thinking about their actual OS limits. The mysql_native_password deprecation warning isn’t urgent, but you’ll need to switch to caching_sha2_password eventually since they’re dropping support. These are just safety nets doing their job, not actual problems.
These warnings just mean MySQL is tweaking your config to work with your system’s limits. Your OS can’t handle what you asked for in the config file, so MySQL dials it back automatically. Like that 450,000 file limit - your system’s ulimit probably won’t allow that many files open at once. The self-signed cert warning is normal for fresh installs and won’t break anything. The mysql_native_password thing is just telling you to update your auth method sometime (no rush). Your server’s running fine - these are safety adjustments, not actual errors. If the warnings bug you, check your my.cnf settings and match them to what your system can actually handle.
these are just MySQL being cautious about ur config. the max_allowed_packet dropped from 2GB to 1GB - still plenty for most queries. the SSL cert warning happens bc MySQL auto-generates certs during install. normal behavior unless u need proper SSL for production.
These warnings are pretty normal in production - your config just hit some system limits. I’ve seen this exact thing on our database servers. Usually it’s because the OS file descriptor and memory limits are tighter than what you set in my.cnf. MySQL just scales things down automatically instead of crashing on startup. That max_allowed_packet getting knocked from 2GB to 1GB? That’s a hard MySQL cap - anything over 1073741824 bytes gets cut no matter what you configure. The certificate warning happens because MySQL creates self-signed certs during install. They work fine locally, but you’ll need real certificates for external connections. Those mysql_native_password deprecation warnings won’t break anything right now, but start planning a move to caching_sha2_password since that’s where things are heading.
ya, it means ur limits r too high for your system. MySQL adjusts em to what it can manage. It should b fine for most tasks, no need to stress unless ur hitting performance issues.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.