<p>ER_STARTUP is an informational MySQL message indicating the server is starting or has just become ready for client connections, but it can surface during failed or incomplete startups.</p>
<p>MySQL Error 1408: ER_STARTUP shows that mysqld is announcing ready for connections. If the message loops or blocks clients, check my.cnf paths, port conflicts, and file permissions, then restart the server with corrected settings. Aligning configuration and port usage clears the notice and restores access.</p>
%s: ready for connections. Version: '%s' socket: '%s'
MySQL Error 1408 with condition ER_STARTUP is printed by mysqld at startup. The full text is "%s: ready for connections. Version: '%s' socket: '%s' port: %d %s". It confirms the daemon has initialised networking and is listening for clients.
Although normal, the message can appear repeatedly when the server fails mid-boot or when monitoring tools misinterpret it as an error. Understanding its context avoids false alarms and highlights genuine startup issues.
The notice appears every time mysqld finishes initialisation. If configuration changes force multiple restarts, you will see several ER_STARTUP lines. It can also surface when the server starts but crashes soon after, causing watchdogs to restart it in a loop.
Port conflicts, bad sockets, missing data directories, or insufficient permissions can trigger partial startups that log ER_STARTUP before failing, confusing administrators who expect a single occurrence.
Start by examining the entire error log to confirm whether ER_STARTUP is followed by crash traces. If crashes occur, resolve the root issue, such as incorrect innodb_data_home_dir or a duplicate port.
Validate my.cnf settings, ensure the data directory exists and is writable, and confirm no other process is using the configured port. After adjustments, restart mysqld and watch for a single ER_STARTUP entry followed by routine activity.
When Docker containers restart repeatedly, mount the data volume with correct ownership so mysqld can write, preventing loops of ER_STARTUP. On systemd hosts, check that LimitNOFILE is high enough to stop early terminations that happen right after ER_STARTUP.
If high-availability tools report ER_STARTUP as an error, tune alert rules to ignore single occurrences and only flag multiple rapid entries, ensuring accurate monitoring without noise.
Keep configuration in version control and run mysqld --validate-config before reloads to catch typos early. Monitor port 3306 (or custom) availability and use lsof to detect collisions. Automate permission fixes with provisioning scripts.
Galaxy users can store vetted startup scripts and my.cnf snippets in Collections, letting teams share approved configurations and reducing accidental misconfigurations that lead to startup loops.
Error 2002 (HY000) - Can't connect to local MySQL server: appears when clients try to connect before ER_STARTUP logs. Wait until ER_STARTUP completes or adjust client retries.
Error 1024 - Too many opens: may follow ER_STARTUP if file descriptor limits are low. Increase the limit in systemd or ulimit settings.
Another service is already listening on the configured MySQL port, causing mysqld to start, announce readiness, then exit.
The socket file path in my.cnf points to a location mysqld cannot create, leading to repeated startups.
The MySQL user lacks ownership of the data directory or log directory, causing crashes shortly after ER_STARTUP.
Damaged InnoDB tablespace or redo logs let the server initialise just enough to print ER_STARTUP before aborting.
Occurs when clients attempt connection before ER_STARTUP or when mysqld fails to bind the socket.
Indicates TCP connection issues, often due to firewall or port conflicts detected during ER_STARTUP.
Appears after ER_STARTUP if file descriptor limits are insufficient for normal operation.
No. A single ER_STARTUP line is normal. Multiple rapid entries usually signal a startup loop that needs investigation.
If the server crashes right after ER_STARTUP, the socket or port closes before clients connect. Fix the underlying crash cause.
You can lower the log_error_verbosity, but it is safer to leave the message and adjust alert rules instead.
Galaxy lets teams store production-ready my.cnf files and startup scripts in shared Collections, reducing misconfigurations that trigger repeated ER_STARTUP messages.
.avif)
.avif){kind=logo}
